What should the structure of an element page be?

[Bjwebb]

Currently this is (each section may not appear if it is empty):

• Full element path
• From the schema
• Attributes
• Subelements
• Notes
• Example usage
• Changelog

[stevieflow]

Note to talk to @jonihillman and @iatisupport about this

[stevieflow]

Proposed:

• Full element path
• From the schema (label: Description)
• Attributes
• Notes
• Example usage
• Who is using this element - link to dashboard?

Marked as in the "footer" of the content pane:

• For developers (link to source - although could be a button)
• Changelog
• Subelements (putting this at the footer of the page as the list can be long)

[Bjwebb]

I've put subelements at the bottom. At the moment all the Extra-Documentation is one contiguous block, and it would require a bit of work to split this up. Therefore the page structure is currently the following:

• Full element path
• From the schema
• Attributes
• Notes
• Example usage
• Changelog
• For developers
• Subelements

Where everything from "Notes" to "Changelog" is pulled directly from the Extra-Documentation (so it needs to be in the correct order there)

"Who is using this element - link to dashboard" requires some development work to create - so I've created a separate issue for this IATI/IATI-Standard-SSOT#38 - I don't think this is one we actually need to get done for 1.04, although it would be nice if we did.

Not sure what you're suggestion by "footer of the content pane"

I'm quite happy to rename sections. I think "Definition" might be better than "Description" for the text taken from the schema. Are you also suggesting we change "Developer tools" to "For developers"? I'm happy to do so.

[stevieflow]

Yes, great

"Developer tools" is fine

"footer" - just meant the bottom