Merge branch 'master' into add-vim-mode

Author: rbertramResi

.babelrc

@@ -0,0 +1,2 @@
+VERSION_LATEST="v11.0.0"
+VERSION_NEXT="v12.0.0"

.env

@@ -0,0 +1,4 @@
+*.res linguist-language=ReScript
+*.resi linguist-language=ReScript
+
+/public/playground-bundles/**  binary linguist-vendored

.gitattributes

@@ -0,0 +1,20 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 🚀 rescript-compiler
+    url: https://github.com/rescript-lang/rescript/issues
+    about: Please report problems about the ReScript compiler, build system and tools here.
+  - name: 💻 rescript-vscode
+    url: https://github.com/rescript-lang/rescript-vscode/issues
+    about: VSCode language support, LSP
+  - name: 📦 create-rescript-app
+    url: https://github.com/rescript-lang/create-rescript-app/issues
+    about: ReScript's project generator
+  - name: ⚛️ rescript-react
+    url: https://github.com/rescript-lang/rescript-react/issues
+    about: ReScript bindings to React.js
+  - name: 🌐 rescript-core
+    url: https://github.com/rescript-lang/rescript-core/issues
+    about: New ReScript standard library
+  - name: 💬 ReScript Forum
+    url: https://forum.rescript-lang.org/
+    about: For discussions about ReScript, please visit the official ReScript forum.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,9 @@
+---
+name: 🚨 Documentation issue
+about: Create an issue to help us improve the rescript-lang.org documentation website
+title: ''
+labels: ''
+assignees: ''
+
+---
+

.github/ISSUE_TEMPLATE/documentation_issue.md

@@ -4,10 +4,11 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
-          node-version: 14.x
+          node-version: 20
+          cache: npm
       - run: npm ci
       - run: npx rescript
       - run: npm test

.github/workflows/pull-request.yml

@@ -7,6 +7,7 @@ public/blog/feed.xml
 
 node_modules/
 .next/
+out/
 index_data/*.json
 
 # Generated via test examples script
@@ -15,8 +16,8 @@ _tempFile.cmj
 _tempFile.cmt
 
 # these docs are checked in, but we consider them frozen.
-pages/docs/manual/v8.0.0/
-pages/docs/manual/v9.0.0/
+# pages/docs/manual/v8.0.0/
+# pages/docs/manual/v9.0.0/
 
 .bsb.lock
 .merlin
@@ -26,3 +27,13 @@ lib/
 .vercel
 
 src/**/*.mjs
+scripts/gendocs.mjs
+scripts/generate_*.mjs
+
+# Generated via generate-llms script
+public/llms/manual/**/llm*.txt
+public/llms/react/**/llm*.txt
+pages/docs/**/**/llms.mdx
+
+public/playground-bundles/
+public/_redirects

.gitignore

@@ -0,0 +1 @@
+22.11.0

.node-version

@@ -6,8 +6,8 @@ Please make sure to check out our [Code of Conduct](CODE_OF_CONDUCT.md) and make
 
 ## Ways to contribute
 
