since github API info is being cached, is the token still necessary?

probably just needs basic browser testing (brute-forcing refreshes, maybe a basic script to spam the endpoint), but also not a huge deal if the token is still necessary

"Better" is relative here: I have no clue what kind of improvements should be made

See docs about accessing remote content

Using the blog page format for project pages doesn't quite fit: there's not spot for a repository link, upload date doesn't correspond to the project's actual time period, etc. Posts that discuss motivations or discoveries during or after the project can maybe get their own blog post that then links to the project page.

Create a shortcode to automate "Current Status" on the homepage, along with throwing the links (email, GitHub, etc.) into the config file as extra data

E.g., "Robert Yin | Blog" or "Robert Yin | Project Post Name*

For individual posts, the page title should be "Robert Yin | SECTION | PAGE" instead of "Robert Yin | PAGE".

The code ticks should probably be placed outside of the link indicators:

could use a little more information about dependencies/development steps

probably because we use the sun icon first, then replace it with the correct icon in Javascript:

See docs

would be nice to not have a bunch of expect statements while also not generically boxing the errros

currently it takes +5 minutes to build an image.

consider using an existing cache solution to cache rust compile steps, along with caching docker layers to reduce the image size.

in the future, also consider adding a nix-based solution for dependencies so that it can run on bare metal.

https://github.com/bobertoyin/personal-site/blob/88419650f4d2a942445749b6e4f4a49c1ffab624/templates/blog-section.html#L4-L12

Use the section title in the content section instead of adding it to the section content.

Home can be more succinct and about what I'm up to now, about can be more of a info dump

Add a new photo of myself to the About/Index page.

Provide some kind of page where only blog posts with the specified topic tag are shown

Tags can then link to these pages where the filter is the tag

The footer currently uses a Bulma-suggested height for footers with a lot of content, but there's no reason to make it so large for a small footer.

https://github.com/bobertoyin/personal-site/blob/98cf5e64d70c335eab2b4c34f17a20183d57f3da/templates/base.html#L29

Looks like this doesn't work as an actual href for the index/about page: perhaps @/_index.md instead?

Need a location somewhere (probably the index page) for resume and contact info.

Should be able to specify whether I am looking for opportunities or not with the resume.

https://github.com/bobertoyin/bobertoyin.com/blob/b0a630183536119e370b462cd1195f7314f17060/content/blog/personal-site-retrospective/index.md

No need to have a link to the porfolio site in the portfolio's Project card: the visitor is already on the site

Docs might help.

Leave most of the content intact, but improve the design with some of the following ideas:

• Get rid of most/all javascript for funsies; keep the idea of SSG and noJS accessibility at the forefront
• Make it look a little more newsletter-y/document-like
  • Change the font (not 100% necessary since Public Sans is solid)
  • Simplify the color scheme
  • Simplify the page layouts and element usage
• Clean up the blog section and blog pages

https://github.com/bobertoyin/personal-site/blob/452f54ae6818d0d7df754b24e286383e96c91cf4/sass/style.scss#L49

The navbar padding looks a little off on mobile (the header logo and burger menu end up coming in closer to the page than the content, giving it a weird look). Consider tweaking the left and right padding for a nicer look?

Just cache for a second or two in the rare case that the endpoint gets spammed in a really short amount of time

Probably just put them into a single tile div; no need to separate them since there's no logic for separation.

No need to specify that they aren't in any order.

Make them look less like buttons, at least for mobile.

Docs might help.

Try implementing topic tags on blog and project pages.

not really necessary, but kind of fun