Hello, There's no magical integration from Wordpress themes. In the other hand, you have diazo (http://docs.diazo.org/en/latest/) that can be integrate in mezzanine. This project is able to integrate any HTML/CSS/JS theme with only an XML transformation sheet. In one ohter CMS this transformation sheet is generated in the web interface.
Best regards, Encolpe 2016-03-09 11:08 GMT+01:00 Johnson Chetty <[email protected]>: > Hallo, > > Just stumbled onto this link. > > Is there any update on this? Can anyone guide/point out if there is any > way to incorporate wp themes? > > On Wednesday, November 24, 2010 at 3:05:40 AM UTC+5:30, ajfisher wrote: >> >> Looks like you were writing that as I was tapping mine out off my phone. >> >> I'm quite partial to the idea of device splitting but I think anything we >> do needs to allow for independence of the template files but the ability to >> use them together when we need them. >> >> Cheers >> ajfisher >> >> >> On Wed, Nov 24, 2010 at 7:29 AM, Stephen McDonald <[email protected]> >> wrote: >> >>> Actually just thinking more on this - I think there are two distinct >>> concepts. A theme, and device support. These don't necessarily have to be >>> tied together conceptually, eg a mobile theme and a web theme. >>> >>> Perhaps a single theme could be broken down into separate sets of >>> templates for different devices? >>> >>> On Wed, Nov 24, 2010 at 7:20 AM, Stephen McDonald <[email protected]> >>> wrote: >>> >>>> You're gonna have to elaborate on "better solution". >>>> >>>> The current implementation of mobile support means that each mobile >>>> template mirrors a web template with a different name based on convention >>>> (.mobile.html) - couple that with the approach I'm taking to theming >>>> whereby a theme is nothing more than a set of templates that physically >>>> gets copied into your project's main templates directory, then yes you >>>> could theoretically install a theme that only provided web templates, and >>>> install a theme that only provides mobile templates, and it would all work. >>>> >>>> In reality I don't think this is a likely scenario especially as you >>>> move towards larger scale sites where consistent branding becomes more >>>> crucial. Is someone really going to install a web theme and a mobile theme >>>> with entirely different styles? Perhaps but I feel like this would be a >>>> very small percentage of use cases. Much more likely would be themes that >>>> have mobile support - all with a consistent look and feel across both >>>> mobile and web. >>>> >>>> While the idea of specifically creating support for multiple isolated >>>> themes at once would be technically cool, I feel like it would be overkill >>>> and add unnecessary complexity. Even more so once you start considering >>>> themes adding their own functionality such as models and template tags. It >>>> just makes a lot more sense from an overall design perspective to steer >>>> theming into single instances. >>>> >>>> Cheers, >>>> Steve >>>> >>>> On Tue, Nov 23, 2010 at 8:30 AM, Andrew Fisher <[email protected]> >>>> wrote: >>>> >>>>> First cut of this looks great Steve. >>>>> >>>>> Is it possible to run N themes in tandem in this with say 1 for web & >>>>> 1 for mobile? >>>>> >>>>> Currently we're doing this with template routing but separating the >>>>> two themes would be a better solution. >>>>> >>>>> Cheers >>>>> ajfisher >>>>> >>>>> On 23/11/2010 7:56 AM, "Stephen McDonald" <[email protected]> >>>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I've been working on an initial framework for working with the concept >>>>> of themes which is now in a working state in the Mezzanine repo. In a >>>>> nutshell, as discussed earlier in this thread a theme is simply a Django >>>>> reusable app that at the very least implements a set of templates and >>>>> static assets. >>>>> >>>>> The main goal I set out to achieve is to leverage Django concepts as >>>>> much as possible and create an infrastructure for template/interface >>>>> developers to be able to create new themes from a project, and install >>>>> these themes into other projects and customize them at the template level >>>>> as much as required. >>>>> >>>>> As such the focus of this work has been mostly around management >>>>> commands automating the workflow of working with themes rather than the >>>>> actual technical implementation of a theme framework, which for the most >>>>> part simply makes use of what's already there with Django. >>>>> >>>>> First draft of the documentation for this is here: >>>>> http://mezzanine.jupo.org/docs/themes.html >>>>> >>>>> <http://mezzanine.jupo.org/docs/themes.html>Feedback welcome! >>>>> >>>>> Cheers, >>>>> Steve >>>>> >>>>> >>>>> >>>>> On Sun, Nov 14, 2010 at 1:35 AM, n3storm <[email protected]> wrote: >>>>> > >>>>> > Hi, >>>>> > >>>>> > no worries about d... >>>>> >>>>> -- >>>>> Stephen McDonald >>>>> http://jupo.org >>>>> >>>>> >>>> >>>> >>>> -- >>>> Stephen McDonald >>>> http://jupo.org >>>> >>>> >>> >>> >>> -- >>> Stephen McDonald >>> http://jupo.org >>> >>> >> -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ http://encolpe.wordpress.com/ Logiciels libres, hockey sur glace et autres activités cérébrales -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
