You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
major: full dynamic pages and plain next.js (nodejs#5426)
* feat: introduce dynamic rendering of pages
* major: full dynamic pages and plain next.js (#2)
* chore: do not resort blog posts
* fix: sort by post date
* chore: apply code-review changes
Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Signed-off-by: Claudio Wunder <cwunder@gnome.org>
* chore: some code review changes
---------
Signed-off-by: Claudio Wunder <cwunder@gnome.org>
Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+54-56Lines changed: 54 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,24 +32,22 @@ Note that regular contributors do not need to become "Collaborators". Any contri
32
32
is a formality that comes with obligations.
33
33
34
34
If you're an active contributor seeking to become a member we recommend reaching out to one of the existing Team Members for guidance.
35
-
35
+
36
36
<details>
37
37
<summary><b>What's the process for becoming a Collaborator?</b></summary>
38
38
39
-
- You must be actively contributing to this repository.
40
-
- Contributions must include significant code reviews or code contributions.
41
-
- A nomination must be done by an existing Team Member of the Website Team with an Issue
42
-
- The Issue must explain and describe why the nominated person is a good addition to the team
43
-
- The Issue must contain links to relevant contributions through:
44
-
- Code Reviews
45
-
- Comments on Issues and PRs
46
-
- Authoring of PRs or Issues
47
-
- Comments or Authoring of Discussions
48
-
- The nomination must have at least 3 existing members of the Website Team to be in agreement with the nomination.
49
-
- This can be done through commenting with "agreement" (showing support) or reacting to the Issue with a :+1: (Thumbs-up Emoji)
50
-
- The Issue must be open for at least 72 hours without an objection from an existing member of the Website Team
51
-
- The nomination cannot pass until all open discordances/objections are resolved.
52
-
- Objections coming from the TSC or Core Collaborators are also counted as valid objections.
39
+
- You must be actively contributing to this repository.
40
+
- Contributions must include significant code reviews or code contributions.
41
+
- A nomination must be done by an existing Team Member of the Website Team with an Issue
42
+
- The Issue must explain and describe why the nominated person is a good addition to the team
43
+
- The Issue must contain links to relevant contributions through:
44
+
- Code Reviews
45
+
- Comments on Issues and PRs
46
+
- Authoring of PRs or Issues
47
+
- Comments or Authoring of Discussions
48
+
- The nomination must have at least 3 existing members of the Website Team to be in agreement with the nomination.
49
+
- This can be done through commenting with "agreement" (showing support) or reacting to the Issue with a :+1: (Thumbs-up Emoji)
50
+
- The Issue must be open for at least 72 hours without an objection from an existing member of the Website Team - The nomination cannot pass until all open discordances/objections are resolved. - Objections coming from the TSC or Core Collaborators are also counted as valid objections.
53
51
</details>
54
52
55
53
# Getting started
@@ -60,60 +58,60 @@ for getting things done and landing your contribution.
60
58
1. Click the fork button in the top right to clone the [nodejs.org repository](https://github.com/nodejs/nodejs.org/fork)
61
59
2. Clone your fork using SSH, GitHub CLI, or HTTPS.
6. Run the following to install the dependencies and start a local preview of your work.
90
88
91
-
```bash
92
-
npm ci # installs this project's dependencies
93
-
npx turbo serve # starts a preview of your local changes
94
-
```
89
+
```bash
90
+
npm ci # installs this project's dependencies
91
+
npx turbo serve # starts a preview of your local changes
92
+
```
95
93
96
94
7. Perform a merge to sync your current branch with the upstream branch.
97
95
98
-
```bash
99
-
git fetch upstream
100
-
git merge upstream/main
101
-
```
96
+
```bash
97
+
git fetch upstream
98
+
git merge upstream/main
99
+
```
102
100
103
101
8. Run `npx turbo format` to confirm that linting, and formatting are passing.
104
102
105
-
```bash
106
-
npx turbo format
107
-
```
103
+
```bash
104
+
npx turbo format
105
+
```
108
106
109
-
9. Once you're happy with your changes, add and commit them to your branch, then push the branch to your fork.
107
+
9. Once you're happy with your changes, add and commit them to your branch, then push the branch to your fork.
110
108
111
-
```bash
112
-
cd ~/nodejs.org
113
-
git add .
114
-
git commit -m "some message"
115
-
git push -u origin name-of-your-branch
116
-
```
109
+
```bash
110
+
cd~/nodejs.org
111
+
git add .
112
+
git commit -m "some message"
113
+
git push -u origin name-of-your-branch
114
+
```
117
115
118
116
10. Create a Pull Request.
119
117
@@ -126,12 +124,12 @@ This repository contains several scripts and commands for performing numerous ta
126
124
<details>
127
125
<summary>Commands for Running & Building the Website</summary>
128
126
129
-
- `npx turbo serve` runs Next.js's Local Development Server, listening by default on `http://localhost:3000/`.
130
-
- `npx turbo build` builds the Application on Production mode. The output is by default within `.next` folder.
131
-
- This is used for the Node.js Vercel Deployments (Preview & Production)
132
-
- `npx turbo deploy` builds the Application on Export Production Mode. The output is by default within `build` folder.
133
-
- This is used for the Node.js Legacy Website Server (DigitalOcean)
134
-
- `npx turbo start` starts a web server running serving the built content from `npx turbo build`
127
+
-`npx turbo serve` runs Next.js's Local Development Server, listening by default on `http://localhost:3000/`.
128
+
-`npx turbo build` builds the Application on Production mode. The output is by default within `.next` folder.
129
+
- This is used for the Node.js Vercel Deployments (Preview & Production)
130
+
-`npx turbo deploy` builds the Application on Export Production Mode. The output is by default within `build` folder.
131
+
- This is used for the Node.js Legacy Website Server (DigitalOcean)
132
+
-`npx turbo start` starts a web server running serving the built content from `npx turbo build`
135
133
</details>
136
134
137
135
<details>
@@ -186,7 +184,7 @@ We recommend a read on our [Collaborator Guide](COLLABORATOR_GUIDE.md#accepting-
186
184
- The person that is fast-tracking the PR (adding the label) must also comment on the PR that they're requesting the PR to be fast-tracked
187
185
- The comment must mention `@nodejs/website` and must have at least one 👍 (or any other sort of approval reaction) if the person fast-tracking the PR is the author of the PR.
188
186
- Fast-tracking is only allowed for small bug fixes, small feature changes, localisation changes, or other sorts of non-critical/highly-impacting changes that are not covered by the previous rule that allows PRs to be merged immediately.
189
-
- Fast-tracking cannot be used for updates on the `COLLABORATOR_GUIDE.md`, CONTRIBUTING.md` guide, `CODEOWNERS`, GitHub Actions or any security-impacting file or document that changes the governing policies of this repository.
187
+
- Fast-tracking cannot be used for updates on the `COLLABORATOR_GUIDE.md`, `CONTRIBUTING.md` guide, `CODEOWNERS`, GitHub Actions, or any security-impacting file or document that changes the governing policies of this repository.
190
188
- There must be no objections after a 48-hour period (Or 72 hours if the PR was authored on the weekend).
191
189
- At least one approval is required for any PR to be merged.
192
190
- Tests must be included in Pull Requests for new features or bug fixes. If any test(s) are failing, you are responsible for fixing them.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
</p>
10
10
11
11
<palign="center">
12
-
<ahref="https://nodejs.org">nodejs.org</a> website built using Nextra (Next.js) with TypeScript, SCSS and MDXv2
12
+
<ahref="https://nodejs.org">nodejs.org</a> website built using Next.js with TypeScript, SCSS and MDXv2
13
13
</p>
14
14
15
15
<palign="center">
@@ -31,7 +31,7 @@
31
31
32
32
## What is this repo?
33
33
34
-
[Nodejs.org](https://nodejs.org/) by the [OpenJS Foundation](https://openjsf.org/) is the official website for the Node.js® JavaScript runtime. This repo is the source code for the website. It is build using [Nextra](https://nextra.site), a Next.js based static site generator.
34
+
[Nodejs.org](https://nodejs.org/) by the [OpenJS Foundation](https://openjsf.org/) is the official website for the Node.js® JavaScript runtime. This repo is the source code for the website. It is build using [Next.js](https://nextjs.org) a React Framework.
0 commit comments