Capacity / Wordpress Integration Theme

Olivier Churlaud olivier at
Tue Jul 18 17:24:22 UTC 2017


Just to say it again: having the whole still there might not be the solution. 

Having a brand new website would allow us to write again (and better) the important and relevant pages, and drop the others. 

I'm pretty sure that having capacity running and keeping all the pages will end in keeping the same content, which is not readable. 

I'm 100% ready to help with writing some content (I don't have time for the technical part). But to me, the content seems as old as the capacity theme, so it has to change too. This doesn't have to be your (Ken's) job. It only needs to have the right infra. 

That's why I think a nice, only WordPress with the plug-ins (custom or not) allowing to deal with everything needed would allow us to move forward on content. (everything being: announcement, twitter/FB threads, application catalog, internationalization). 

If the new WordPress loads the old capacity pages, the kde website will still be crappy and read old.. 


>Date: Mon, 17 Jul 2017 17:50:20 -0400
>From: Ken Vermette <vermette at>
>To: kde-www <kde-www at>
>Subject: Capacity / Wordpress Integration Theme
>	<CAFtcy6x_Y4PqzowpCtc3CGdEfxGo9xMfhNwTny5NJR6GQoKdRw at>
>Content-Type: text/plain; charset="utf-8"
>Hello everyone, this is an update on the website redesign stuff; I know
>it's been a while since my last update, so I'll also be going over some
>plan changes.
>Mainly I'd like to go over the plan for our existing Capacity pages,
>how we can get Wordpress deployed before we have the 'complete
>solution' to
>replace absolutely everything we need it to handle.
>The original plan had a "scorched earth" policy where we would just
>the new site fresh, along with some custom plugins we would have to
>the dynamic pages we need. This had several issues, and as attractive
>as a
>fresh start is... things like dead links, loss of important pages, and
>dependency on a robust-and-mature replacement out-of-box has been
>the next phase of site updates. It required the theme, a page builder,
>language integration for that page builder, and various other plugins
>things like the homepage, applications, and announcements.
>So for the past couple weeks I've been working on solutions going the
>way - making Wordpress fit into our current system, and I've landed on
>something which seems to be workable, with only has relatively minor
>compared to a full-out deployment.
>The new plan I'm working towards is a Capacity Wordpress theme and a
>Wordpress Capacity plugin which joins the two together. The aim is to
>capacity pages import Wordpress directly, then communicating with a
>Wordpress will take over page rendering using the theme layout,
>navigation, etc. Using some voodoo hacks it essentially turns Capacity
>Wordpress when this theme is enabled on a Capcity-driven page. The
>rendering is still done via Capcacity function calls, so it breaks
>but everything beyond the content is Wordpress driven. That being said,
>still working out the fineries, there's still some visual compatibility
>issues, and it requires a patch to Capacity as well which I want to
>out. If it sounds a bit confusing, here's the essential workflow:
>1. Capacity page is requested
>2. Per-page Capacity config has the Wordpress installation linked (if
>not, nothing special happens)
>3. Wordpress is loaded (if failure, Capacity works as usual)
>4. Capacity verifies the Capacity compatibility plugin is active in
>Wordpress (if disabled, Capacity works as usual)
>5. Via the plugin, Wordpress captures the body content and runs it as
>output to an otherwise standard Wordpress page
>6. Everything is awesome.
>Eventually, we want to move pages out of Capacity and into Wordpress
>completely at some point. This, too, is handled by the same
>combo in development. It might be patched in later as it's a massive
>right now, but using this plugin we'll be able to set redirects within
>Wordpress as we complete replacement pages; capacity pages should
>immediately and automatically redirect when superseded this way, and we
>even SEO the pages is desired by flagging the redirect. As a special
>to this, it means that as we replace pages it won't destroy the
>capacity content and the pages will be able to provide a "view legacy
>content" link - probably by a nice clean URL flag instead of cordoned
>folders. Expanding the steps above, step 4.5 is "check to see if
>has content to use instead of the Capacity content, if so, use that".
>Beyond that it keeps all current workflows intact, so for better or
>everyone gets to keep things as-is until we override the pages
>and even then reversion will be a simple Wordpress toggle.
>All that said and done, right now my prototype is super hackish with
>of hardcoded paths, but I've proven to myself that the concept works.
>So, this is the "have our cake and eat it too" solution I have at this
>point. The main downsides I can see with it at this point mostly
>to a potential performance penalty; every page we switch will have both
>Capacity and Wordpress run in it. I don't know how much juice our
>have or even if it will make a significant impact, but it means pages
>the compatibility layer will have the performance cost of an uncached
>wordpress page. That being said, this is being done as a per-page
>toggleable 'switch', so when we're ready to begin deploying it we can
>enable pages gradually and see if my performance concerns are
>justified. If
>performance is an issue we would need to look into a plugin-level
>solution, but I don't want to put the cart before the horse. The next
>is that navigation links and other wordpress-driven page content will
>have il8n until a solution is devised, but page content and
>content will use standard translation pot files as we use now which may
>fine. Lastly, the live search functionality of the new design will not
>a way of searching static pages, but it's a feature we don't have at
>right now.
>In term of deployment, the plan is fairly straightforward;
>1. When finished the integration utilities, we apply a patch which
>the compatibility layer on the Capacity level. Pages not using it won't
>any impact.
>2. We install Wordpress on, installing the Aether theme,
>integration Plugin, and homepage content plugin.
>3. We convert the "Aether" pages we have now to use Capacity/Neverland
>instead of AetherLibs.
>4. Finally, we add a config line to each Capacity page setting the
>Wordpress path. This will automatically convert the page to
>Wordpress/Aether. Minor CSS tweaks and overrides may be required to
>out content, but nothing too invasive. Everything will become
>We can purposefully limit the rollout of wordpress-enabled pages if
>desired; going from Capacity to Wordpress is going to have some
>and we can also limit the exposure of any issues which may need to be
>ironed out. That being said I don't want a repeat of the initial
>redesign where I blindsided most of you, so I'll make sure we have a
>review of the changes before anything goes in so there isn't too much
>'ironing out' needed.
> - Ken
>-------------- next part --------------
>An HTML attachment was scrubbed...
>Subject: Digest Footer
>kde-www mailing list
>kde-www at
>End of kde-www Digest, Vol 172, Issue 6

Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.

More information about the kde-www mailing list