Skip to content

Home

Jump to bottom
Hugo - hnla edited this page Jun 2, 2016 · 12 revisions

##Welcome to the next-template-packs wiki! ###Project Outline, Planning, and Timescale pages

See menu for detail tasks

New Templates Action Plan:

Outline action plan for development of new templates,

project scope and implementation

Provisional project timescale:

Commences: ASAP - essentially commences from now. (09/05/16)

Estimated Completion: approx end of 2.8 or late Autumn (fall)?

Primary Tasks

  • Add template files - basic revision for better markup, clean id/class tokens.

  • Wireframes to discover components UI/UX - previous TP wireframes may help as a starting point? - BPDevel Chat wireframes 2012 - karmatosed/buddypress-templates Wireframes as a task can run alongside other tasks as those are being pulled into shape, doing this helps to prevent roadblocks while discussions underway.

  • Re-implement JS to be modular (breakup and discard existing)

  • Re-factor a primary stylesheet for a more modular ruleset approach.

  • Build new template parts for core markup re-factoring.

  • Review components and visual layout aspects, add design where possible within constraints of theme compatibility and parent themes.

Timescales are very lose!

Weeks 1 - 4

Initial ongoing discovery phase (first two weeks max! ?)

  1. Discussions to ratify:

  • JS approach - modular? Imath already taking the approach I favour

  • Approach to working in new include dirs and template parts to handle breaking out core markup to templates directories

  • Any additional aspects needing a lose consensus.

  1. Setup github repo

  2. First/Second passes at templates cleanup and token updating - hnla undertaking - tickets/issue to be created off the back of initial work for tokens, general markup changes, & issues needing discussing.

  • Index Dir templates re-factoring to pull out filters & nav functions to single include files.

  1. Further clear down/ strip out js to only essential requirements

  2. Re-factor a new empty stylesheet to handle primary styles, structure this file along modular lines - modular CSS – BP pattern library.

  • Group discussion to establish the best layout for this SCSS/CSS. Agree or not whether we sass things moving forward.

  • Group discussion on template markup and token choices to be opened.

Weeks 2 - onwards

Template files can be hacked away at while we might still be discussing/deliberating finer points.

On copies of existing template files, we can begin by stripping out majority of ID's & Class tokens, leaving perhaps only those that are obvious e.g .bp-lists to cover generic lists in BP components, .members-listfor specific, bp-table. We can also add tentative data-*="" attributes to elements as we go (imath will have some already in place and in use)

Ongoing identification and re-factoring of core markup to template directories, this task spans both old legacy templates and new. We will push these changes as they occur into the new templates see #6844 (this aspect does not need to be 100% completed as it's approach should always be essentially backward compatible, not breaking layouts)

Weeks 6 - onwards

With templates, asset files JS, CSS, and basic stylesheet styles in place or well underway, starting to realize wireframe designs can begin.

Clone this wiki locally