Setting up the dev environment
Cloning from git
First clone and change directory to a checkout of the git repository:
git clone https://gitlab.com/dustyweb/activitypub.rocks.git cd activitypub.rocks
Setting up dependencies the easy way: use Guix
Next you’re going to get the environment up and running. The “easy” way to do this is to use Guix (which can be run as its own operating system distribution or as a userspace package manager under any GNU/Linux distribution):
guix environment -l guix.scm
This will set up a shell with all dependencies pre-configured.
Setting up the dependencies the manual way
Running the server
Now that you have a dev environment up, it’s easy!
haunt build && haunt serve -w
Writing a new blogpost
Add a new Markdown file to the
posts/ directory and save it with a
.md extension; you’ll need to add a header like so:
title: My first ap.rocks blogpost date: 2019-03-08 14:45:00 tags: activitypub, hello world --- Content goes here!
(You can also use Skribe though I suspect only the lispiest of people will like doing this.)
Editing the site structure
css/fonts/images can be found in the
The rest of the website’s design can be found in
haunt.scm. Really this file ought to be split up. The templates all use sxml which may be unfamiliar to you but is a real delight once you learn to use it.
Basically activitypub.rocks is secretly a scheme program; the website’s rendering it its output. That’s the haunt philosophy. This is used to its full potential to generate the implementation reports page.
Basically, if you aren’t a Scheme hacker, editing the activitypub.rocks website is a great way to learn to become one!