Commit ca62693f authored by Zach's avatar Zach
Browse files

Make README more approachable

The readme was written hastily prior, and referred to an older version.
I changed the overall format so it starts witha  directory tour, a path
for customization, and _then_ the heavier coding stuff.

This is incomplete, as I want it to be suuuper accessible, with each
directory having its own README.
parent 2fd471d3
......@@ -2,16 +2,55 @@
It's a zine library for the Chorus!
**You can see an example library here:**
**To get a personal history, and changelog, for this library code check out: ``
# Directory Structure
The code is organized around the metaphor of a real-life zine library. So you have all of the zines, the building the zines go in, and the volunteers that perform all the actions that make the whole operation run.
You also have the identity of this library branch, and what distinguishes it from other zine libraryies.
This repo is laid out the same:
- `branch/`Holds the name and details of this particular library branch.
- `building/` Holds the HTML and CSS components that make up the library's structure and look.
- `volunteers/` Holds the core javascript functions that handle when the site is loaded, a zine is added, a zine is edited, etc.
- `zines/` Holds the zines themselves, each in their own text file.
TODO: Each folder has its own README with more details.
# Customizing the library
If you are the librarian, you can edit any of these files to make your branch your own. The level of customization depends on how much coding you wanna do.
Here's what I recommend:
- Edit the branch details either by clicking edit in the front-end, or by editing the info.txt file in the `branch/` folder.
- Remove any zines you don't wanna carry by deleting them from the `zines/` folder.
- Add new zines either through the front end, or by making a new .txt file in the `zines/` folder.
- Customize the general look by going to `building/aesthetic/stylesheets/colors-and-fonts.css`
- Customize the whole styling by going to `building/aesthetic/stylesheets/main.css`
- Customize the structural code in `building/components` or `volunteers`. This last step will require some more javascript knowledge.
The library is built using [choo]( This is a cute framework for building interactive web apps. Their homepage has an awesome tutorial on getting started. To really customize this, though, you'll need to install all required modules and such to your local computer. (see below)
# Installing
First, set up the App:
The simplest way to install this is to visit the library link in beaker, then fork it and add it to your local directory.
Alternately, you can clone this from gitlab.
`git clone`
git clone
cd dat-zine-library
npm install
npm run build
Then add it to yr BeakerBrowser:
If you cloned it from gitlab, you'll need to add this folder to yr BeakerBrowser:
- Open Beaker
......@@ -36,69 +75,6 @@ title: name of zine
url: dat:/ads;lkfajdsgklajglkah3j2kljakhdh32j.sha256
Click save and you should be good. If not, lemme know!
# Background
I get really excited about the creative world offered Dat, and Beaker Browser. They (along with Scuttlebutt), are pointing to the place that comes after the web. We call that place The Chorus. This is a tool made exclusively for the Chorus.
With Dat, anyone can have _abundant_ websites. since there are no server costs, you don't have to think about one central home for your stuff, and you don't have to adjust all the things you make to fit within the limits of the platform or site you are on. Instead, if you wanna make a new just make a new dat site. This is _really cool_.
I realized that dat sites can be just like zines. You can make one about whatever you like, fill it with what is important to you at that moment, and then give it out to whoever you want. There is no hierarchy to who can make or read a dat site, and there are no rules for how they should look or what they should be about.
So if I want a world filled with dat zines, I thought i should try to build a zine library to hold my favorites in. And thus: THIS!
It's a tool for you to hold the zines that are important to you, so that others can find them more easily.
Once you start using this site, it will be _your_ personal library. You can share it with others who can then fork it and build up their libraries too. Then you can share libraries like a good ol' fashioned web ring.
It also is intended to help build a practice of making dat zines, and a method to signal to other cool solarpunks that you wanna share the zine you just made.
## First: Make a Zine
To start, you wanna make or find a dat zine. This can be any sort of dat archive that includes a `distro` folder. This folder holds the information you want to make sure is included whenever someone adds yr zine to their library. So inside the distro folder is the cover of your zine and an info.txt file. That file looks something like this:
title: Fun Baking Time Zine
- Zach
- Angelica
materials: HTML, CSS, Choo
sharing: Share and fork and modify as you see fit, but please attribute any of these words back to me.
notes: We made this zine as a rainy day project. It ended up taking a week, but it was a rainy week too so it all worked out.
The cover can be any sorta .jpg, .png, or .gif
## Add the Zine to yr Library!
Now, go to your dat-zine-library site, view the files, and navigate yourself to the zine folder. In that folder you'll add a new .txt file called `the-name-of-the-zine.txt`
That file should look like so:
// filename is fun-baking-time-zine.txt
title: Fun Baking Time Zine
url: dat:/238r23uotu98329591295j23813j123j.sha256
Zach and Angelica gave me this zine the last time we hung out cos I wanted to know how to make Angelica's cinnamon chocolate cookies.
Then just press save and yr done!
The dat site will now include this new entry, your notes about it, the cover image, and the relevant info taken from that info.txt file!
Click save and you should be good. If not, lemme know!
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment