Documentation: use output from new doc-ci with odoc 3 features

.github/CODEOWNERS

@@ -1,7 +1,7 @@
-/data/ @christinerose
+/data/changelog/ @sabine
 /data/pages/governance.md @avsm
 /data/pages/privacy_policy.md @avsm
 /data/pages/carbon_footprint.md @avsm
 /data/tutorials/platform/op_00_principles.md @avsm
 /data/tutorials/platform/op_01_users.md @avsm
-/data/tutorials/guides/op_02_roadmap.md @avsm
+/data/tutorials/guides/op_02_roadmap.md @avsm

.github/PULL_REQUEST_TEMPLATE/cookbook_pr_template.md

@@ -0,0 +1,16 @@
+#### Checklist
+Ensure the following are addressed before submitting your PR:
+
+1. **Real-World Usefulness**:
+   - [ ] Does the task address a practical need in real-world application development?
+
+2. **Code Quality**:
+   - [ ] Is the code production-ready, safe, and free of potential security issues?
+   - [ ] Does the code avoid uncaught exceptions or other potential pitfalls?
+
+3. **Standard Library and Packages**:
+   - [ ] For tasks using the Standard Library: Does this recipe provide value beyond what an LLM could easily generate?
+   - [ ] For tasks using a package: Does this recipe implicitly recommend the package for production use?
+
+4. **Recipe Redundancy**:
+   - [ ] Does this recipe duplicate an existing task? If so, does it add value by showing differences between packages or approaches?

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,4 @@
+Please go to the `Preview` tab and select the appropriate sub-template:
+
+* [Other PR](?expand=1&template=other_pr_template.md)
+* [OCaml Cookbook Contribution](?expand=1&template=cookbook_pr_template.md)

.github/other_pr_template.md

@@ -0,0 +1,4 @@
+## Checklist
+
+* [ ] Please format your code using `make fmt`
+* [ ] If addressing an open issue, please link to it by writing "Resolves #1234" (use the relevant issue number)

.gitignore

@@ -10,3 +10,6 @@ _opam/
 
 # Files that people sometimes accidentally include in their PRs
 *:OECustomProperty
+
+# TailwindCSS opam file, which appears to be generated by the build
+tailwindcss.opam

CODE_OF_CONDUCT.md

