Skip to content

JavaScript / Mockup documentation best practice #903

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
thet opened this issue Jul 13, 2017 · 3 comments
Closed

JavaScript / Mockup documentation best practice #903

thet opened this issue Jul 13, 2017 · 3 comments

Comments

@thet
Copy link
Member

thet commented Jul 13, 2017

I added these docs to the mockup repository:

https://github.com/plone/mockup/blob/master/mockup/patterns/structure/README.rst
plone/mockup#785

It's about how to customize the structure updater pattern.

I think, having docs besides each pattern is good practice (Patterns also do so. See: https://github.com/Patternslib/Patterns/blob/master/src/pat/gallery/documentation.md ). But placing the docs where I did in PR plone/mockup#785 does not really follow the Mockup practice. Also it's not Markdown but ReStructredText.
An option would be to place the docs on the same level like https://github.com/plone/mockup/blob/master/mockup/GETTING_STARTED.md
Having them in the plone/documentation repository is another option.

I don't have a strong opinion here. Maybe it's time to think about restructuring the Mockup docs?

Let's discuss this, @plone/documentation-team

@thet thet changed the title More documentation on Mockup JavaScript / Mockup documentation practice Jul 13, 2017
@thet thet changed the title JavaScript / Mockup documentation practice JavaScript / Mockup documentation best practice Jul 13, 2017
@thet
Copy link
Member Author

thet commented Aug 24, 2022

Stale issue. JS‌ docs have to be updated or even rewritten for Plone 6 anyways.

@thet thet closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2022
@stevepiercy
Copy link
Contributor

stevepiercy commented Aug 24, 2022

@thet would you please create a new issue for Plone 6 that provides any direction for what needs to be documented or rewritten? Please include where you would suggest it be placed in the new docs structure. I assume this is for Classic UI?

@stevepiercy
Copy link
Contributor

Superseded by #1270

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants