feed.xml

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Ocsigen Blog</title>
  <link href="https://ocsigen.org/feed.xml" rel="self" />
  <link href="https://ocsigen.org" />
  <updated>2026-09-08T00:00:00+00:00</updated>
  <id>https://ocsigen.org/</id>
  <author><name>Ocsigen Project</name></author>
  <entry>
    <title>TyXML 5.0.0: the HTML living standard and SVG 2</title>
    <link href="https://ocsigen.org/blog/posts/tyxml-5.0.0.html" />
    <updated>2026-09-08T00:00:00+00:00</updated>
    <id>https://ocsigen.org/blog/posts/tyxml-5.0.0.html</id>
    <author><name>The Ocsigen team</name></author>
    <summary type="html">TyXML 5.0.0 is out, and it is a major release. The library now follows the current specifications: the WHATWG living standard for HTML, and SVG 2 with the Filter Effects module for SVG, whose support had not moved since SVG 1.1. On the way …</summary>
  </entry>
  <entry>
    <title>Why Ocsigen decided not to switch from Lwt to Eio (for now)</title>
    <link href="https://ocsigen.org/blog/posts/why-ocsigen-stays-on-lwt-for-now.html" />
    <updated>2026-07-01T00:00:00+00:00</updated>
    <id>https://ocsigen.org/blog/posts/why-ocsigen-stays-on-lwt-for-now.html</id>
    <author><name>Vincent Balat</name></author>
    <summary type="html">Through 2025 we migrated the entire Ocsigen stack from Lwt to Eio. The migration compiles and the test suite passes, and yet we have decided to stay on Lwt for now. This post explains the two obstacles that stopped us: the loss of function …</summary>
  </entry>
  <entry>
    <title>Ocsipersist 2.1.0: type-safe persistence with Deriving</title>
    <link href="https://ocsigen.org/blog/posts/ocsipersist-2.1.0.html" />
    <updated>2026-06-23T00:00:00+00:00</updated>
    <id>https://ocsigen.org/blog/posts/ocsipersist-2.1.0.html</id>
    <author><name>The Ocsigen team</name></author>
    <summary type="html">Ocsipersist 2.1.0 is out. The headline is a new, type-safe way to store your data: persistent references, stores and tables can now be serialised with Deriving_Json instead of Marshal. The data is human-readable in the database and stable a…</summary>
  </entry>
  <entry>
    <title>Ocsigen in 2026: what we&#x27;re working on</title>
    <link href="https://ocsigen.org/blog/posts/status-of-the-ocsigen-project.html" />
    <updated>2026-06-19T00:00:00+00:00</updated>
    <id>https://ocsigen.org/blog/posts/status-of-the-ocsigen-project.html</id>
    <author><name>The Ocsigen team</name></author>
    <summary type="html">What are we actually working on these days? Faster Wasm compilation, a new documentation toolchain, hierarchical module names, mobile through Capacitor, AI coding skills... Here is an honest look at the state of Ocsigen in 2026: what is in …</summary>
  </entry>
  <entry>
    <title>A new home for the Ocsigen blog</title>
    <link href="https://ocsigen.org/blog/posts/welcome-to-the-ocsigen-blog.html" />
    <updated>2026-06-14T00:00:00+00:00</updated>
    <id>https://ocsigen.org/blog/posts/welcome-to-the-ocsigen-blog.html</id>
    <author><name>The Ocsigen team</name></author>
    <summary type="html">The Ocsigen blog is back, and it is now built like the rest of the Ocsigen website: with wodoc, our odoc-based static site generator. Each post is a plain .mld file — the same lightweight markup we use for the manuals and the API document…</summary>
  </entry>
  <entry>
    <title>Documenting OCaml projects with wodoc</title>
    <link href="https://ocsigen.org/blog/posts/documenting-ocaml-projects-with-wodoc.html" />
    <updated>2026-06-07T00:00:00+00:00</updated>
    <id>https://ocsigen.org/blog/posts/documenting-ocaml-projects-with-wodoc.html</id>
    <author><name>The Ocsigen team</name></author>
    <summary type="html">wodoc turns .mld and .mli sources into a complete, styled website — not just API documentation. The very site you are reading is built with it.</summary>
  </entry>
</feed>