based.cooking.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Lines
*	Add a lightweight inline favicon (#256)	Clément	2021-03-21	-0/+1
\| \| \| \|	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.
*	add meta description tag (#339)	Alexander Johansen	2021-03-21	-0/+1
\| \| \|	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)
*	Make site scale properly on mobile	Rikard Karlsen	2021-03-18	-0/+1
\|
*	responsive css: multi-column list on wide screens	Luke Smith	2021-03-15	-2/+2
\|
*	update footer	Sylvain Gauthier	2021-03-15	-3/+4
\|
*	get ready for merge	Sylvain Gauthier	2021-03-15	-1/+2
\|
*	add list of tag links at the end of each recipe	Sylvain Gauthier	2021-03-15	-0/+3
\|
*	fix	Sylvain Gauthier	2021-03-15	-8/+11
\| \| \| \| \| \|	- Set correct title on pages (remove leading '#') - Remove main title on recipe pages - Put metadata at the end of articles
*	use a clean Makefile system to build/deploy site	Sylvain Gauthier	2021-03-15	-0/+32
	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