In our current model we have world > region > country > class
But, for nations with lots of installations, we have: world > region > country > category > class. Sometimes the categories are presented as text links, sometimes as image links.
Hmm, actually a more versatile strategy would be for `world > (one or more grouping pages) > category > class
It's the grouping page that is actually a table of text or image links. We probably don't need to enforce the above information structure, since DITA-IT will just walk the tree. But, we should formally move from country to category.
So, our country and countryBody elements should be renamed to category and categoryBody.
[x] Rename country to category
[x] Introduce collection (text links) and rich-collection (image links) elements
[ ] Update our current content to meet the above new constraints
[ ] Add new instance of Britain
[ ] Add child category pages to Britain
[ ] Check Britain exports as expected.
Samples of infrastructure provided here:
In our current model we have
world > region > country > class
But, for nations with lots of installations, we have:
world > region > country > category > class
. Sometimes the categories are presented as text links, sometimes as image links.Hmm, actually a more versatile strategy would be for `world > (one or more grouping pages) > category > class
It's the grouping page that is actually a table of text or image links. We probably don't need to enforce the above information structure, since DITA-IT will just walk the tree. But, we should formally move from
country
tocategory
.So, our
country
andcountryBody
elements should be renamed tocategory
andcategoryBody
.collection
(text links) andrich-collection
(image links) elementsBritain
Britain