12 Commits (a0cf4859190efc4b8ce02c34ba68a42508a0dbd6)

Author	SHA1	Message	Date
Kegan Dougal	be9402b66f	Move feature profiles section to modules as a sub-section	9 years ago
Kegan Dougal	1da64db302	Use relative depths for groups instead of absolute ones ... This means the group can be agnostic to how deeply nested it is, improving reusability of groups.	9 years ago
Kegan Dougal	5115346297	Add instant_messaging module; modify batesian section rules ... Previously, all `m.room.*` events were wodged into `{{room_events}}` which isn't great when you want to pull specific ones out. Batesian had a 1:1 mapping of `render_foo()` to a section `{{foo}}`, and having to constantly add functions for new types is a PITA. Batesian now supports returning a `dict` instead of a section `string` where the keys are the `{{foo}}` and the value is what will be inserted. Also add conflicting section key checks to avoid multiple definitions of the same `{{foo}}`. Define dicts for event schemata and swagger HTTP APIs. Using this new feature, split out the instant messaging stuff from the events section, and replace `{{room_events}}` with a list of specific events e.g. `{{m_room_member_event}}`.	9 years ago
Kegan Dougal	5b134119bd	Add presence module; fix relative title bug ... If a relative title appeared after an HTTP API table, it would insert the wrong level because it thought that part of the table was a title.	9 years ago
Kegan Dougal	b49cb57fe5	Move events sections to CS API	9 years ago
Kegan Dougal	0c0ac3e814	Fix common event fields template to use subtitle char	9 years ago
Kegan Dougal	e8cdfcbba2	Rename spec files to not have numbers everywhere; update targets.yaml	9 years ago
Kegan Dougal	f71763b0d3	Implement relative title styles ... Templates don't know at what level they will be inserted. Previously, we hard-coded the title style which is not compatible with the build target system. Define a set of styles which will be replaced by the gendoc script when it encounters them: '<' : Make this title a sub-heading '/' : Make this title a heading at the same level '>' : Make this title a super-heading The build target system is now basically complete and functioning.	9 years ago
Kegan Dougal	067363c629	Get the desired title levels right; print out the actual level used to stdout	9 years ago
Kegan Dougal	8590cc84b5	Process and extract targets in gendoc.py	9 years ago
Kegan Dougal	568982ee2e	Represent nested deps in targets.yaml along with title styles ... This will allow us to programatically position .rst snippets *anywhere* which will for once and for all remove the horrid title level mismatch bugs. We require this in order to allow people to re-shuffle the spec without having to adjust the spec itself (e.g. 2 targets with different levels of nesting).	9 years ago
Kegan Dougal	703f913a47	Add a 'targets.yaml' files in /specification ... We're well beyond the point now where a simple `cat` of .rst files to "build" the spec is practical. We may want to slice and dice the spec in different ways to address various cross-cutting concerns. To this end, there is now a 'targets' file which contains the "build targets" for the spec, which contains the sorting order for the .rst files. For now, we just have a single target: 'main'.	9 years ago