Skip to content

include mockup docs and tutorials #1

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
svx opened this issue Feb 10, 2014 · 7 comments
Closed

include mockup docs and tutorials #1

svx opened this issue Feb 10, 2014 · 7 comments
Assignees

Comments

@svx
Copy link
Member

svx commented Feb 10, 2014

include all docs about mockup/toolbar and so on, this goes together with:
plone/mockup#279

@svx
Copy link
Member Author

svx commented Apr 7, 2014

@polyester I assigned this ticket to you, since you were working on it during the sprint in Munich :)

@svx
Copy link
Member Author

svx commented Sep 28, 2014

@polyester do yo know the status of this ?

@svx
Copy link
Member Author

svx commented May 5, 2015

@polyester

@fulv you started to work on that during PLOG 2015 right ?

@fulv
Copy link
Member

fulv commented May 5, 2015

Yes, I'm still working on it.

On Tue, May 5, 2015 at 6:44 AM sven notifications@github.com wrote:

@polyester https://github.com/polyester

@fulv https://github.com/fulv you started to work on that during PLOG
2015 right ?

Reply to this email directly or view it on GitHub
#1 (comment).

@svx
Copy link
Member Author

svx commented May 5, 2015

cool !!!!!!!

tkimnguyen added a commit that referenced this issue Jun 20, 2015
@svx svx added the sprint label Jul 9, 2015
polyester pushed a commit that referenced this issue Nov 19, 2015
Content type as default view update
@ebrehault
Copy link
Member

Hi @svx and @fulv,
I do not know what is the status on this issue, but we definitely need to document Mockup pattern usage in the Plone doc.
I am not sure getting the full content of http://plone.github.io/mockup/dev/# makes a lot of sense because a lot of patterns are internal to Plone (almost nobody will re-use Theme mapper pattern or the Structure pattern for a custom dev).
Moreover mixing a JS/markdown-based doc and a RST/python-based doc sounds tricky.

So I think we should have a regular doc page here (written manually) explaining how to use the main patterns (like modal, content-loader, moment, etc.).

What do you think?

svx pushed a commit that referenced this issue Apr 27, 2017
Update introduction-to-collections.rst
@stevepiercy
Copy link
Contributor

Closing in favor of #1270 and #1253

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

6 participants