Content repo structure and simple local preview.
Structure
-
The plan/record/share a "static" classification (which later can be a dynamic taxonomy) which is used by transcluding the plan.md / record.md / share.md files in the index.md file. As a result, the home page displays the TOC (note that I have only updated the first chapter links).
-
I've adopted a structure where the chapters are the top level folders, they contain an index file (which used to be the content in the files). And numbered "section" files. This should work with top level lessons and activities folders, with numbered files in each. The idea is that the app's home page will list the top level folders, and clicking on these will displays the list of "section" level files. Each section level file will contain content that fits on one screen in the app. This is why I think that these sections shouldn't be merged in one file, given that we want the authors to understand intuitively that one file = one screen.
-
It's a detail but I've renamed files using what's called kebab-case https://en.wikipedia.org/wiki/Letter_case#Special_case_styles in the future we might support also camelCase as you started using.
Tasks
-
Basic content structure for navigation -
Multilingual structure