Issue metadata
Sign in to add a comment
|
Add documentation in page_info folder |
||||||||||||||||||||||||
Issue description
i.e. a README.md file containing:
- A brief summary of the related code for different platforms and how the parts interact
- A short summary of the history and future direction.
- Links to relevant design docs from recent changes:
- Material Page Info (Public Doc) [1]
- Material Page Info Test Plan [2]
- Page Info Spring Cleaning 2017 [3]
- Hiding default permissions in Page Info [4]
I should probably make sure the design docs all have a least one reference in a Page Info folder int he public Enamel folder.
[1] https://docs.google.com/document/d/1wMKbWsXKHzTT1e_UZkI1jtHrCCcVsNTX18P6db-y6RU/edit#heading=h.au203bjfkch0
[2] https://docs.google.com/document/d/1sigJGd_KKPmLAG6yfWynRfI7lZuZdrah9siEtyRPCIs/edit#heading=h.127pio16mn79
[3] https://docs.google.com/document/d/12YnhxsNd-o82DfsyPpHRKM2yuXx7XOoKqaPt94CL9z8/edit
[4] https://docs.google.com/document/d/19ZfLlD8xyeALW0RZvGsEdYM82wxXYcGLjLr__fUfXRQ/edit#heading=h.au203bjfkch0
,
Nov 30 2017
More documentation can never hurt but I don't think we usually have documentation like this for individual UI components, so I'm going to close this. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by est...@chromium.org
, Nov 10 2017