How content becomes website.
Original documents are in org/_posts and get rendered into jekyll/_posts. The code for doing that is in my .emacs. There’s also a bit of code there for rendering the inter-post links that might be of interest.
Jekyll headers and any template code are enclosed in #+BEGIN_EXPORT html org tags so that they are rendered exactly in the resulting files. An example is here.
Much of the effort to get org working with jekyll relied on the tutorial here.
Some javascript demos that I’ve coded over the years are included as git submodules. As long as the demo repos have a index.html simply adding the submodule (and including it in the jekyll directory structure) is enough to get a live version on the website. I’ve been manually updating the Demo landing page with the links.
In order to accomplish the github backlinks I scripted a tiny plugin that runs a git command and injects the result into a jekyll variable.
The theming is accomplished with the files that are in jekyll/_includes, jekyll/_layouts, and jekyll/_sass. The general structure of these were cribbed from the wonderful minima. Minima had too much stuff for my liking, so I removed most of it.
I used a few top-level tachyons concepts to accomplish column widths and font sizes.
The font is Latin Modern from GUST e-foundry.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent