RazorX
https://github.com/evansosenko/evansosenko.com
Going back to basics and having zero external dependencies is quite enjoyable. Understanding how Hugo templates, themes, and content all work together was more complicated than I originally expected, but they have build a good system. Hopefully this helps anyone looking to get started.
If you are hacking on this today, you can use this starter repo to get a LaTeX project setup that builds and publishes your document with GitHub Actions: https://github.com/makenew/latex-project
A masterpiece that formalizes all of the handway bits you learned in physics. Will change your perspective forever.
Thermodynamics and an Introduction to Thermostatistics Herbert B. Callen
The only book that actually taught me thermo. Everything else was just confusing garbage.
Tends to be the most useful in-code comment because if someone comes along and "helps" to refactor the "weird" code, they could accidentally undo the workaround and get stuck in the same loop the original author was in.
My immediate thought was that some order processing step somewhere is not idempotent.
Best to Auth0! I really hope you can maintain your company culture and excellence, but I can't risk my business on that now.
Included: JS and Python package /microservice / serverless projects; Serverless Benthos; LaTeX paper; zsh and neovim config.
Reasons why this approach is successful
1. Most project generators don't provide a simple way to keep boilerplate updated. These projects leverage git merge and git diff which is designed for the task. So keeping all the generated projects updated as tools evolve is actually possible.
2. Fork friendly: you can fork and customize these repos to create your own personalized skeleton project, and still merge updates from the original.
3. These projects give you a working CI deployment.
4. The projects themselves are REAL working examples which are deployed / published.
5. Isolated boilerplate so any issues with tooling can be verified, tested, and upgraded independently.
I've been using Bespoke.js [1]. Minimal core, and drop in plugins as needed. I also made a skeleton for quickly making new decks [2].
I want to avoid vendor lock-in to something like chef for this. The idea is that everything is either defined in a tool-agnostic config file, and bootstrapping / installing / updating the dependencies is handled by simple shell scripts. Down the road I can always swap out the tooling (bower, config_curator, archutil) without updating code in my repos since state is defined as data.
I don't like syslinks or putting ~/ under git as I don't want my working tree to affect my dotfiles until I run an "install" command.
I would love to see some kind of namespacing: something that would come with organization-specific cookbooks. Really, when I said "don't belong on the main community site" I really mean "don't belong in the current global namespace."
I use a subdomain of that main domain as the User Pages site.
How should DNS be setup and how should the CNAME files on GitHub read?
As an example, the domain on the left should load the site normally hosted from the location on the right:
example.com -> username.github.io/blog
io.example.com -> username.github.io
Is this possible?
Once I put the paper on the arXiv I open sourced everything and made a portal with links to all the repos. The only thing missing is the repo for the source of the submitted paper which I'll add once it makes it through APS review.
Here is my work if you're interested or have any feedback: