Clean up gitignore and yarn (#337)

* Clean up gitignore and yarn

* Add back the pages/docs/manual/ stuff and add explanation

Author: chenglou

.gitignore

@@ -1,5 +1,3 @@
-out
-
 .DS_Store
 *.swp
 *.swo
@@ -11,17 +9,14 @@ node_modules/
 .next/
 index_data/*.json
 
+# these docs are checked in, but we consider them frozen.
+# git add -f file to update them
 pages/docs/manual/v8.0.0/
 pages/docs/manual/v9.0.0/
 
-yarn-error.log
-
 .bsb.lock
 .merlin
 lib/
 .vscode/
 
 .vercel
-
-# for IDE tooling tests
-bin.exe

CONTRIBUTING.md

@@ -22,7 +22,7 @@ If you can't find any relevant issues, feel free to create a new one to start a
 
 **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! 
+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").
 
@@ -84,6 +84,6 @@ Most of the stuff we want to build can be built as components with Tailwind clas
 
 - Clone the project and follow the [README](README.md) instructions
 - Always run the page locally and verify your changes (especially when working on code examples)
-- When writing markdown with code examples, always run `yarn test` to prevent broken code
+- When writing markdown with code examples, always run `npm test` to prevent broken code
 - Feel free to open `Draft PRs` when you are working on bigger features (good for visibility and asking for feedback)
 - Improve code based on last feedback until the code is ready to be merged

package.json

@@ -34,7 +34,7 @@
   },
   "scripts": {
     "dev": "next",
-    "build": "rescript && yarn run update-index && next build",
+    "build": "rescript && npm run update-index && next build",
     "test": "node scripts/test-examples.mjs && node scripts/test-hrefs.mjs",
     "reanalyze": "reanalyze -all-cmt .",
     "update-index": "node scripts/extract-indices.mjs && node scripts/extract-tocs.mjs && node scripts/extract-syntax.mjs && node scripts/generate_feed.mjs > public/blog/feed.xml"