Code. It is probably too new to be docs-umented and at any rate API documentation seem to rely more and more on better PHPDoc comments and the use of docs generators (with or without IDEs).
Itamar Tzadok
Posts made by Itamar Tzadok
$this->datagenerator = testing_util::get_data_generator()->get_plugin_generator('local_more_rules');
hth
Afaict the name doesn't have a particular meaning. The idea is that you can create tests for core components with steps that are not provided by core, by adding a local plugin (e.g. local_mysteps, local_davidrules etc.) defining the steps there and then writing the tests with those additional steps.
Start with understanding Output renderers.
For the navigation block you can override core_renderer::render_navigation_node.
hth
The headings provide a convenient way to see a list of items for reference in the TOC. See illustrations below. The page itself is not necessarily content heavy. Still the content it does contain may be easier to read with clearer headings.
The option of splitting to smaller pages is always there and I'm using it in other places of the Dataform docs. It comes with the price of more difficult maintenance, which is why I have suggested adding the Labeled Section Transclusion extension (https://moodle.org/mod/forum/discuss.php?d=256835#p1113710). Currently I have to create many content templates to be able to include the same content in several pages in order to reduce the number of clicks and avoid duplicating.
Btw, in the illustrations below some of the items in the TOC are included in the page via a template so it's already split to smaller pages.
