)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"46b93909d83841b8dad1be1131a798a0c7e60e6c","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Extract project config YAML into ref docs"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Put the YAML definitions for project configuration items into their"},{"line_number":10,"context_line":"own reference documents."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: If3aaeac2fc4258b8869dcfff67ef3c011b50e158"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fa7e38b_eeb137e5","line":10,"updated":"2020-01-14 16:11:17.000000000","message":"Maybe you could explain the rationale a bit more?  I can think of 2 reasons, but am unsure if these are what you\u0027re after:\n\n* It\u0027s a really long page.\n* Separate pages show up better in the TOC and make it easier to navigate.\n\nI\u0027m a little worried about splitting off the introductory material from each section.  Imagine a user discovers that they need to learn about a nodeset.  They might jump straight to https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_284/701977/1/check/zuul-tox-docs/284ca1a/docs/references/nodeset_def.html and miss https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_284/701977/1/check/zuul-tox-docs/284ca1a/docs/references/config.html#nodeset\n\nHow about we move the introductory material to the leaf-nodes as well (ie, so that docs/references/nodeset_def.html has everything about nodesets).  And then make references/config.html an index page.  It could just be a :toctree: list, or we could write a sentence or two about each object.","commit_id":"704d0ce13d82a236df4072ffadf3cfeb57f3a32e"},{"author":{"_account_id":3099,"name":"David Shrewsbury","email":"dshrewsb@redhat.com","username":"dshrews"},"change_message_id":"1fbfa6f64519aa444acb3feb980148da0968152e","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Extract project config YAML into ref docs"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Put the YAML definitions for project configuration items into their"},{"line_number":10,"context_line":"own reference documents."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: If3aaeac2fc4258b8869dcfff67ef3c011b50e158"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fa7e38b_4e3f2b22","line":10,"in_reply_to":"3fa7e38b_eeb137e5","updated":"2020-01-14 16:16:39.000000000","message":"Sure. This change is the biggest pet peeve that I had with the current docs and the main reason I wanted this reorg. I could never remember where the various definitions were for these items when I needed to reference them, so being able to quickly identify where they live is the main objective.\n\nI\u0027m fine with moving each item\u0027s intro material to the reference docs.","commit_id":"704d0ce13d82a236df4072ffadf3cfeb57f3a32e"}]}