ambirdsall.github.io

My personal site! Hullo!

It's a blog with a cool little sierpinski triangle doodad

On scroll or devicemove it populates a sierpinski triangle via the Chaos Game algorithm. Right now I'm just blogging about programming, but I may change that.

I also like the thought of doing something fun to expand the triangle doodad. For example, clicking on the triangle could start them flocking around using the 2d version of the boids algorithm.

🚀 Quick start

It's 2024 and only yarn will install the deps without error ¯\_(ツ)_/¯
Start a development server.
```
cd ambirdsall.github.io/
yarn develop
```
Open the source code and start editing!

Your site is now running at http://localhost:8000!
- Play around in src/pages
- Write some mdx markdown in src/posts/ and there you go! A blog post.

important bits

file	wat
`src/templates/blogTemplate.js`	the template for/layout of blog post pages
`src/components/layout.js`	the layout of the front page
`src/pages/index.js`	the front page

the rest is just Gatsby-generated framework documentation

🧐 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

/node_modules: This directory contains 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) such as your site header or a page template. src is a convention for “source code”.
.gitignore: This file tells git which files it should not track / not maintain a version history for.
.prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.
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.
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.
LICENSE: this 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.

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

ambirdsall/ambirdsall.github.io