My website/blog is a Phoenix application, which uses esbuild, and tailwindcss for styling, as per this guide. It has an RSS feed and supports auto-discovery.
Since tailwindcss generates thousands of CSS classes, most of which are unused by this project, we automatically purge the unneeded classes when we are running in production (but not in development).
As a convenience feature, images are displayed upside-down for users in Australia.
Using yamerl and earmark to process my markdown blog posts. I learned how to do this from this blog post. In order to integrate tailwindcss with the HTML generated by earmark, I use an earmark postprocessor to insert classes like markdown-h3, which I then style in the CSS file (using tailwindcss).
Also on my website is my resume, which is the size of a letter piece of paper and can be easily printed or downloaded as a PDF file by clicking the PDF download button. The resume is an original design written in HTML/CSS using tailwindcss.
The posts/drafts themselves on my blog are not included in the public repo, as I don’t want my draft posts read by anyone, and I’d like it to be marginally more difficult to steal my posts. As such, they are included as a separate private submodule. I also include private deployment instructions in that private submodule.
When dealing with submodules, set git config –global submodule.recurse true to make sure pulling from the parent module also pulls from the submodule. Or clone with git clone --recurse-submodules git@github.com:taylor-gl/taylor.gl.git