Your SlideShare is downloading. ×
Plone mockup   modernising plone front-end development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Plone mockup modernising plone front-end development

364
views

Published on

The talk I gave on August 7th 2013 at the PloneSA Meetup.

The talk I gave on August 7th 2013 at the PloneSA Meetup.

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
364
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. PLONE UI TEAM and several other hard working ninjas BRING YOU
  • 2. [ modernising Plone front-end development ]
  • 3. What?What? It is a collection of different widgets which... according to some people.. should be part of Plone since last year already
  • 4. Why?Why? We have full unit testing of Plone js We gradually replace and fix Plone's javascript story * We can avoid using z3c.form for making new widgets We have an increased pool of potential new contributors Allow front end developers to contribute easily to Plone Improve the user experience for Plone 5 with modern widgets
  • 5. So...So... Rok Garbas started the Mockup Project
  • 6. InterestingInteresting facts...facts... uses RequireJS (adheres to AMD) (development only) Almond used instead of RequireJS for packaged production js code. Uses LessCSS (dynamic stylesheet language) In heavy development is MIT licensed
  • 7. But someBut some minorminor Confusion?Confusion?
  • 8. But someBut some minorminor Confusion?Confusion? from Mockup FAQ - Heavy inspiration from PatternsLib - no code shared Uses PatternsLib registry - gives us nice way to trigger Patterns via pat-<pattern-name> class. side note: Every pattern is also jQuery plugin and the pattern can be triggered as such but then.. Rok's (older?) blog post:
  • 9. I want to try it!I want to try it!
  • 10. How?How? You need Git & Node installed Standalone Git checkout Plone interfaces with Mockup project via plone.app.widgets & plone.app.toolbar Plone 4.3 buildout: buildout.deco on Github Or try the pattern demos online
  • 11. Sources:Sources: Mockup Project Documentation Rok Garbas' Blog PloneUI mailing list
  • 12. Credits:Credits: http://plone.github.io/mockup/dev/#about https://github.com/plone/buildout.deco http://lists.plone.org/pipermail/plone-ui/2013-July/ *http://www.coactivate.org/projects/plog2013/plone-mockup-plone-app-widgets http://garbas.si/blog/2013/escaping-april-weather-plog-reportout http://garbas.si/blog/2013/patternslib-plone-mockup-ok-time-to-explain-it
  • 13. Time for some demosTime for some demos
  • 14. @witekdev Thanks!Thanks!

×