Tracking our slide
trumpocalypse is a way of tracking what isn't normal around us. It's designed to be easy-to-use, distributed, and customizable.
This repo provides YAML-formatted data to track the abnormal things happening under the Trump presidency. On its own it's just a data store, but if you have a Jekyll site you can use this data along with a page template to keep your own log.
trumpocalypse is designed to be easy to merge in to, to enable sharing of posts between people. Each person can keep their own repo and take or ignore pulls as they feel fit. This isn't an editorial service, it's a method for people to keep their own logs and share how they want to.
These steps assume you have an existing Jekyll site. If you don't, GitHub pages is a great way to set one up.
- Add trumpocalypse as a submodule within your _data directory
git submodule add https://github.com/Sagelt/trumpocalypse.git trumpocalypse
- Add trumpocalypse renderer as a submodule wherever you'd like the page to live. For example, if you add the submodule under /pages, you'd run this command there.
git submodule add https://github.com/Sagelt/trumpocalypse-ui.git trumpocalypse
- Update as often as you'd like
git submodule update --remote
As above, but replace the repo links being added with your own repos.
Please send your pull requests! Note that taking pulls to this repo is my personal decision. If you don't like the things I choose to highlight you can use this system to make your own.
Each story should go in its own .yaml file in a directory based on the date. title and url fields are required, at least one tag is recommended. desc field is optional.
Stories are displayed in alphabetical order based on file name. Place your files in whatever order makes the most sense to you.
Some friends and I have a group chat where we share news stories. garykac had the great idea of hosting a page to collect all these things. It resonated with me because I'd heard advice to keep a log of changes to avoid the slow redefinition of 'normal' under Trump. I wanted to make something that could be merged easily so people can share what they find, so I expanded on garykac's idea.
Yep.
I used stuff I like. I was more interested in creating a tool anyone could fork and host themselves than fancy CMS features.
I host a live version on my site which is also based on a git repo.