A collection of my tabletop role-playing game adventures, characters, character journals, and assorted tools or miscellanea. https://ttrpg.theinternetvagabond.com
Find a file
2024-06-14 16:51:08 -04:00
.forgejo/workflows Maybe fix action 2024-06-14 16:51:08 -04:00
_adventures Add beginning of adventures 2024-03-06 18:09:03 -05:00
_includes Fix linking for deployment to Codeberg Pages 2024-06-14 14:52:31 -04:00
_journals Update Journal-related functionality 2024-03-06 18:07:45 -05:00
_layouts Fix Seventh journal titles 2024-06-14 15:05:27 -04:00
adventures Big update dump 2024-06-14 12:46:00 -04:00
assets Big update dump 2024-06-14 12:46:00 -04:00
journals Fix Seventh journal titles 2024-06-14 15:05:27 -04:00
.gitignore Getting started 2024-02-26 19:42:22 -05:00
404.html Implement Journals 2024-03-04 00:56:10 -05:00
_config.yml Fix linking for deployment to Codeberg Pages 2024-06-14 14:52:31 -04:00
favicon.ico Add favicon.ico 2024-02-26 22:23:18 -05:00
Gemfile [Meta] Update Version and Lock file 2024-02-27 09:49:58 -05:00
Gemfile.lock [Meta] Update Version and Lock file 2024-02-27 09:49:58 -05:00
index.markdown Add an index page 2024-03-06 18:07:05 -05:00
README.md Add README, try to make workflow work 2024-06-14 16:46:06 -04:00

TTRPG Compendium

Static, Jekyll-based site for all tabletop RPG-related stuff I write about.

Adventures

Some of the adventures I've written up or am working on.

Journals

Both character and campaign journals

Tools

Stuff that helps with TTRPG play.

Building

For just running locally, easiest is to use a container:

    docker run --rm \
               --volume="$PWD:/srv/jekyll:Z" \
               --publish [::1]:4000:4000 \
               jvconseil/jekyll-docker \
               jekyll serve

For modifying and publishing newly generated content, the following process works pretty well:

  1. Remove the _site directory.
  2. Clone the "pages" branch into _site: git clone -b pages ssh://git@forge.niblock.tech:8222/vagabond/ttrpg-compendium.git _site
  3. Run the container from above step. It will now build into _site, which is linked to the "pages" branch.
  4. When satisfied with changes, be sure to push both from _site and the base repository to keep the source and the results up-to-date.