-- Writing docs for the manual (Check for issues that are marked with a [`manual`](https://github.com/reason-association/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"manual") and [`help wanted`](https://github.com/reason-association/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"help+wanted") tag)
-- Joining in discussions on our [issue tracker](https://github.com/reason-association/rescript-lang.org/issues)
+- Writing docs for the manual (Check for issues that are marked with a [`manual`](https://github.com/rescript-lang/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"manual") and [`help wanted`](https://github.com/rescript-lang/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"help+wanted") tag)
+- Joining in discussions on our [issue tracker](https://github.com/rescript-lang/rescript-lang.org/issues)
 - Give feedback for improvements (incomplete / missing docs, bad wording,
   search user experience / design, etc.)
 - Advanced: Help building platform features (design system, automatic testing, markdown parsing, etc.)
@@ -16,35 +16,35 @@ Please make sure to check out our [Code of Conduct](CODE_OF_CONDUCT.md) and make
 
 ### Find an issue
 
-Before you start any work or submit any PRs, make sure to check our [issue tracker](https://github.com/reason-association/rescript-lang.org/issues) for any issues or discussions on the topic.
+Before you start any work or submit any PRs, make sure to check our [issue tracker](https://github.com/rescript-lang/rescript-lang.org/issues) for any issues or discussions on the topic.
 
 If you can't find any relevant issues, feel free to create a new one to start a discussion. We usually assign issues to a responsible person to prevent confusion and duplicate work, so always double check if an issue is currently being worked on, or talk to the current assignee to take over the task.
 
 **Always make sure to get feedback from the core maintainers before starting any work**
 
 The project follows very specific goals and tries to deliver the highest value with the least amount of resources. Please help us focus on the tasks at hand and don't submit any code / bigger refactorings without any proper discussion on the issue tracker. Otherwise your PR might not be accepted!
 
-If you need inspiration on what to work on, you can check out issues tagged with [`good first issue`](https://github.com/reason-association/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue") or [`help wanted`](https://github.com/reason-association/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"help+wanted").
+If you need inspiration on what to work on, you can check out issues tagged with [`good first issue`](https://github.com/rescript-lang/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue") or [`help wanted`](https://github.com/rescript-lang/rescript-lang.org/issues?q=is%3Aissue+is%3Aopen+label%3A"help+wanted").
 
 ### Discuss an issue
 
 We really appreciate all input from users, community members and potential contributors. Please make sure to consider the other person's opinion and don't assume any common knowledge.
 
-**Most importantly: Keep it professional and be nice to each other**
+**Most importantly: Keep it professional and be nice to eachother**
 
-There might be situations where others don't understand a proposed feature or have different opinions on certain writing styles. That's fine, discussions are always welcome! Communicate in clear actionables, make your plans clear and always stick to the original topic.
+There might be situations where others don't understand a proposed feature or have different opinions on certain writing styles. That's fine, discussions are always welcome! Communicate in clear actionables, make your plans clear and always to stick to the original topic.
 
 If other contributors disagree with certain proposals and don't change their mind after longer discussions, please don't get discouraged when an issue gets closed / postponed. Everyone tries their best to make the platform better, and to look at it in another perspective: Closed issues are also a highly valuable resource for others to understand technical decisions later on.
 
 ### Communicate your Time Commitment
 
 Open Source development can be a challenge to coordinate, so please make sure to block enough time to work on your tasks and show commitment when taking on some work. Let other contributors know if your time schedule changes significantly, and also let others know if you can't finish a task.
 
-We value your voluntary work, and of course it's fine to step back from a ticket for any reason (we can also help you if you are getting stuck). Please talk to us in any case, otherwise we might re-assign the ticket to other contributors.
+We value your voluntary work, and of course it's fine to step back from a ticket for any reasons (we can also help you if you are getting stuck). Please talk to us in any case, otherwise we might re-assign the ticket to other contributors.
 
 ### Communication Channels
 
-- [Issue Tracker](https://github.com/reason-association/rescript-lang.org/issues)
+- [Issue Tracker](https://github.com/rescript-lang/rescript-lang.org/issues)
 - [ReScript Discourse (General / mostly unrelated discussions)](http://forum.rescript-lang.org)
 
 ## Working on the rescript-lang.org
@@ -55,7 +55,7 @@ We try to keep our contribution guidelines to a minimum. Please keep following r
 
 The less code we write, the better. If there's a way to do rendering on the server, or enhance existing markdown files, we prefer that over client-side rendering and external loading.
 
-We also try to keep our third-party dependencies to a minimum. We use specific frameworks to make things work (`unified`, `remark`, `mdx`, `bs-platform`, etc).  Please try to keep a small JS footprint, especially for client side code (to keep the bundle size small).
+We also try to keep our third-party dependencies to a minimum. We use specific frameworks to make things work (`unified`, `remark`, `mdx`, `bs-platform`, etc). Please try to keep a small JS footprint, especially for client side code (to keep the bundle size small).
 
 ### Think about the target audience & UX
 
@@ -66,13 +66,13 @@ Always check if there are any designs for certain UI components and think about
 ### Technical Writing (Documentation)
 
 - Think and write in a JS friendly mindset when explaining concepts / showing examples.
-- No `foo` examples if somewhat possible. Try to establish practical context in your showcase examples.
+- No `foo` examples if somewhat possible. Try to establish practical context in your show case examples.
 - No references to `OCaml`. ReScript is its own language, and we don't rely on external resources of our host language.
 - If possible, no references to `Reason` examples / external resources. Our goal is to migrate everything to ReScript syntax.
 
 ### Tailwind for CSS Development
 
-We use [TailwindCSS](https://tailwindcss.com) for our component styling. Check out the [tailwind.config.js](tailwind.config.js) file for configured tailwind features, colors, border-radius values etc..  If you are not familiar with Tailwind, check out existing components for inspiration.
+We use [TailwindCSS](https://tailwindcss.com) for our component styling. Check out the [tailwind.config.js](tailwind.config.js) file for configured tailwind features, colors, border-radius values etc.. If you are not familiar with Tailwind, check out existing components for inspiration.
 
 We sometimes also need to fall back to common css (with tailwind `@apply` directives to enforce our style system). You can find the CSS main entrypoint in [styles/main.css](styles/main.css).