Content editing is difficult

[jamiefolsom]

• For routine tasks, use Site Leaf. Must be upgraded to a non-free account, to allow for volume of content. Check with Jamie/Nick about that upgrade.
• For tags, which have to be edited both within source posts, and within tag posts: can we migrate tags to data files, or collections, so that they are more "relational"? See: http://jekyllrb.com/docs/collections/ and http://jekyllrb.com/docs/datafiles/

Pain points

• Metadata (frontmatter) editing (punctuation has a different meaning
• Content editing is not too bad
• Adding a new source is not too bad
• Easily add some content below the image or the artifact (above or below)
• Article: add a brief summary

Basically -- ease of editing is crucial

[jamiefolsom]

What I've found out

• Tags are inserted into source posts as strings

What I think we should do about it

• I think we should use Jekyll collections instead

@tezcatlipoca what do you think?

[feralresearch]

@jamiefolsom

Collections would be fine I think.

Alternatively, on my own sites, I make use of the datafiles directory and a short script for deployment which prefaces the 'bundle exec...' with curl statements to retrieve the data off of the internet. This means I can just edit a spreadsheet or text file (could probably be hosted on google docs I think) and then it gets rolled into Jekyll at "compile time." It's low-tech but it works nicely. The script could also create the requisite .md files for our site if needed.

I have no idea if something like this would work here - a roundabout way of asking who is doing the editing and deployment and how.

I'll attach an example.

deploy.sh.zip