A new Node.js resource built using Gatsby.js with React.js, TypeScript, and Remark.

Overview


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

  1. Install dependencies.

    # install the dependencies
    npm install
  2. Start developing.

    # "start": "gatsby develop"
    npm start
  3. 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
  1. .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.

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

  3. /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."

  4. /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.

  5. /test: Tests for this projects are stored in this directory. This project uses Jest as it's testing framework.

  6. /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.

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

  8. .nvmrc: nvm configuration so packages work as they should

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

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

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

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

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

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

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

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

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

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

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
IA / UX Planning
UI Design and Content Creation
Site Development

Links

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

Comments
  • Removing/replacing the

    Removing/replacing the "learn" section tutorial

    In the Website Redesign meeting today, it was agreed that:

    1. The expansive Learn section is not appropriate for the site.
    2. The site should have a minimal getting-started page or two which might end with links to the OpenJS Foundation free Node.js training materials and/or a small number of other official/canonical/unimpeachably-reputable links.

    We can leave the Learn material in place for people who have bookmarked it, but we shouldn't link to it. (Or is this site considered beta right now so it's OK to remove things and have them return 404?)

    Infrastructure planning 
    opened by Trott 43
  • feat: Adding google calendar

    feat: Adding google calendar

    Description

    Adds calendar page to Nodejs.dev, similar to https://calendar.google.com/calendar/u/0/[email protected]oogle.com

    Related Issues

    Addresses #883

    Completed now, there will be follow-up worked defined in the task list for the above issue

    wr-agenda 
    opened by soytumadre 37
  • feat: Modified Gatsby Configuration for querying markdown blogs

    feat: Modified Gatsby Configuration for querying markdown blogs

    Description

    Updated the gatsby-node.js file to support querying for blog markdown files in /content/blog directory. I also added a sample blog accessible at [URL]/blog/2021/03/19/intro-to-nodejs.

    For testing, I decided to extend and reuse the existing Article component used in /learn pages. Please let me know if it's okay or I'll have to create separate components for blog pages.

    Related Issues

    Addresses #1152

    opened by manishprivet 37
  • New/landing page

    New/landing page

    Description

    Started working on landing page implementation. Please review it, because any feedback will be useful.

    • using scss modules for styling
    • refactored file structure

    https://www.loom.com/share/68d6186bfd3c4abcabe80e2df81249c1

    opened by alexandrtovmach 32
  • feat(i18n): introduce localisation capabilities and language toggle

    feat(i18n): introduce localisation capabilities and language toggle

    Check List

    • [x] I have read the Contributing Guidelines and made commit messages that follow the guideline.
    • [x] I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
      • This is important as most of the cases your code changes might not be correctly linted
    • [x] I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
    • [x] I have checked that the build works locally and that npm run build and npm run build-storybook work fine.
    • [x] I've covered new added functionality with unit tests if necessary.

    Description

    This PR introduces several changes within the nodejs.dev codebase. By introducing full Internationalization and Localization support. The following changes and introductions were done:

    • Introduced two plugins gatsby-theme-i18n and gatsby-theme-i18n-react-intl
      • Those respectively introduce the support of Localized pages and MDX/Markdown pages and content, the introduction of language prefixes in the website and finally, the support of FormatJS/ReactIntl.
      • When a page doesn't contain a translation for the current language, it falls back to the default language version of that page
      • The gatsby-theme-i18n was patched since it is kinda unmaintained, and we were required to patch it to work with some of our requirements.
        • The patches allow it to redirect pages without the language prefixes to the same page with a language prefix
        • It also allows the gatsby-plugin-offline to work
    • Introduced a Language Dropdown that easily allows switching between Languages
    • Introduced a config.json file for i18n with multiple Language metadata.
      • Note.: Most of the languages are disabled and miss correct metadata; this can be populated later by the @nodejs/i18n team.
    • Introduced a helper that easily allows to wrap Article pages into Localized GraphQL data and render them without duplicating code. (Most of the pages (src/pages) were copy-paste and simple changes. This helper creates uniformity and allows us to create new pages easily and have a centralized Layout for Article pages (src/components/Layout/article.tsx)
    • Created a helper that keeps track of the user's language choices and redirects them to the stored language of preference. This hook also attempts to redirect them initially to the language their system/browser prefers.
      • TL;DR if the browser language is Spanish, and they open the page without the language prefix, it will redirect to the Spanish version of our page if we support the language.
    • This PR introduced several micro performances, styles and logic fixes to the Nodejs.dev website, whose most are related to the introduction of the Node.js.dev website
    • This PR also moved all the content pages adding a prefix on the file extension to en.md
      • Markdown files now require this suffix to inform the engine which language they belong.

    Screenshots

    image image image

    Related Issues

    Closes #2568 Closes #254 Closes #1555 Closes #274

    enhancement i18n 
    opened by ovflowd 31
  • feat(docs): introduced initial version of api docs system

    feat(docs): introduced initial version of api docs system

    Description

    This PR introduces an initial version of a script that retrieves the Markdown files for each API version of the current non-EOL and non-Pending Node.js API docs.

    This PR introduces the mechanisms that modifies the <!-- YAML --> API tags into an MDX Component for rendering the Metadata as in https://nodejs.org/api.

    It also introduces mechanisms to create the Frontmatter of the Codebase.

    This PR will also replace the current docs.tsx page into a template and remove all its garbage code.

    Related Issues

    Closes https://github.com/nodejs/nodejs.dev/issues/2611 Closes https://github.com/nodejs/nodejs.dev/issues/2630

    Check List

    • [ ] I have read the Contributing Guidelines and made commit messages that follow the guideline.
    • [ ] I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
      • This is important as most of the cases your code changes might not be correctly linted
    • [ ] I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
    • [ ] I have checked that the build works locally and that npm run build work fine.
    • [ ] I've covered new added functionality with unit tests if necessary.
    enhancement docs 
    opened by ovflowd 30
  • Website Wireframes

    Website Wireframes

    Hey everyone!

    In the previous meeting we left with an action item to start iterating on site wireframes so we can have more detailed conversations about site structure and IA, especially now that https://github.com/nodejs/website-redesign/issues/4 has defined the site structure in broad strokes. I'm excited to help kick that off 🎉

    This weekend I've taken the time to knock out initial wireframe layouts of most of the major top-level sections of the site for us to start iterating on (Ironically the only top-level page I haven't gotten to yet is the "Community" page 😅). The wireframes are living on InVision for easy design feedback, I've already left a few comments and open questions scattered throughout to help kickstart conversation. Feel free to click through and explore!

    If anyone else has been working on wireframes, please share them here! We can discuss how to reconcile differences and work to converge on a single source-of-truth for the project.

    InVision Project:

    https://invis.io/SJG12D028NX#/281335816_Home

    Note: Keep in mind if you comment, that wireframes are iterating on IA, general site structure and broad user experiences! In this phase, wherever/whenever we are reviewing wireframes, please keep feedback focused on these topics and not on visual design!

    Proposal for Moving Forward:

    If the above wireframes feel like a solid foundation to start working off of, I'd like to propose the team move forward by leaving comments, and have a more focused discussion, over on the InVision board. We can continue to iterate there until we have consensus on a content-complete, robust wireframe to pass off for whoever is going to do the high-fidelity design pass.

    I'm happy to volunteer as idea-synthesizer throughout the iteration process and integrate any and all feedback left on the InVision board (that appears to have reached consensus) back into the wireframe for further iterations. However, I'm also more than happy to share the source Sketch project with anyone who would like to help with the pixel pushing! We will just have to coordinate closely with changes – unfortunately true collaborative design software is difficult to come by...

    Again, if anyone else has been working on wireframes, please share them here! We can all discuss how to reconcile differences and work to converge on a single source-of-truth for the project.


    Let me know your thoughts on both the wireframes, and how you believe is best to move forward into this next phase – excited to finally be looking at mock ups!

    opened by amiller-gh 30
  • npm start throwing error

    npm start throwing error

    URL:

    https://nodejs.dev

    Browser Name:

    n/a

    Browser Version:

    n/a

    Operating System:

    Windows 11

    How to reproduce the issue:

    I synced my fork with the main repo, then did git pull on main. I created a new branch and ran npm start.

    It gives the following error

    
    [2824:00000272A4050CD0]    67425 ms: Mark-sweep (reduce) 1933.7 (2061.8) -> 1915.7 (2039.0) MB, 191.4 / 0.1 ms  (average mu = 0.203, current mu = 0.150) allocation failure GC in old space requested
    [2824:00000272A4050CD0]    67702 ms: Mark-sweep (reduce) 1935.2 (2058.3) -> 1917.0 (2029.6) MB, 242.4 / 0.1 ms  (average mu = 0.161, current mu = 0.124) allocation failure GC in old space requested
    
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
     1: 00007FF706657A1F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+114207
     2: 00007FF7065E6096 DSA_meth_get_flags+65542
     3: 00007FF7065E6F4D node::OnFatalError+301
    15: 00007FF706924C8B v8::internal::WasmTableObject::Fill+603
    16: 00007FF706F25086 v8::String::Utf8Length+22
    17: 00007FF706604DB7 v8::internal::Malloced::operator delete+17479
    18: 00007FF706ED5CA6 v8::internal::Builtins::code_handle+172790
    19: 00007FF706ED5899 v8::internal::Builtins::code_handle+171753
    20: 00007FF706ED5B5C v8::internal::Builtins::code_handle+172460
    21: 00007FF706ED59C0 v8::internal::Builtins::code_handle+172048
    22: 00007FF706FA90C1 v8::internal::SetupIsolateDelegate::SetupHeap+494673
    23: 00000272A77889E0
    

    I tried to delete the cache which didn't work. I then deleted my local repo and re-cloned it, ran npm install and then npm start and it still gives the same issue.

    bug build Infrastructure 
    opened by EmmaDawsonDev 28
  • Use SVG Images for Node.js Features

    Use SVG Images for Node.js Features

    This PR replaces the blurred images on the homepage with free SVG Images from Icons8 using their free license.

    BEFORE

    image

    AFTER (Now with SVG images)

    image

    P.S. Ignore the button color conflict which has already been handled in #747.

    opened by ahmadawais 28
  • Allow new staging domain and improve experience of previews

    Allow new staging domain and improve experience of previews

    Did some improvements to staging based on feedback from #587

    Some highlights

    • staging.nodejs.dev now works... no need to include the gcs url
    • index.html is no longer required in the url (I figured out the config I had wrong there)
    • http -> https redirect in place for staging
    • No more gcbrun
    • Auto runs on all PRs
    • Should work for forks
    • Upgrade to Node.js 12 for build

    One more thing that is nice, we could add an additional action to make staging.nodejs.dev be whatever is on the staging branch... I'll open a separate PR for that.

    opened by MylesBorins 27
  • Refactoring Site Creation and Additions

    Refactoring Site Creation and Additions

    Hi all,

    happily we improved our codebase in last few days quite a lot! Though all the problems I run into while working on bugs led me to prepare this big refactoring PR. Please take a look and let me know if there is any room for improvements or if you have any concerns about new structure.

    PS: Sorry about big PR I needed to approve my approach in most of the cases. After having all the code together I didn’t split them up again. :|

    Closes: #23 #106 #24

    opened by LaRuaNa 27
  • feat(I18n): add possibility to translate UpcomingReleasesItem

    feat(I18n): add possibility to translate UpcomingReleasesItem

    Description

    Adding the possibility to translate UpcomingReleasesItem

    Related Issues

    No related issue

    Check List

    • [X] I have read the Contributing Guidelines and made commit messages that follow the guideline.
    • [ ] I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
      • This is important as most of the cases your code changes might not be correctly linted
    • [x] I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
    • [x] I have checked that the build works locally and that npm run build work fine.
    • [ ] I've covered new added functionality with unit tests if necessary.
    opened by AugustinMauroy 3
  • Node Status column on french transalation shows english word for `pending`

    Node Status column on french transalation shows english word for `pending`

    URL:

    https://nodejs.dev/fr/download/

    Browser Name:

    Firefox

    Browser Version:

    Firefox 108 on Ubuntu Linux

    Operating System:

    Ubuntu 20.04

    How to reproduce the issue:

    Expected a french translation for the items in status column but found English translation for pending

    enhancement i18n 
    opened by HassanBahati 4
  • build(deps-dev): Bump @typescript-eslint/parser from 5.45.1 to 5.47.1

    build(deps-dev): Bump @typescript-eslint/parser from 5.45.1 to 5.47.1

    Bumps @typescript-eslint/parser from 5.45.1 to 5.47.1.

    Release notes

    Sourced from @​typescript-eslint/parser's releases.

    v5.47.1

    5.47.1 (2022-12-26)

    Bug Fixes

    • ast-spec: correct some incorrect ast types (#6257) (0f3f645)
    • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

    v5.47.0

    5.47.0 (2022-12-19)

    Features

    • eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

    v5.46.1

    5.46.1 (2022-12-12)

    Note: Version bump only for package @​typescript-eslint/typescript-eslint

    v5.46.0

    5.46.0 (2022-12-08)

    Bug Fixes

    • eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

    Features

    • eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)
    Changelog

    Sourced from @​typescript-eslint/parser's changelog.

    5.47.1 (2022-12-26)

    Note: Version bump only for package @​typescript-eslint/parser

    5.47.0 (2022-12-19)

    Note: Version bump only for package @​typescript-eslint/parser

    5.46.1 (2022-12-12)

    Note: Version bump only for package @​typescript-eslint/parser

    5.46.0 (2022-12-08)

    Note: Version bump only for package @​typescript-eslint/parser

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 1
  • build(deps): Bump gatsby-plugin-catch-links from 4.24.0 to 4.25.0

    build(deps): Bump gatsby-plugin-catch-links from 4.24.0 to 4.25.0

    Bumps gatsby-plugin-catch-links from 4.24.0 to 4.25.0.

    Changelog

    Sourced from gatsby-plugin-catch-links's changelog.

    Changelog: gatsby-plugin-catch-links

    All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

    5.3.0 (2022-12-13)

    🧾 Release notes

    Note: Version bump only for package gatsby-plugin-catch-links

    5.2.0 (2022-11-25)

    🧾 Release notes

    Note: Version bump only for package gatsby-plugin-catch-links

    5.1.0 (2022-11-22)

    🧾 Release notes

    Note: Version bump only for package gatsby-plugin-catch-links

    5.0.0 (2022-11-08)

    🧾 Release notes

    Chores

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 1
  • build(deps): Bump gatsby-plugin-webfonts from 2.2.2 to 2.3.2

    build(deps): Bump gatsby-plugin-webfonts from 2.2.2 to 2.3.2

    Bumps gatsby-plugin-webfonts from 2.2.2 to 2.3.2.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 1
  • build(deps): Bump gatsby-transformer-yaml from 4.24.0 to 4.25.0

    build(deps): Bump gatsby-transformer-yaml from 4.24.0 to 4.25.0

    Bumps gatsby-transformer-yaml from 4.24.0 to 4.25.0.

    Changelog

    Sourced from gatsby-transformer-yaml's changelog.

    Changelog: gatsby-transformer-yaml

    All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

    5.3.0 (2022-12-13)

    🧾 Release notes

    Note: Version bump only for package gatsby-transformer-yaml

    5.2.0 (2022-11-25)

    🧾 Release notes

    Note: Version bump only for package gatsby-transformer-yaml

    5.1.0 (2022-11-22)

    🧾 Release notes

    Note: Version bump only for package gatsby-transformer-yaml

    5.0.0 (2022-11-08)

    🧾 Release notes

    Chores

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 1
Starter-gatsby-blog - Gatsby starter for a Contentful project from the community.

