Write the design text to be published as a document that planned the final design in that form from the start.
Principles
Published text contains only the final design that a new participant who does not know the history of the conversation can read through. Do not include revision diffs, the process of consideration, lists of rejected proposals, or references to the conversation. Do not write about the existence or application of this skill itself in planning or design text.
For how to create the chrome, comment core, and version of a single HTML, follow kf-g-html-document-universal-single-file . When publishing design text, rewrite its body ([data-content-root]) as the final form. The target is limited to the design text being published now.
How to read through
- Fully rewrite the text to be published as a document that planned the final design in that form from the start.
- Treat the reader as a new participant who does not know the history of the conversation, and place only text that works without the history.
- Place only the descriptions necessary for reading through the final design.
- In planning or design text to be published, write only the design content.
Final check
- The published text can be read through as the final design
- A new participant can understand it without the conversation
- The published text does not contain revision diffs, the process of consideration, rejected proposals, or references to the conversation
- The published text does not contain statements about the existence or application of this skill