tchoi8 / distributedwebofcare

DWC

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

revise archiving/documentation scheme

achimkoh opened this issue · comments

  • maintain non-hierarchical structure of posts
  • display author in list?
  • sample tag scheme for medium: [art, drawing, performance, text, criticism, tutorial]
    • where ART: drawing or performance and
    • TEXT: critique or tutorial
    • ADMIN STUFF can remain untagged

For example, using this scheme, all guest essays and the EAW transcript could use tags: [text, criticism]; Cabal can use tags: [text, tutorial]; the performance documentation (yet to be updated) can use tags: [art, performance]. Or maybe categories instead of tags, whichever one works best.

We also (probably) want these sub-elements to have a consistent front matter taxonomy with other projects and individual artworks, so information such as top project (soft care) and date of production should also be in there.

Within the entire archive, DWC as a project can fall into a curation/organizing/event/4d thing.

If we choose so, we can maintain individual paintings, performances, workshops, etc as separate artworks that are duplicate or linked/aliased in DWC as a meta-artwork. For example, a directory structure like the following:

2018/dwc_drawing_1
2018/dwc_drawing_2
2018/dwc_performance
2018/DWC
2018/DWC/art
2018/DWC/art/dwc_drawing_1 (alias or duplicate)
2018/DWC/art/dwc_drawing_2 (alias or duplicate)
2018/DWC/art/dwc_performance (alias or duplicate)
2018/DWC/text/collaborators_essays
2018/DWC/text/taeyoons_essays

One thing to think about is that this is a Jekyll site nested inside a jekyll site and I'm not sure how that plays out when the static site is generated.