Go to file
Ricard Illa 916a375b8d feat: ci/cd: clone recursively 2023-04-24 11:26:55 +02:00
assets feat: updated cv 2023-04-24 11:13:29 +02:00
icons icons as a submodule 2022-08-25 16:09:27 +02:00
pages feat: updated cv 2023-04-24 11:13:29 +02:00
sass donate 2021-06-27 18:56:46 +02:00
.envrc added flake direnv 2022-08-03 15:28:56 +02:00
.gitignore removed html files from tree 2022-08-03 15:37:15 +02:00
.gitmodules icons as a submodule 2022-08-25 16:09:27 +02:00
.woodpecker.yml feat: ci/cd: clone recursively 2023-04-24 11:26:55 +02:00
LICENSE added license 2022-08-03 16:08:41 +02:00
Makefile minor cosmetic adjustments to Makefile 2022-08-25 16:29:41 +02:00
README.md icons as a submodule 2022-08-25 16:09:27 +02:00
config.yaml feat: removed donate page 2023-04-24 11:13:25 +02:00
flake.lock added flake direnv 2022-08-03 15:28:56 +02:00
flake.nix added rsync to flake for deployment 2022-08-03 15:35:25 +02:00
footer.j2 complete rewrite 2021-06-27 18:22:40 +02:00
header.j2 icons as a submodule 2022-08-25 16:09:27 +02:00

README.md

Personal static frontpage

This is what I use to build my static personal frontpage accessible from the clearnet and from the tor network.

I use Jinja2 templates for the HTML content and Sass for the styling. GNU make is used to automate the build.

The result are simple static HTML files with embedded CSS.

I build two separate versions: one for the clearnet and another for the tor network. The only difference between both versions is the domain name used in the links.

Why

My site is simple enough that using a proper static site generator would have been overkill, but I still wanted something easier to maintain than directly writing HTML by hand. So a templating system like Jinja2 is a nice compromise.

Icons

I'm using the feather icons for the website navigation bar. The repo with the icons is cloned as sub-module and the needed SVGs are embedded into the HTML when the website is built.

Build dependencies

There's a zero chance than anyone other than me would want to build this, and I'm already keeping track of that using a Nix Flake. But still:

  • GNU Make: used to automate the build
  • GNU findutils: my Makefile uses find and makes use of some of its GNU extensions, so POSIX-compliant find wouldn't be enough
  • j2cli: to render the Jinja templates
  • sassc: to convert the Sass files into CSS
  • html-tidy: to validate and tidy up the resulting HTML files a bit
  • rsync: to copy the result to my public web server