Contentful Gatsby Starter Blog Create a Gatsby blog powered by Contentful. Static sites are scalable, secure and have very little required maintenance

Priya Chakraborty 0 Jan 29, 2022
Validate your Markdown frontmatter data against a JSON schema — remark-lint rule plugin

remark-lint-frontmatter-schema Validate Markdown frontmatter YAML against an associated JSON schema with this remark-lint rule plugin. Supports: Types

Julian Cataldo 20 Dec 10, 2022
This tool allows you to draw up plans for facilities from Foxhole's new Inferno update. It takes power and resource needs into account to help you efficiently design your facilities.

Foxhole Facility Planner This tool allows you to draw up plans for facilities from Foxhole's new Inferno update. It takes power and resource needs int

Brandon Ray 23 Dec 23, 2022
This document introduces an early implementation of the Node-RED runtime that runs on resource-constrained microcontrollers (MCUs).

Node-RED MCU Edition Copyright 2022, Moddable Tech, Inc. All rights reserved. Peter Hoddie Updated June 25, 2022 Introduction This document introduces

Peter Hoddie 53 Jan 3, 2023
React Gatsby static web tool for generative artists working on token based NFT artwork (ex: Artblocks)

token-art-tools React Gatsby static web tool for generative artists working on token/hash based NFT artwork (ex: Artblocks) https://ctrlshiftmake.gith

