Paul Jackson
Paul Jackson
All the digital playbook content should be made available as a dataset (e.g., JSON, XML), so it could be used in non-HTML scenarios (and even for HTML scenarios such as...
Currently this is a manual process and would reduce effort if Travis could deploy to gh-pages automatically after each merge to master. Instructions can be found here: https://docs.travis-ci.com/user/deployment/pages/
Should build it so it is compatible with WET4 (built like a plugin) and then later contribute it if there is interest.
The dataset approach that is under development is primarily text-centric, but how should it deal with images and videos? It is likely that the playbook content will include images (and...
What type of automated checks should be set up for the dataset and the authoring methods that feed the dataset? There will be alternate views that are dependent upon the...
Currently the playbook is being output to GitHub pages, but what about when it is time to officially publish the playbook to Canada.ca? The dataset could be made available through...
With the dataset approach under development (generating views from a JSON dataset using Kramdown and Jekyll/Liquid), the next logical step could be providing an actual API for the playbook. How...
To make it easier to tell what has already been tagged for filtering and what those tags are (dpgn- classes) there should be an option in the filtering interface to...
Currently you have to go into the filter panel to tell which filters are active (use "Show filters" button). It would be helpful to have the active filters visible outside...
For the [GC Digital Playbook](https://canada-ca.github.io/digital-playbook-guide-numerique/en/overview.html) we borrowed your Jekyll theme work for the Canada.ca theme and them ported it over to using the Centrally Deployed Templates Solution (CDTS) managed by...