Commit 7fbf41d7 authored by Ana Isabel Carvalho's avatar Ana Isabel Carvalho

Update README.md

parent 3104df58
......@@ -6,20 +6,22 @@ into Markdown so that we can turn it into a website.
## Directory structure
* **01-original-scribus-files**: the original `.sla` files taken from the repositories
* **02-converted-markdown**: auto-converted Markdown versions of each issue, with pages out of order
* **03-separated-articles**: individual files for each article, not reviewed for markup yet
* **04-tagged-articles**: marked up files, with metadata headers
* **image-lists**: list of image files in each issue
* **old-content**
* * **01-original-scribus-files**: the original `.sla` files taken from the repositories
* **02-converted-markdown**: auto-converted Markdown versions of each issue, with pages out of order
* **03-separated-articles**: individual files for each article, not reviewed for markup yet
* **image-lists**: list of image files in each issue
* **content/issue**: marked up files, with metadata headers
* **content/images**: all images, full size
## Steps and progress
1. [DONE] Make a script to extract content from SLA files.
2. [DONE] Reorder the resulting Markdown and separate it into individual article files.
3. Extract the image file references from the SLA files, place them in this repo and link to them in the Markdown article files.
4. Add metadata headers to each Markdown file with Author, Title, Issue, other relevant fields
5. Design website
3. [DONE] Extract the image file references from the SLA files, place them in this repo and link to them in the Markdown article files.
4. [DONE] Add metadata headers to each Markdown file with Author, Title, Issue, other relevant fields
5. [WIP] Design website
6. Make script to generate the site pages from the Markdown files
7. Publish site
8. Done!
......
Markdown is supported
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