Repository navigation
Proposal: Strictly separate content and templates #56
Description
(This is an idea I've got after reading the discussion in #55 (comment), although it's not related to the discussion itself, so I'm opening a new issue not to spam that discussion).
See this template. It has content. It says things. I propose we remove the content form the template and save it somewhere where content belongs, such as in this repository a YAML or Markdown file.
Does it make sense?
(This is not intended as bikeshedding, feel free to ignore the proposal until more pressing issues are fixed.)
Activity
Sanqui commentedon Mar 9, 2017
I believe that is already being done for lessons. I can see some lessons have already been converted to Markdown, e.g. cmdline. However, it's more complicated with templates for e.g. the front page, which aren't simply formatted text, rather websites with various elements - buttons, containers, cards. Those may be expressed easier in explicit HTML.
encukou commentedon Mar 9, 2017
Yeah, the home page is special – it mixes short pieces of text and formatting, and it's quite visual. I think separating here would make it quite a lot harder to edit.
For more content-heavy pages, this should be done already.
Merge pull request #56 from muzikovam/for-review1
Překlepy, reformulace, vyhození nadbytečností (pyvec#56)