Nodejs.dev

Nodejs.dev site built using Gatsby.js with React.js, TypeScript, SCSS, and Remark.

You can find the latest Figma design protype here.

🚀 Get Started

Install dependencies.
```
# install the dependencies
npm install
```
Start developing.
```
# "start": "gatsby develop"
npm start
```
Open the source code and start editing!

Your site is now running at http://localhost:8000!

Note: You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.

🧐 What's inside?

A quick look at some of the top-level files and directories found in this project.

.
├── .github
├── .storybook
├── meetings
├── node_modules
├── src
├── stories
├── style-guide
├── test
├── util-node
├── .editorconfig
├── .eslintignore
├── .eslintrc.js
├── .firebaserc
├── .gitignore
├── .nvmrc
├── .prettierignore
├── .prettierrc
├── .remarkrc
├── cloudbuild-deploy.yaml
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── empty.env
├── firebase.json
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── LICENSE
├── ModerationPolicy.md
├── OKR.md
├── package-lock.json
├── package.json
├── README.md
├── test-preprocessor.js
├── test-setup.js
└── tsconfig.json

.storybook: This directory contains configuration files so the storybook package works as it should. Storybook is used to build the individual UI components in this project.
/node_modules: The directory where all of the modules of code that your project depends on (npm packages) are automatically installed.
/src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser), like your site header, or a page template. "Src" is a convention for "source code."
/stories: This directory contains stories for UI components used in this project. You can find out what a story is here. Also, you can run them locally using npm run storybook.
/test: Tests for this projects are stored in this directory. This project uses Jest as it's testing framework.
/util-node: Custom utility functions that require nodeJs to run can be stored in files inside this directory. An example is the create-slug function in the createSlug.js file that generates unique slugs for articles.
.gitignore: This file tells git which files it should not track/not maintain a version history.
.nvmrc: nvm configuration so packages work as they should
.prettierrc: This is a configuration file for a tool called Prettier, which is a tool to help keep the formatting of your code consistent.
empty.env: Rename to .env and set your Contentful API key
gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.
gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you'd like to include, etc. (Check out the config docs for more detail).
gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.
LICENSE: Gatsby is licensed under the MIT license.
package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won't change this file directly).
package.json: A manifest file for Node.js projects, which includes things like metadata (the project's name, author, etc.). This manifest is how npm knows which packages to install for your project.
README.md: A text file containing useful reference information about your project.
tsconfig.json: Config file for TypeScript

📝 Data Sources

This repository contains no documentation content. Content is pulled from across the Node.js GitHub Org, Contentful, and other data sources and stitched together into a cohesive website.

src/documentation

The src/documentation directory currently contains all the getting started content.

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.
To dive straight into code samples head to our documentation. In particular, check out the "Guides", API reference, and "Advanced Tutorials" sections in the sidebar.

🏛 Governance

This initiative adopts the general Node.js Code of Conduct, as well as its own Contributing Guidelines.

Meetings

Meeting notes from past meetings are maintained for later reference. Query issues for "Meeting" to find future meetings.

Summary / Current Status

Our current focus is on site development. Development is happening in the nodejs.dev repo. This repo continues to be the hub for the redesign initiative.

Team

Any person who wants to contribute to the initiative is welcome! Please read Contributing Guidelines and join the effort 🙌.

This repo is managed by the nodejs.dev. Members of the nodejs website team also have commiter rights on the repo.

The nodejs.dev team

@ahmadawais - Ahmad Awais ⚡️
@alexandrtovmach - Alexandr Tovmach
@amiller-gh - Adam Miller
@argyleink - Adam Argyle
@benhalverson - Ben Halverson
@BeniCheni - Benjamin Chen
@codeekage - Abraham Jr. Agiri
@darcyclarke - Darcy Clarke
@designMoreWeb - Divy Tolia
@imbhargav5 - Bhargav Ponnapalli
@jemjam - j'em bones
@joesepi - Joe Sepi
@jonchurch - Jonathan Church
@kasicka - Zuzana Svetlíková
@keywordnew - Manil Chowdhury
@LaRuaNa - Onur Laru
@maddhruv - Dhruv Jain
@manishprivet - Manish Kumar
@marcustisater - Marcus Tisäter
@mbj36 - Mohit kumar Bajoria
@MylesBorins - Myles Borins
@ogonzal87 - Oscar Gonzalez
@ollelauribostrom - Olle Lauri Boström
@pierreneter - Nguyễn J Huỳnh Long
@sagirk - Sagir Khan
@saulonunesdev - Saulo Nunes
@skllcrn - Christopher
@SMotaal - Saleh Abdel Motaal
@timothyis - Timothy
@tstreamDOTh - T Thiyagaraj
@ZYSzys - ZYSzys

The Website Redesign Teams

This repo originated as "The Website Redesign" strategic initiative under the Node.js Community Community. Below are various teams and people that participated in that process.

Information Gathering

@amiller-gh - Adam Miller
@codeekage - Agiri Abraham JNR
@darcyclarke - Darcy Clarke
@maddhruv - Dhruv Jain
@fhemberger - Frederic Hemberger
@JonahMoses - Jonah Moses
@chowdhurian - Manil Chowdhury
@oe - Olivia Hugger
@bnb - Tierney Cyren
@timothyis - Timothy

IA / UX Planning

@oe - Olivia Hugger
@fhemberger - Frederic Hemberger
@bnb - Tierney Cyren
@timothyis - Timothy
@JonahMoses - Jonah Moses
@amiller-gh - Adam Miller
@emilypmendez - Emily Mendez
@darcyclarke - Darcy Clarke
@maddhruv - Dhruv Jain
@chowdhurian - Manil Chowdhury
@codeekage - Agiri Abraham JNR
@add1sun - Addison Berry
@Qard - Stephen Belanger
@watilde - Daijiro Wachi
@tolmasky - Francisco Ryan Tolmasky I
@milapbhojak - Milap Bhojak
@devamaz - Ahmad Abdul-Aziz

UI Design and Content Creation

@amiller-gh - Adam Miller
@bnb - Tierney Cyren
@codeekage - Agiri Abraham JNR
@chowdhurian - Manil Chowdhury
@maddhruv - Dhruv Jain
@milapbhojak - Milap Bhojak
@tolmasky - Francisco Ryan Tolmasky I
@iNidAName - Hassaan Sani
@abedzantout - Abdul Rahman Zantout
@AliObaji - Ali Obaji
@AhmadAwais - AhmadAwais

Links

Community Committee Code of Conduct Contributing Guidelines Meeting Notes Query issues for "Meeting"

parthlaw/nodejs.dev