Here's an example of me installing a theme with an embedded configuration for a plone based blog:
My workflow for creating that was:
find and install a nice zipped theme
configure Plone site to work as a blog
export portlets and site structure / content into theme usin c.themesitesetup export
trim portlets.xml to only include assignments
Current issues (visible also in demo):
catalog must be manually reindexed after theme activation (maybe there could be a treshold to make it automatically when the site as almost no content)
new styles collection criteria was not exported nor imported (that's due to Archetypes RFC822-marshalling, which cannot be extended for custom fields like the criteria field, but could be fixed for Dexterity because the new extensible plone.rfc822)
Of course, there's also more small issues with content export / import, but actually none that could not be fixed, because GenericSetups' filesystem export / import framework seems to extensible enough.
Had to try a re-take with my experimental collective.atrfc822 replacing the default Archetypes RFC822 Marshaller with the plone.rfc822 one. Now also collection's queryfield and even the news item image were export and imported:
I don't know about Dylan's use case, but I've used fat themes because of ease of deployment (scripted zip-upload), not so much because of reusability (which is hard anyway with customer branded themes). For me, fat themes has replaced the need for site specific policy packages.
Yes this is the same for us, customer themes. Although we have been doing zip deployments for themes for a long time (since we went eggless).
@tkimnguyen I suspect the marketplace for ootb themese comes when plone is more attractive to solo webmasters (like no buildout) and as they start making their own personal themes. But maybe its chicken and eggs?
It would be good to see some ootb fat themes that include example content.
Still, I think we would all like to see more shared Plone themes like Vikas' from last year. Perhaps someone cough @pigeonflight cough would like to organize a theming sprint?
@tkimnguyen Vikas' proposal for the 2016 Summer of Code is well done! I submitted a proposal for a theme pack for this year's GSoC which was not as thorough as I would have liked or even close to as good as Vikas', so I'm not holding much hopes of getting in, but I'll still contribute one quality theme regardless.
But let's still remember that the idea of Dylan's eggless approach and also this add-on is that themes could be (miss?)used to include complete site configurations, with content types and all. Like 1) install Plone 2) upload configuration and initial configuration for a blog 3) tweak theme for your taste. We re doing more and more sites like Dylan proposed years ago: we have a bunch of generic backend packages shared by all of our sites and then a fat theme configuring everything.
(Of course, things are not perfect yet. The example content import with generic setup has issues [and Dylan has been proposing better approach for that], supporting both maintained fat theme and TTW customizations needs thought, as do automated testing testing of fat themes.)
Yes, sorry, badly worded... I did not mean we should do only regular themes. I like the idea of these fat themes. Is there any way you can share one that you've made but strip out the branding and leave something generic in terms of design?