Owen Moore 71 Dec 15, 2022
A minimal e-commerce store using Gatsby, SANITY, Stripe, Use-Shopping-Cart and Netlify

?? Gatsby Starter Stripemart Like a supermarket but for Stripe. No ongoing monthly costs. Perfect for artists, creators and independent builders doing

Eric Howey 26 Nov 14, 2022
GatsbyConf - Decoupling Drupal Using Gatsby: A Crash Course workshop

GatsbyConf - Decoupling Drupal Using Gatsby: A Crash Course workshop

Octahedroid 7 Sep 29, 2022
Palaemon is an open-source developer tool for monitoring health and resource metrics of Kubernetes clusters and analyzing Out of Memory (OOMKill) errors

Palaemon ?? ?? An Electron based developer tool for Kubernetes cluster monitoring and error analysis Palaemon is a Greek, child sea-god who came to ai

OSLabs Beta 99 Dec 28, 2022
PxLoader is a simple JavasScript library for creating preloaders and resource downloaders for HTML5 apps.

PxLoader is a Javascript library that helps you download images, sound files or anything else you need before you take a specific action on your site

Pixel Lab 1.1k Dec 30, 2022
A Node.js REST API example built with Express and Typescript that can be used as template for creation of new servers.

api-example-firebase-nodejs A Node.js REST API example built with Express and Typescript that can be used as template for creation of new servers. The

