lindleyw
commented
9 years ago The challenge will be that a WP "theme" is actually a mass of HTML+PHP, CSS, images, and sometimes JavaScript. "Themes" are mostly active code, and are the most concentrated cesspool^H^H^H^H locus of WP-specific API calls.
Taking a step back, however, the active parts of WP themes are a few basic elements:
- "The Loop" which controls spitting out the selected posts or pages requested by the HTTP query. Themes can define more than one loop, or use various functions to retrieve other posts, pages, or meta-information.
- Widgets, little drag-and-drop elements definable by plugins, which are placed into zero or more Widget Areas created by the Theme. Widgets can be created and manipulated through the built-in Admin interface.
- Menus, added in WP 3.0, are essentially lists (that can be defined through the Admin interface) of a few predefined things: posts, pages, categories, etc. The Menu system was rather grafted onto the more automatic parts of WP and doesn't really match up with the way anything else works. A Theme can define zero or more Menu areas for admins to edit.
Trying to import the active parts of a WP theme seems nearly impossible, but if a user-interface-element mapping can be documented, at least a utility could put most of the HTML, CSS and graphics into proper locations for a new native theme.
scottwalters
WordPress themes (CSS, icon sets) should be importable into wG via a utility.
This is to be done in two parts: WordPress themes should be converted to an intermediate, neutral format suitable for consumption by any blog, CMS, or the like. Todo: Actually look at some WordPress themes.
Second part is conversion of this into a wG theme consisting of static "extras" files, template assets in the correct template namespaces, and CSS class names translated.