All Projects β†’ wendelfreitas β†’ wendel.dev

wendelfreitas / wendel.dev

Licence: MIT license
My personal website and blog about software development, bleeding edge and open source πŸ”₯

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to wendel.dev

Gatsby Starter Typescript Rebass Netlifycms
My default Gatsby setup. Includes rich MDX support.
Stars: ✭ 79 (+21.54%)
Mutual labels:  styled-components, gatsby
Gatsby V2 Tutorial Starter
Gatsby V2 Starter - product of step by step tutorial
Stars: ✭ 139 (+113.85%)
Mutual labels:  styled-components, gatsby
Feathericons.com
The Feather website
Stars: ✭ 104 (+60%)
Mutual labels:  styled-components, gatsby
Bonneville
A simple, clean GatsbyJS starter for those looking to get up and running with Gatsby
Stars: ✭ 23 (-64.62%)
Mutual labels:  styled-components, gatsby
my-personal-blog-gatsby
πŸ™†πŸ»β€β™€οΈ Welcome to the source code of my personal blog. This project was created with Gatsby and GraphQL 🌼
Stars: ✭ 43 (-33.85%)
Mutual labels:  styled-components, gatsby
Mvfsillva
My personal website
Stars: ✭ 13 (-80%)
Mutual labels:  styled-components, gatsby
Gabriel Adorf Portfolio
Gabriel Adorf's personal website
Stars: ✭ 133 (+104.62%)
Mutual labels:  styled-components, gatsby
www
🦁 Source files for my personal site
Stars: ✭ 64 (-1.54%)
Mutual labels:  styled-components, gatsby
Smakosh.com
My personal website
Stars: ✭ 185 (+184.62%)
Mutual labels:  styled-components, gatsby
Felipefialho.com
😺 My personal website
Stars: ✭ 177 (+172.31%)
Mutual labels:  styled-components, gatsby
Gatsby Portfolio Dev
A portfolio for developers
Stars: ✭ 556 (+755.38%)
Mutual labels:  styled-components, gatsby
lewis-gatsby-starter-blog
A custom Gatsby starter template to start a blog or personal website.
Stars: ✭ 34 (-47.69%)
Mutual labels:  styled-components, gatsby
personal-website-react
A personal website built using Gatsby πŸš€βš›οΈ
Stars: ✭ 43 (-33.85%)
Mutual labels:  styled-components, gatsby
Gatsby Starter Typescript Deluxe
A Gatsby starter with TypeScript, Storybook, Styled Components, Framer Motion, Jest, and more.
Stars: ✭ 50 (-23.08%)
Mutual labels:  styled-components, gatsby
v2
Hack Club’s (old) website ✨
Stars: ✭ 101 (+55.38%)
Mutual labels:  styled-components, gatsby
Gatsby Admin Template
Free admin dashboard template based on Gatsby with @paljs/ui component package
Stars: ✭ 124 (+90.77%)
Mutual labels:  styled-components, gatsby
gatsby-personal-site
My personal site made with Gatsby
Stars: ✭ 31 (-52.31%)
Mutual labels:  styled-components, gatsby
Gatsby Theme Superstylin
πŸ’… A Gatsby Theme with styled-components
Stars: ✭ 165 (+153.85%)
Mutual labels:  styled-components, gatsby
gatsby-starter-apple
🍎 Gatsby blog starter kit with beautiful responsive design
Stars: ✭ 88 (+35.38%)
Mutual labels:  styled-components, gatsby
jiahao.codes
😎 Personal Website
Stars: ✭ 63 (-3.08%)
Mutual labels:  styled-components, gatsby

Wendel Freitas

Wendel Freitas

Kick off your project with this default boilerplate. This starter ships with the main Gatsby configuration files you might need to get up and running blazing fast with the blazing fast app generator for React.

Have another more specific idea? You may want to check out our vibrant collection of official and community-created starters.

πŸš€ Quick start

  1. Create a Gatsby site.

    Use the Gatsby CLI to create a new site, specifying the default starter.

    # create a new Gatsby site using the default starter
    gatsby new my-default-starter https://github.com/gatsbyjs/gatsby-starter-default
  2. Start developing.

    Navigate into your new site’s directory and start it up.

    cd my-default-starter/
    gatsby develop
  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.

    Open the my-default-starter directory in your code editor of choice and edit src/pages/index.js. Save your changes and the browser will update in real time!

🧐 What's inside?

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

.
β”œβ”€β”€ node_modules
β”œβ”€β”€ src
β”œβ”€β”€ .gitignore
β”œβ”€β”€ .prettierrc
β”œβ”€β”€ gatsby-browser.js
β”œβ”€β”€ gatsby-config.js
β”œβ”€β”€ gatsby-node.js
β”œβ”€β”€ gatsby-ssr.js
β”œβ”€β”€ LICENSE
β”œβ”€β”€ package-lock.json
β”œβ”€β”€ package.json
└── README.md
  1. /node_modules: This directory contains 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) such as 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 for.

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

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

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

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

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

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

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

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

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

πŸŽ“ 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.

πŸ’« Deploy

Deploy to Netlify

Deploy with ZEIT Now

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].