GithubHelp home page GithubHelp logo

00mjk / vanhelbergen-com-v3 Goto Github PK

View Code? Open in Web Editor NEW

This project forked from allardvanhelbergen/vanhelbergen-com-v3

0.0 0.0 0.0 15.27 MB

My website

Home Page: https://www.vanhelbergen.com

JavaScript 99.72% HTML 0.10% CSS 0.18%

vanhelbergen-com-v3's Introduction

AvH monogram

vanhelbergen.com

The www.vanhelbergen.com website.

πŸš€ Quick start

  • yarn

  • yarn develop

    • Your site is now running with hot reloading at http://localhost:8000!

    • Query data through http://localhost:8000/___graphql.

  • yarn storybook

    • Storybook is running to view individual components at http://localhost:6006

Tips

πŸ’« Deploy

  • yarn build

    • Run the production build to check there are no errors. You can check a deploy preview for your branch on Netlify.

    • Once the branch gets merged to master, Netlify deploys automatically to https://vanhelbergen-com.netlify.com/.

Gatsby

Made with Gatsby

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a Gatsby project.

/.
β”œβ”€β”€ /.storybook
β”œβ”€β”€ /src
    β”œβ”€β”€ /components
    β”œβ”€β”€ /content
    β”œβ”€β”€ /images
    β”œβ”€β”€ /pages
    β”œβ”€β”€ /templates
    └── /theme
β”œβ”€β”€ /static
β”œβ”€β”€ gatsby-browser.js
β”œβ”€β”€ gatsby-config.js
β”œβ”€β”€ gatsby-node.js
└── gatsby-ssr.js

Folders

  1. /.storybook: Storybook configuration files.

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

    1. __stories__: Stories for all non-component type things. Otherwise stories are kept next to the components in the components folder.

    2. /components: React components for across the site.

    3. /content: Markdown and MDX files for blogs and portfolio entries. Assets for entries should be included withing this folders.

    4. /images: Assets that need to be dynamically included in random places, e.g. global styles, and the home logo.

    5. /pages: Components under src/pages become pages automatically with paths based on their file name. Check out the pages docs for more detail.

    6. /templates: By convention, templates used across multiple pages are stored here. Contains templates for programmatically creating pages. Check out the templates docs for more detail.

    7. /theme: Contains all over-arching style files (styles for components are stored with their components). Not to be confused with Gatsby Themes.

  3. /static: If you put a file into the static folder, it will not be processed by Webpack. Instead it will be copied into the public folder untouched. Check out the assets docs for more detail.

Autogenerated folders

  1. /.cache This folder is an internal cache created automatically by Gatsby from. The files inside this folder are not meant for modification. Should be .gitignore-d.

  2. /public The output of gatsby build process will be exposed inside this folder. Should be .gitignore-d.

Files

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

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

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

  4. gatsby-ssr.js: 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.

  5. src/html.js Add it for custom configuration of default .cache/default_html.js. Check out the custom html docs for more detail.

πŸŽ“ Related documentation

πŸ‘ Thanks

I couldn't have built any of this without all the awesome people out on the web. Definitely forgetting some people here, but it's a start. :)

  • Gatsby, Greater-gatsby
  • Storybook, Styled-components, Style-dictionary
  • Bootstrap, Tailwind
  • CCS tricks, A List apart, Smashing Mag
  • Egghead.io, TylerMcGinnes, Master Games

vanhelbergen-com-v3's People

Contributors

allardvanhelbergen avatar dependabot[bot] avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.