Closed IanMayo closed 1 year ago
We're storing the class-summary as a DITA properties object.
(See updated strategy at end)
This is how it gets rendered, by default:
The users are used to seeing these properties as two-row table that consumes less vertical space, like this:
So, I'm pretty sure we need to customise the publish process to support this.
Note: in the short term we could switch this to just being a 6 column table, that we copy directly from the mock data.
Yes, let's do that. Let's change Class Summary to being a table of two rows of 6 cells. Well, one header row and one body row.
Class Summary
We're storing the class-summary as a DITA properties object.
(See updated strategy at end)
This is how it gets rendered, by default:
The users are used to seeing these properties as two-row table that consumes less vertical space, like this:
So, I'm pretty sure we need to customise the publish process to support this.
Note: in the short term we could switch this to just being a 6 column table, that we copy directly from the mock data.
Yes, let's do that. Let's change
Class Summaryto being a table of two rows of 6 cells. Well, one header row and one body row.