@@ -4,4 +4,4 @@ This project has adopted the [OCaml Code of Conduct](https://github.com/ocaml/co
 
 # Enforcement
 
-This project follows the OCaml Code of Conduct [enforcement policy](https://github.com/ocaml/code-of-conduct/blob/main/CODE_OF_CONDUCT.md#enforcement).
+This project follows the OCaml Code of Conduct [enforcement policy](https://github.com/ocaml/code-of-conduct/blob/main/CODE_OF_CONDUCT.md#enforcement).

CONTRIBUTING.md

@@ -22,7 +22,8 @@ We've provided a list of community-driven content below. When adding content to
 - [The OCaml Planet](#ocaml-planet)
 - [Job Board](#content-job)
 - [Success Stories](#content-success-story)
-- [Academic and Industrial Users](#content-user)
+- [Academic Users](#content-academic-user)
+- [Industrial Users](#content-industrial-user)
 - [OCaml Books](#content-book)
 - [OCaml Cookbook Recipes](#content-cookbook)
 - [Recurring Events](#content-recurring-event)
@@ -104,13 +105,50 @@ The success stories should be structured in the following way:
 
 You can read [Ahref's Success Story](https://ocaml.org/success-stories/peta-byte-scale-web-crawler) for a good example.
 
-### <a name="content-user"></a>Add an Academic or Industrial User
+### <a name="content-academic-user"></a>Add an Academic User
 
-> Contribute to the [Academic Users](https://ocaml.org/academic-users) and [Industrial Users](https://ocaml.org/industrial-users).
+> Contribute to the [Academic Users](https://ocaml.org/academic-users).
 
-Add a new industrial user by creating a new Markdown file in [data/industrial_users/](data/industrial_users/). For instance: [cryptosense.md](data/industrial_users/cryptosense.md).
+You can add a new academic user by creating a new Markdown file in [data/academic_institutions/](data/academic_institutions). When submitting an academic institution to our webpage, please structure the data as follows:
 
-You can add a new academic user by creating a new Markdown file in [data/academic_institutions/](data/academic_institutions). For instance: [cornell.md](data/academic_institutions/cornell.md).
+Information about the institution
+- **`name`**: The full name of the academic institution.  
+- **`description`**: A brief overview of the institution, including its background and key details.  
+- **`url`**: The official website of the institution.  
+- **`logo`**: A link to the institution’s logo image.  
+- **`continent`**: The continent where the institution is located.  
+
+A list of courses available at the institution. Each course entry must include:  
+- **`name`**: The full name of the course.  
+- **`acronym`**: The course code or identifier.  
+- **`url`**: A direct link to the course webpage.  
+
+Location
+- **`lat`**: The latitude of the institution’s location.  
+- **`long`**: The longitude of the institution’s location. 
+
+For instance: [cornell.md](data/academic_institutions/cornell.md).
+
+### <a name="content-industrial-user"></a>Add an Industrial User
+
+> Contribute to the [Industrial Users](https://ocaml.org/industrial-users).
+
+Add a new industrial user by creating a new Markdown file in [data/industrial_users/](data/industrial_users/). When submitting an industrial user to our webpage, please structure the data as follows:
+
+Information about the organization
+- **`name`**: The full name of the organization.  
+- **`description`**: A brief overview of the organization, including its mission and key details.  
+- **`logo`**: A link to the organization’s logo image.  
+- **`url`**: The official website of the organization.  
+
+Locations  
+- A list of countries where the organization operates.  
+
+Additional Information  
+- **`consortium`**: Indicates whether the organization is part of a consortium (`true` or `false`).  
+- **`featured`**: Indicates whether the organization is highlighted as a featured entity (`true` or `false`). 
+
+For instance: [cryptosense.md](data/industrial_users/cryptosense.md).
 
 ### <a name="content-book"></a>Add a Book
 
@@ -124,10 +162,10 @@ The OCaml Cookbook is a place where OCaml developers share how to solve common
 tasks in OCaml using packages from the OCaml ecosystem.
 
 Here are the steps to contribute a recipe for an existing task:
-* Find the task in the [data/cookbook/tasks.yml](data/cookbook/tasks.yml) file.
-* Go to the task folder inside [data/cookbook/](data/cookbook/) that has the
+- Find the task in the [data/cookbook/tasks.yml](data/cookbook/tasks.yml) file.
+- Go to the task folder inside [data/cookbook/](data/cookbook/) that has the
   same name as the task's `slug`.
-* Create a `.ml` file containing the recipe and a YAML header with metadata about
+- Create a `.ml` file containing the recipe and a YAML header with metadata about
   the recipe.
 
 If the recipe does not fit into any existing task, you also need to create a
@@ -138,7 +176,7 @@ located under a relevant `category:` field.
 Finally, it is also possible to create and organise groups of tasks by creating
 new categories. Categories are recursive and may have subcategories, which are
 full categories too. A task listed in
-[data/cookbook/tasks.yml](data/cookbook/tasks.yml) may have no recipes yet. On the 
+[data/cookbook/tasks.yml](data/cookbook/tasks.yml) may have no recipes yet. On the
 other hand, it is not allowed to have a task folder in
 [data/cookbook/](data/cookbook/) that does not correspond to a task from the
 [data/cookbook/tasks.yml](data/cookbook/tasks.yml) file because it triggers a
@@ -147,14 +185,27 @@ compilation error.
 Each recipe is a way to perform a task using a combination of open-source
 libraries.
 
-#### OCaml Cookbook Recipe Review Checklist
+#### Guidelines for New OCaml Cookbook Recipes
+
+When contributing new recipes to the OCaml Cookbook, please adhere to the following:
+
+1. **Task Selection**:
+   - Focus on practical, reusable tasks relevant to a wide audience.
+   - Ensure the task demonstrates idiomatic OCaml usage.
+   - Avoid tasks that are overly trivial or highly specific to niche cases.
+
+2. **Code Standards**:
+   - Write clear, idiomatic OCaml code.
+   - Ensure the code compiles without errors or warnings.
+   - Use standard OCaml libraries and tools wherever possible.
 
-Checklist for reviewing OCaml cookbook submissions:
+3. **Evaluation Criteria**:
+   - Does the recipe address a useful real-world task?
+   - Is the code ready for production use?
+   - If using a package, does it implicitly recommend the package for production?
+   - Avoid duplicating existing recipes unless demonstrating package differences.
 
-1. does this recipe implement the task it's assigned to?
-2. if this recipe is creating a new task: (1) is the new task substantially different from existing tasks, (2) there is no existing task that this recipe solves, (3) is the new task description very clear on what the task is (be specific!)
-3. is the code explained sufficiently without overexplaining (be short and focus on what matters)?
-4. is the code such that you would put it into production? I.e. are the libraries used stable enough and is the code readable?
+Following these guidelines will help us maintain a high-quality and consistent OCaml Cookbook.
 
 ### <a name="content-recurring-event"></a>Add A Recurring Event
 
@@ -181,7 +232,7 @@ The Changelog covers developments across:
 
 #### Purpose and Audience
 
-The primary audience for the Changelog is OCaml users. Content should focus on changes, updates, and news that directly impact users of OCaml and its ecosystem. 
+The primary audience for the Changelog is OCaml users. Content should focus on changes, updates, and news that directly impact users of OCaml and its ecosystem.
 
 Good candidates for Changelog posts include: