Please Note: I will be in France between May 25 and June 11. I will have internet access, and I will be able to contribute, but not as much so as usual. In preparation for this trip, I will start work on my deliverables several weeks early. I finish my final exams on May 4th, so I will have more time than the usual student during the community bonding period and can work on my first set of deliverables (which coincidentally will not require much WordPress reference) during that time.

Deliverables will consist of major functional benchmarks:

1. A CSS library designed for positioning DOM elements (Weeks -3 – 1)

  • Grids-based, but adjustable
  • Calculate values within the library from three of four input values: number of columns, column width, gutter width, and website container width
  • Cross-browser compatible

2. An editor that outlines block elements to create the appearance of a wireframe (Weeks 1 – 2)

3. Modify the wireframe by clicking on an element and adding a row/column adjacent to the element, or by clicking on and removing an element (Weeks 3 – 4)

  • Automatically adjust affected surrounding elements’ CSS

4. Resize elements within the wireframe by dragging element borders (Weeks 3 – 4)

  • Also, the ability to align elements left/right/center
  • Automatically adjust affected surrounding elements’ CSS

5. Allow the user to add CSS styles (Week 5)

  • Via uploaded file (which could be accessed in the editor)
  • Override any user-input styles that would affect the structural CSS
  • A potential future modification could allow users to directly edit structural CSS

6. Position content modules within the theme by dragging module titles into wireframe elements (Weeks 6 – 7)

  • Titles would initially be found in a list of content modules (such as post content, widgets, menus, etc.)
  • The main “content” module would refer to a separate PHP file that would act similarly to the common theme’s index.php and redirect to the proper files for each page type (front page, archives, etc.)

7. Allow the user to create multiple pages per theme (Week 7 )

  • If the designer wants various pages to differ in style (e.g. front page and archives), the theme can refer to separate structures for specific pages.

8. Compile and save the theme (Weeks 8 – 9)

  • Compile a structural CSS file that only includes the portions of the library used by the theme
  • Compile a PHP file that includes the structural framework and the functions necessary to load the page content
  • Set a variable that defines the template as “framework compatible”

9. Load and edit “framework compatible” themes (Weeks 9 – 10)

  • Generate the wireframe from the compiled PHP file
  • Generate the CSS library from the values within the compiled CSS file

10. Documentation and testing/debugging where necessary (Weeks 11 – 12)