Things to be done:

  1. create a child page at http://drupal.org/node/196218
  2. link the child page on the project documentation
  3. gather all documentation in the issue queue and transfer it to the documentation
  4. update the documentation for current dev
  5. fill up the missing documentation gaps

Comments

andregriffin’s picture

This is a good idea. Also, depending on how much Zen code we reuse, it would be nice to add documentation for each tpl file and it's variables, like Zen does (http://drupal.org/node/1728090). Then add the add the link to the documentation at the top of each tpl, respectively.

markhalliwell’s picture

Created child book page: http://drupal.org/node/1976938

markhalliwell’s picture

Issue summary: View changes

Updated issue summary.

markhalliwell’s picture

Converted the markdown readme of the "sub-theme how to" at: http://drupal.org/node/1978010. We should probably make a beta4 release so these pages and project page can be updated accordingly.

markhalliwell’s picture

Assigned: Unassigned » wundo

Actually I'm thinking we should just include the link to the root documentation page and the "Creating a Bootstrap sub-theme" page inside the project's README and take the documentation out of the project. It will help reduce duplication and inconsistency errors.

markhalliwell’s picture

Status: Active » Fixed

Done. I removed the documentation from the repo and provided the above links instead. I also updated the project page. This allows the updating documentation much easier since it's separate from the repo.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Updated issue summary.