Skip to content
Please note that GitHub no longer supports Internet Explorer.

We recommend upgrading to the latest Microsoft Edge, Google Chrome, or Firefox.

Learn more

/ nodejs.dev

A new Node.js resource built using Gatsby.js with React.js, TypeScript, Emotion, and Remark.
TypeScript CSS JavaScript Other
  1. TypeScript 43.1%
  2. CSS 41.4%
  3. JavaScript 14.7%
  4. Other 0.8%
Branch: master
Find file
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Open in Desktop Download ZIP

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio

If nothing happens, download the GitHub extension for Visual Studio and try again.

@keywordnew @jonchurch
keywordnew and jonchurch Notes for meeting on 2020-01-30 (#391) 
* Create 2020-01-30.md

Thank you for taking notes, @jonchurch and @SMotaal 👍🏽

* fix: Tweak meeting minutes to fix md linting errors

Co-authored-by: Jonathan Church <me@jonchurch.com>
Latest commit aa613a0 Jan 31, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github build(deps): bump handlebars in /.github/action/result-poster (#384) Dec 28, 2019
meetings
src doc: add MEAN and Loopback (#372) Dec 24, 2019
style-guide fix: remark-lint minor suppressed rules (#351) Dec 23, 2019
test feat: Show outline on keyboard nav and style outline to match theme (#… May 26, 2019
.editorconfig chore: Add .editorconfig. Feb 19, 2019
.firebaserc build: Auto deploy via build + firebase. Feb 1, 2019
.gitignore fix: Initialize with null to assign a deliberate non-value (#178) Mar 7, 2019
.nvmrc
.prettierignore refactor: Simplify logic to mark navigation items as done (#197) Mar 14, 2019
.prettierrc feat: New Prettier rules. Mar 1, 2019
.remarkrc
.travis.yml chore: Upgrade dependencies (#268) Jun 22, 2019
CODE_OF_CONDUCT.md fix: remark-lint prohibited-strings (#348) Oct 18, 2019
CONTRIBUTING.md fix: remark-lint minor suppressed rules (#351) Dec 23, 2019
LICENSE Update LICENSE (#205) Mar 28, 2019
ModerationPolicy.md fix: remark-lint prohibited-strings (#348) Oct 18, 2019
README.md fix: remark-lint minor suppressed rules (#351) Dec 23, 2019
cloudbuild-deploy.yaml build: replace grc images w/ official images (#341) Oct 21, 2019
cloudbuild.yaml build: replace grc images w/ official images (#341) Oct 21, 2019
commitlint.config.js feat: Update commitlint config and docs to disallow a period at the e… Mar 2, 2019
empty.env feat: Initial commit of Gatsby project. Jan 17, 2019
firebase.json Refactoring Site Creation and Additions (#157) Mar 7, 2019
gatsby-config.js chore: Update eslint-utils (#301) Sep 1, 2019
gatsby-node.js fix: Initialize with null to assign a deliberate non-value (#178) Mar 7, 2019
package.json chore: bump remark-preset-lint-node to 1.10.1 (#356) Dec 20, 2019
test-preprocessor.js chore: Add testing framework. Feb 20, 2019
test-setup.js chore: Run prettier/tslint in ci (#97) Mar 8, 2019
tsconfig.json feat: Initial commit of Gatsby project. Jan 17, 2019
tslint.json chore: Run prettier/tslint in ci (#97) Mar 8, 2019
yarn.lock build(deps): bump handlebars from 4.1.2 to 4.5.3 (#385) Dec 28, 2019

README.md


Nodejs.dev

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



You can find the latest Figma design protype here.

🚀 Get Started

  1. Install Yarn (if Yarn Package Manager is not available on your machine).

    Yarn has an installation guide for your specific configuration. Happy knitting!

  2. Install dependencies.

    # install the dependencies
yarn install

  3. Start developing.

    # "start": "gatsby develop"
yarn start

  4. 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 the top-level files and directories you'll see in a Gatsby project.

.
├── node_modules
├── src
├── .gitignore
├── .nvmrc
├── .prettierrc
├── empty.env
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
├── README.md
├── tsconfig.json
├── tslint.json
└── yarn.lock

  1. /node_modules: The directory where all of the modules of code that your project depends on (npm packages) are automatically installed.

  2. /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.”

  3. .gitignore: This file tells git which files it should not track/not maintain a version history.

  4. .nvmrc: NVM configuration so packages work as they should

  5. .prettierrc: This is a configuration file for a tool called Prettier, which is a tool to help keep the formatting of your code consistent.

  6. empty.env: Rename to .env and set your Contentful API key

  7. gatsby-browser.tsx: 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.

  8. 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).

  9. 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.

  10. gatsby-ssr.tsx: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

  11. LICENSE: Gatsby is licensed under the MIT license.

  12. 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).

  13. 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.

  14. README.md: A text file containing useful reference information about your project.

  15. tsconfig.json: Config file for TypeScript

  16. tslint.json: TS Lint configuration file

  17. yarn.lock: Yarn is a package manager alternative to npm. You can use either yarn or npm, though all of the Gatsby docs reference npm. This file serves essentially the same purpose as package-lock.json, just for a different package management system.

📝 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

@nodejs/website-redesign

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

Any member of the website-redesign initiative attached to the current phase of the project will be added to a future phase as the project moves forward.

Any member of the website-redesign initiative who prefers to begin contributing at a specific future phase is welcome to make a PR adding their handle to that phase.

Information Gathering

IA / UX Planning

UI Design and Content Creation

Site Development <-- current phase

Links

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

You can’t perform that action at this time.