OERu/Planning/Technology working group/Issue tracker and queries

Links

 * 1) Demo WP version: https://wordpress-oerudevpgogy.rhcloud.com/
 * 2) Source outline in the wiki used to generate the snapshot
 * 3) Terms of reference

Known issues

 * Some of the images don't appear
 * Some of the links don't work as is (I think both of these are the harvest script)

Issue tracker (Version 0.2)
Current issues identified when deploying theme on hosted instance (Wayne's WP install)

Shortcode questions

 * Accordion - I have done this and will try to style colourwise as per the rest of the theme
 * That's fine. consistent background and style in expanded view is fine. --Mackiwg (talk) 02:00, 6 February 2015 (UTC)
 * Course title block: Specifies course title, strapline and course image - this can all be done on the theme customiser - would it be preferable to change it per page?
 * Ideally, when the script runs it would be nice if the users is not required to customise the page type in Wordpress after the import. Jim, we may need to think about a wiki template if this style is used on other pages within the course. However, I don't image a use case other than the landing page. --Mackiwg (talk) 02:03, 6 February 2015 (UTC)
 * Default footer: which provides CC license attributions  and optional institution logo (see for example: http://olijones.github.io/index.html#) - think the theme widgets covers this https://wordpress-oerudevpgogy.rhcloud.com/wp-admin/widgets.php is the link to play with footer content.
 * I envisage two footer areas:
 * The "default" footer which contains the CC license, link to Privacy Policy, Author history in the Wiki and the logo of the contributing OERu partner. See for example the footer here: http://www.olijones.github.io/index.html. --Mackiwg (talk) 23:32, 6 February 2015 (UTC)
 * Optional extended footer which has the ability to add additional "navigational links" to pages on the site which are support links, i.e. not part of the main course content. See below for more info. --Mackiwg (talk) 23:32, 6 February 2015 (UTC)
 * Extended footer: The footer support widgets - but I am not sure what text in the footer would be page dependent - so perhaps an example would help? Am not sure if the theme footer covers this?
 * I envisage the "extended footer" for additional support links, for example help tutorials, learner support etc. This would enable us to reclaim real estate on the global navigation, for example by shifting the support link in this snapshot to the footer area. --Mackiwg (talk) 23:32, 6 February 2015 (UTC)
 * The extended footer area could mimic the display /style of this theme example. The theme has a "heading" and sublinks arranged in columns. For example we could have headings for "Help tutorials" and "Learner support" with sub-headings which link to pages on the site. So for example: under the "heading" Help tutorials, we could have 1) Registration tutorial 2) Blog tutorial 3) Microblog tutorial etc . Under the "heading" Learner support, we could have 1) Tips, 2) FAQs 3) Ask a friend etc.
 * We would need to have a clear way in the wiki to identify pages and links for the optional extended footer area, for example, and alternate sub-page in the wiki (for example http://wikieducator.org/course/footer with corresponding bullet list which the script can harvest or other clever solution.) --Mackiwg (talk) 23:32, 6 February 2015 (UTC)
 * In Wordpress the "header" does not link to a page, but the sub-pages under the header would link to to the standard page type we are using for course content. --Mackiwg (talk) 23:32, 6 February 2015 (UTC)

General questions

 * Most WordPress themes support menu nesting to any level - so the theme supports more than 2 - should people want it too - is this ok?
 * Yes, that's fine. If users want to go beyond three levels post import, that's fine. In our current model we accommodate 3 hierarchical levels. The 3rd level navigation in the style is a page element (expand / collapse table - see for example the orientation navigation here). The default should be the page element navigation. However, if using the native wordpress theme navigation, perhaps we can deploy an "off" / "on" option in the theme?