Re: What I'd like to see gsoc achieve: plone distributions
espen <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi ( more brainstorming) Could it be possible to enable «live editing» (the stuff that was included and removed again) just for the front-page? (then it woud be possible for «new users» to just click and edit the front page Espen 27. mars 2015 kl. 10:48 skrev Dylan Jay [via Plone] <ml-node+s293351n7573486h19-PKuAHvtXa09l57MIdRCFDg@public.gmane.org>: > > > On 27 Mar 2015, at 4:42 pm, Dylan Jay <[hidden email]> wrote: > > > >> > >> On 27 Mar 2015, at 4:25 pm, Espen Moe-Nilssen <[hidden email]> wrote: > >> > >> > >> 25. mars 2015 kl. 11:30 skrev Dylan Jay <[hidden email]>: > >> > >>> I can't see plone changing quickly such that plone doesn't have smart generic plugins. I'm not suggesting that themes don't use plugins but they come preconfigured and include demo content. > >>> > >>> Like this http://themes.crunchpress.com/?theme=book-store-wp > >>> > >> It would be so cool to have something like this for Plone. > >> If we focus on diazo themes, it should be doable, > >> Oe problem, though, is how to add the content > >> And also, how to edit it ? > > > > I figure the simplest way is to use GS but store it in portal_resources inside the theme in a profiles folder. > > You can have a control panel to snapshot the current site and that could include filters to only include the "right" kinds of GS steps. There is GS for creating content using plone.rfc822 now but not for saving content to GS I believe. The format kind of sucks and it only handles certain content types so is not universal. Either we improve it or perhaps put jsonify into the core and use that from GS or a combination of both. > > > > So as a theme creator you might > > 1. create a prototype site with the same content. > > 2. Setup the GS filters to strip out things like users or mailhost settings > > 3. develop your theme TTW > > 4. got to theming control panel and snapshot the site. review the XML in the theme editor. > > 5. click a publish button to push your theme to plone.org (or where ever is configured as your theme repo). > > or the sharing/publishing can be done via asko's existing git integration - https://github.com/collective/collective.gitresource > Configure a github repo. Click push. > > > > > As a theme installer you might > > 1. browse the set of available themes inside theming control panel available on plone.org (or configured theme repo) > > 2. click install > > 3. downloads and activates it. > > 4. asks if you want to install default content and configuration. Gives a summary of what it will install. (maybe you can opt out of some?). Include warnings on what will be overwritten. > > 5. click install. done. > > > > Most of that I think is doable in a sprint or GSOC. > > > >> > >> Maybe it could be done with collectve cover, and/or diazo rules > >> > >> > >> Espen > >> > >> > >>> This idea that themes are 100% generic and can be used on any kind of site is too idealistic I think. It sets the bar far to high and also makes the themes too bland. > >>> > >>> The default content and configuration is installed on first install maybe vs GS. You would likely have upgrades to the diazo or plugins but you would have to ship upgrade profiles to the GS if you wanted to ship a theme that included upgrades to configuration. Most likely you wouldn't. > >>> The idea is to help people get started quickly so they have to make so many choices on how to get a useful site for their purpose quickly. > >>> > >>>> On 24 Mar 2015, at 9:47 pm, David Bain <[hidden email]> wrote: > >>>> > >>>> One of my frustrations with Wordpress in the past is functionality being tied to themes, I consider this a weakness, not a strength. In fact, it is my understanding that the best wordpress developers discourage the practice, or to put it another way, key functionality in a them is something done in wordpress, found to be wanting and now actively discouraged. > >>>> > >>>> Anchoring key functionality to a theme sets us up for troublesome migration issues (at least when a customer wants to change the look of their site). Upgrading the look of the site becomes a production rather than simply changing the theme. > >>>> > >>>> I'm definitely in favour of distributions, but they need to be theme independent, so that an end user doesn't have to cross their fingers when changing themes for their new Plone based "daily deals distribution", "education distribution" or "mini-reddit-clone distribution". > >>>> > >>>> My suggestion is that an audit of the most commonly used widgets and views be done, then themers would be encouraged to account for these in their theme. The closest thing we have to that now is the /test_rendering view which shows common widgets. A good summer of code project towards this end would be to fill out a more comprehensive reference page for themers. > >>>> > >>>> This approach is used for wordpress themes on themeforest in the form of shortcodes pages. > >>>> See screenshot below: > >>>> > >>>> <image.png> > >>>> > >>>> > >>>> - > >>>> > >>>> > >>>> > >>>> David Bain, RHCSA > >>>> Owner at Alteroo > >>>> [hidden email] > >>>> www.alteroo.com > >>>> (876) 475-5824 > >>>> > >>>> > >>>> On Tue, Mar 24, 2015 at 5:30 AM, espen <[hidden email]> wrote: > >>>> > >>>> 24. mars 2015 kl. 11:20 skrev Dylan Jay [via Plone] <[hidden email]>: > >>>> > >>>>> at is missing? > >>>>> I realise it's perhaps beyond GSOC student but perhaps not if someone steps up and architects how you could put a prebuilt site into a theme package. Previously I'd suggested just dumping GS xml into the theme package and then a button to install the GS after you activate a theme but no one seemed to like that so perhaps someone could come up with a better idea that a GSOC student could code? And then we could have some great example sites rather than just e > >>>> > >>>> Just some brainstorming: > >>>> > >>>> Could it somehow be possible that the universal installer installed some Plone sites. > >>>> SO: after installing Plone (for the first time), when you go to http://localhost:8080, you see > >>>> Plone site > >>>> and > >>>> PloneDemo1 > >>>> PloneDemo2 > >>>> etc > >>>> > >>>> As many probably does not want this, it should be possible to turn off in buildout (?) > >>>> > >>>> Espen > >>>> > >>>> View this message in context: Re: What I'd like to see gsoc achieve: plone distributions > >>>> Sent from the Core Developers mailing list archive at Nabble.com. > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored > >>>> by Intel and developed in partnership with Slashdot Media, is your hub for all > >>>> things parallel software development, from weekly thought leadership blogs to > >>>> news, videos, case studies, tutorials and more. Take a look and join the > >>>> conversation now. http://goparallel.sourceforge.net/ > >>>> _______________________________________________ > >>>> Plone-developers mailing list > >>>> [hidden email] > >>>> https://lists.sourceforge.net/lists/listinfo/plone-developers > >>>> > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored > >>>> by Intel and developed in partnership with Slashdot Media, is your hub for all > >>>> things parallel software development, from weekly thought leadership blogs to > >>>> news, videos, case studies, tutorials and more. Take a look and join the > >>>> conversation now. http://goparallel.sourceforge.net/_______________________________________________ > >>>> Plone-developers mailing list > >>>> [hidden email] > >>>> https://lists.sourceforge.net/lists/listinfo/plone-developers > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Plone-developers mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/plone-developers > > > If you reply to this email, your message will be added to the discussion below: > http://plone.293351.n2.nabble.com/What-I-d-like-to-see-gsoc-achieve-plone-distributions-tp7573429p7573486.html > To start a new topic under Core Developers, email ml-node+s293351n293355h58-PKuAHvtXa09l57MIdRCFDg@public.gmane.org > To unsubscribe from Plone, click here. > NAML -- View this message in context: http://plone.293351.n2.nabble.com/What-I-d-like-to-see-gsoc-achieve-plone-distributions-tp7573429p7573487.html Sent from the Core Developers mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers