Back to News

OCaml.org Newsletter: July 2023

Welcome to the July 2023 edition of the OCaml.org newsletter! As with the previous issues, this update has been compiled by @sabine and @tmattio.

Our goal is to make OCaml.org the best resource for anyone who wants to get started and be productive in OCaml. The OCaml.org newsletter provides an update of our progress towards that goal and an overview of changes we are working on.

We couldn't do it without all the amazing OCaml community members who help us review, revise, and create better OCaml documentation. Your feedback enables us to better prioritise our work and make progress towards our goal. Thank you!

This month, our priorities were:

  • Learn Area: We're working towards making OCaml.org a great resource to learn OCaml and discover its ecosystem. This month, we continued writing the new documentation content and iterating on community feedback. We also finalised the Figma light desktop designs and started implementing the UI.
  • JavaScript Toplevels: We started exploring how to generate JavaScript toplevels for OCaml packages, with the goal of allowing users to load packages into the OCaml Playground, and adding a new toplevel feature to the OCaml Packages area. Ultimately, we aim to make every code block on OCaml.org interactive!
  • General Improvements: As usual, we also worked on general maintenance and improvements based on user feedback, and we're highlighting some of our work.

In addition to our work on the site, we introduced new ways for the team to interact with the community. We've created an #ocaml.org Discord channel, and we started holding public OCaml.org dev meetings. Don't hesitate to reach out to us on Discord and join the dev meetings. We're always looking for new insights on things to improve!

Learn Area

1. Redesign of the Learn Area

As the designs for the new Learn area are nearing completion, we started implementing the UI. If you have visited the documentation in the past few weeks, you've probably noticed a few changes. The most prominent one being the new tabs to navigate the different parts of the documentation.

On the design front, our focus will now be directed to the mobile views and dark mode.

Relevant PRs and Activities:

  • Continued work on Figma UX/UI designs for the new Learn area:
    • Finalised the light theme designs
    • Created color variants and a color palette in Figma, aiming for consistency with Figma to the Tailwind configuration, and established naming conventions for light and dark mode colors.
    • Designed various button variants on Figma, including Extra large, Large, Small, Large Ghost, Ghost, and Level tag styles.
  • Started implementing new components for the Learn Area:
  • Introduced new tabs to navigate the OCaml documentation by section -- ocaml/ocaml.org#1429

2. OCaml Documentation

We also continued the work on the new documentation content. As we've been through the lifecycle of new pages a couple times, we're getting more structured. Each new page goes through the following steps: Outline Approval, Drafting, Internal Review and, finally, Community Review. We have two new pages that are in the final stage (community review), namely the File Manipulation tutorial and Arrays guide. They should be ready to merge in the coming weeks. We also have a completely new Getting Started tutorial that aims to replace the existing "Your First Day with OCaml." It's currently in the internal review stage and should be shared on Discuss for community review soon.

Plus, we've got a lot more content in the drafting stage.

Stay tuned, as we'll be sharing more and more new documentation pages for community review!

Relevant PRs and Activities:

3. Preparing the Move of the opam Documentation to OCaml.org

The next step for the centralised package documentation is to serve the documentation of critical OCaml packages, including the OCaml manual and the Platform tools documentation. This requires a lot of work on odoc to remove the blockers that prevents project from moving from their current documentation generator to odoc. As an intermediate step, we'll be moving the opam documentation to OCaml.org's Learn area, so we can retire the frontend of opam.ocaml.org and redirect all the trafic to ocaml.org.

We've been working towards these goals this month. You can follow our progress on this PR.

Relevant PRs and Activities:

  • ocaml/opam:
  • ocaml-opam/opam2web:
    • Rearrange opam2web to remove all package info, build only opam archive, keep public key, and create redirections from opam.ocamlorg to ocaml.org in a Caddyfile. Current WIP branch at https://github.com/sabine/opam2web/tree/strip_to_bare_minimum
  • ocaml/ocaml.org:
    • Give Local Blogs a Page and RSS Feeds. This introduces the concept of a "blog hosted on OCaml.org." This way, we can host the non-changelog posts of the opam blog in such a way that we can redirect opam.ocaml.org/blog/feed.xml to ocaml.org/blog/opam/feed.xml

JavaScript Toplevels

Always with the aim to improve the learning experience, we're exploring how to generate JavaScript toplevels for all the OCaml packages (the ones that are JavaScript-compatible, that is).

This would enable a few very neat new features:

  • Loading OCaml packages from the OCaml Playground: to enable the use of any JavaScript-compatible package. This is very handy to share code snippets to beginners, which is currently limited to using the standard library.
  • Toplevels for OCaml packages on the centralised documentation: to spawn a toplevel while navigating the documentation.
  • Interactive toplevels for every code block: This includes the OCaml packages that contain code examples, but also every code block and exercices on the Learn area. You'd be able to run the code, edit it, run it again and inspect the result directly from the browser. Every documentation page becomes a Jupyter notebook!

We're very excited at the possibilities this brings to improving the learning experience. Let us know what you think, and stay tuned for updates on our explorations!

Relevant PRs and Activities:

General Improvements

This month, we're welcoming no less than 4 new contributors:

  • @contificate improved the OCaml Playground layout with @StonedHesus doing a review
  • @just-max fixed an issue with code sharing on the OCaml Playground
  • @AshineFoster updated the dev setup to be able to run the site without an internet connection.
  • @theteachr contributed a typo fix to the homepage.
  • @brandoncc contributed a typo fix to the First Day with OCaml tutorial

Thanks a lot to all the contributors this month! It's lovely to see more and more people making contributions to the site!

Relevant PRs and Activities:

  • OCaml Playground:
    • @contificate resolved the layout problem of the playground's bottom bar and thoroughly tested it in different browsers with a review from @StonedHesus -- ocaml.org#1384
    • Building the playground was challenging due to a script incompatibility with POSIX -- ocaml.org#1456
    • @just-max discovered and resolved an issue with Base64-encoded URLs generated by the Playground share button, ensuring backward compatibility -- ocaml.org#1434
  • OCaml.org package documentation:
    • Voodoo output format was updated to list README/LICENSE/CHANGELOG as part of status.json -- voodoo#68, ocaml.org#1435
    • Voodoo now includes a Voodoo_serialize module for data serialisation and deserialisation -- voodoo#103, ocaml.org#1442
    • Compile step issues with documentation pipeline generation tool addressed -- voodoo#115
    • In case of missing documentation, users are now redirected to the last documented version -- ocaml.org#1438
  • Bug fixes and miscellaneous improvements: