marcus-grant / brain2

My 2nd brain zettelkasten statically generated wiki using gatsby

Gatsby minimal TypeScript starter

🚀 Quick start

1. Create a Gatsby site.

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

   # create a new Gatsby site using the minimal TypeScript starter
   npm init gatsby

2. Start developing.

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

   cd my-gatsby-site/
   npm run develop

3. Open the code and start customizing!

   Your site is now running at http://localhost:8000!

   Edit src/pages/index.tsx to see your site update in real-time!

4. Learn more

   • Documentation

   • Tutorials

   • Guides

   • API Reference

   • Plugin Library

   • Cheat Sheet

🚀 Quick start (Gatsby Cloud)

Deploy this starter with one click on Gatsby Cloud:

brain2's Issues

REMINDER - Use debugger; and create branches on each issued change

• Use the debugger; keyword when stuck working on how templates are made
• Create a new feature/fix/refactor branch when making changes
  • These should probably correspond to issues created here

Add support for modified timestamps in notes sorting & metadata displays

It's too time consuming & complex to write down the timestamps for modification dates by hand. And one of the best ways to review notes is to find the ones most recently modified.
This isn't trivial. Potentially it's possible to use the gatsby-source-filesystem plugin to get modified timestamps straight from the filesystem. However, as these two articles it might be preferrable to use git's author time metadata instead as it has the dates of file modification diffs for each commit.

TLDR; Explore these options in the two above articles and try to create a node API update and associated queries and components to firstly, sort notes in the index by modification date and secondly display the modification date in the notes and index.

Maintain your own gatsby-source-git plugin

The plugin gatsby-source-git is no longer maintained, for a while. It throws silly syntax errors probably due to not keeping up to date modules. It should be somewhat easy to maintain for your own purposes when this project is more mature. Later on this or another git sourcing alternative should be explored beyond just using git submodules as was addressed in issue #1.

Refactor starter blog boilerplate to typescript

The project needs to be typescript, convert the new starter blog files to something the typescript compiler will approve of.

Convert gatsby-node.js to .ts

Some problems are arising from gatsby-node being a js file. Transform it, but try and find guides first.

Source Notes markdown files & assets from notes repo

The site generated will source markdown files from a git repo containing all the zettelkasten styled notes. Make it source this repo and show it works with some kind of site or index template.

Fix VSCode debugging of node side & Chrome side

Breakpoints aren't caught on VSCode through node for some reason. Figure out why and fix it, and optionally get the devtool chrome inspector version of this work.

Add a "tags" page & gatsby nodes to query markdown tags

First read this.
To navigate the many tags in these notes it's going to help to be able to have a tag index as a tag page in the site. It will also help to give each note page template a tag page template for sites sharing that tag.

Replace lodash func camelcase with a utility function export

Lodash is always a huge import, create your own version in a src/util/dash.ts file.

Here is the implementation lines from the lodash project of the camelcase function

Create automated deployment

Needs to be deployed at some point. Create the scripts and infra deployments necessary to make it happen.

Change page path creation to use filenames instead of titles

Using titles as a way to create page paths is confusing. Instead change it to use filenames somehow. This query I'm not sure of but it should exist. Find it and change all of the notes paths to use it instead.

Create an index page that shows all articles sorted in some order

The notes need a home or index page, create it.

Replace react-helmet with gatsby's builtin "head" component

React Helmet was from a time before Gatsby had built their own simpler, more performant and smaller in storage head API. Replace all instances of Helmet with head.

Typography closer to Wikipedia's "Linux Libertine" both sans and serif

https://en.wikipedia.org/wiki/Linux_Libertine