Re: Plain Language Prototype for comments

Hi everyone,



I had a message off-list from someone who’d prefer to remain anonymous that pointed me to this prototype for context:
https://docs.google.com/drawings/d/1uebx3tpkt2dGZaV8GnWVw-LBLE_u9bOtlHH09HVAjTs/edit




It has tabs for ‘get started’ and others, including development and testing.



That helps, but I replied:



If things like ‘how’ and ‘examples’ are included in the ‘get started’ tab, that shows you to some fairly specific details without actually giving people the accurate requirement. (As David said, the bit that would be referred to in laws/policies.)



Also, the ‘flavor’ mentioned (technology) will affect all the tabs, not just the develop tab. It also affects most sections of the summary.



For example, the headings requirement changes depending on the technology in a way that would affect the summary. e.g. Flash didn’t have headings as such, I don’t think Android apps do either unless it’s changed recently. The advice for ePub/PDF is subtly different from HTML due to the bundling of pages into one document.



Either the summary has to work across technologies (with less detail than the example included), or it needs to incorporate the technology details explicitly. I.e. you choose “html” to see this version of the summary.





The person offered to work through the examples with me, but I think this is a structural thing.



Everyone chunk of content (e.g. the why, how, examples) is potentially affected by the technology, at least in the way it is being approached now.



Is that the intent, or was the intent to keep the technology to a particular part/area of the SC?



Cheers,



-Alastair