Rodrigo João Bertotti 5 Nov 25, 2022
MLPleaseHelp is a simple ML resource search engine.

README MLPleaseHelp is a simple ML resource search engine. How To Use You can use this search engine right now at https://jgreenemi.github.io/MLPlease

Joseph Greene 5 Jan 20, 2021
Utility for collecting resource-based policies from an AWS account

AWS resource-based policy collector This library aims to collect resource-based policies from an AWS account. NOTE: This library does not cover all AW

Will Dady 22 Dec 5, 2022
Cache Solidjs resources by key (derived from the resource source)

Solid Cached Resource (Experimental) Create a solid resource attached to a cached state by a unique key. Heavily inspired by react-query, but for soli

Yonatan 27 Dec 31, 2022
Sanity plugin for viewing resources which reference a particular resource.

@indent-oss/sanityio-referenced-by Plugin to see which documents reference a particular document referenced-by-sanityio.mov Video Alt Text: Demonstrat

Indent 16 Nov 2, 2022
JS Cloudimage 360 View - A simple, interactive resource that can be used to provide a virtual tour of your product

JS Cloudimage 360 View - A simple, interactive resource that can be used to provide a virtual tour of your product

Scaleflex 1.9k Jan 7, 2023
A build plugin to integrate Gatsby seamlessly with Netlify

Essential Gatsby Plugin This build plugin is a utility for supporting Gatsby on Netlify. To support build caching and Gatsby functions on Netlify, you

Netlify 72 Dec 27, 2022
GatsbyContactFormBasedOnFormikAnalysis - This is example contact form for gatsby framework.

Gatsby minimal starter ?? Quick start Create a Gatsby site. Use the Gatsby CLI to create a new site, specifying the minimal starter. # create a new Ga

Bart 1 Jan 2, 2022
Gatsby-Formik-contact-form-with-backend-panel - Full working contact form with backend GUI panel.

Gatsby minimal starter ?? Quick start Create a Gatsby site. Use the Gatsby CLI to create a new site, specifying the minimal starter. # create a new Ga

Bart 1 Jan 2, 2022
Gatsby-starter-minimal-blog - Typography driven, feature-rich blogging theme with minimal aesthetics.

Gatsby-starter-minimal-blog - Typography driven, feature-rich blogging theme with minimal aesthetics. Includes tags/categories support and extensive features for code blocks such as live preview, line numbers, and line highlighting.

Priya Chakraborty 0 Jan 29, 2022