| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
The previous ones looked kind of dull. These are from my gruber-darker
rainbow-delimiters theme.
|
|
|
|
|
|
|
|
This makes it much easier to click on them. Required some style
reshuffling to satisfy CSS.
|
|
- all www.* traffic -> non-www
- redirect old blog entries without including the port
|
|
Deleting this code feels strange. This project has been around for a
decade, and despite occasionally needing a bunch of tweaks it had aged
well and worked fine for a very long time.
I've reached a strange point where I don't really feel like using
Haskell anymore, and every interaction with this project in recent
years has been fighting dependency management tooling for Haskell, or
dealing with strange build problems.
The simple fact is that the service never really did anything other
than render Markdown dynamically, and at this point I can do that much
better with //tools/cheddar instead.
So, tazblog-hs, it's time to say goodbye. Rest in peace!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds the actual insertion of entries into the homepage, subtly
colour-coding different types of entries.
|
|
Shuffles around the nginx locations that are served to ensure that all
static content will be served from tazj.in/static (including for the
blog).
|
|
Adds the Jetbrains Mono font and the WIP CSS file for the homepage
and (soon) the blog.
|
|
This is not yet fully functional, but going in the right direction.
Some concepts are introduced:
* There is a light theme (used for blog entry pages) and a dark
theme (used for the homepage itself)
* Entries can be either blog posts, projects or miscellaneous things
that I want to link people to (possibly with a comment)
It might be interesting to add pages that filter to specific types, or
some such, which should be relatively easy to do.
Note that the layouts of entries are not actually done yet.
|
|
The homepage is going to be the landing page for all content, whether
it be blog posts or other stuff.
|
|
This lets me easily create an ordered list of entries if the homepage
is designed to list both blog posts and other content.
|
|
|
|
This introduces a derivation which builds an instance of nginx
statically serving my blog posts, though as of now no indexes are
being generated and no XML feed is available.
This is just the initial draft of this setup and not yet what shall be
yielded in the end.
|
|
This is mostly equivalent to the Haskell implementation, with the
primary difference that the Lisp DNS library does not support caching
yet.
|
|
Following this change, Markdown files in the tree view will be
rendered as highlighted Markdown sources.
|
|
Drops the previous patch setup to use //third_party/cgit instead.
|
|
These patches now live as commits at //third_party/cgit
|
|
With the sync-gcsr changes from the previous commits remote branches
are turned into local branches anyways.
|
|
1. Generate links to subtree about pages.
2. Render README files in subtrees, too.
|
|
|
|
This will render about pages using the Comrak renderer defined in
Cheddar.
Note that due to the way its implemented this will have one
interesting behaviour: Markdown files in the tree will *also* be
rendered as HTML.
I will need to see how that works out before deciding whether or not
to disable it.
|
|
|
|
It renders GitHub-flavoured Markdown, which is nice for most
use-cases.
|
|
|
|
|
|
Hopefully file following actually works for directories, too!
|
|
This moves the various projects from "type-based" folders (such as
"services" or "tools") into more appropriate semantic folders (such as
"nix", "ops" or "web").
Deprecated projects (nixcon-demo & gotest) which only existed for
testing/demonstration purposes have been removed.
(Note: *all* builds are broken with this commit)
|
