| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* Add main tag to article footer
* Add main tag to article header
|
|
This reverts commit 5e23604d55349b1db4e75c394fe912a01e7793fc, reversing
changes made to d5e5efd3678213aa5b6ea8ad6f410db865813dc6.
|
|
|
|
|
|
|
|
Browser will query for a favicon if none were specified.
Using emoji and SVG we can create a very light favicon that is still descriptive of the website and avoid having one more request done to the server for nothing.
|
|
This will get the site a better SEO score in Lighthouse. I believe it's used by search engines to show a description for the site? Good nonetheless. (if it should be changed lemme know)
|
|
|
|
because i find myself clicking on it and being disappointed that it isn't a link.
|
|
|
|
|
|
|
|
|
|
- Set correct title on pages (remove leading '#')
- Remove main title on recipe pages
- Put metadata at the end of articles
|
|
This way, we get dependency/smart update for free. We don't need to
rebuild all the pages everytime a new one is added. The author, date of
creation and date of revision are extracted from git information. The
index is generated automatically, so adding a recipe is literally just
adding a markdown file in src/.
The deployment system uses rsync to push only newer data to the server.
There is a tag system that you can add at the end of each recipe file.
Tag pages are generated statically that contain all recipes with a given
tag.
It introduces more HTML template files, though.
To build website, type
make build
To deploy it,
make deploy
To clean everything,
make clean
|
