WET 5 - WET-BOEW documentation
We have start our planning to develop WET 5
What we need for WET 5
We would need people for the following task:
Communication lead
Being able to monitor, respond and report/redirect to whom appropriate. Ideally it will be a lead for each channel. We are looking to monitor various social media channel such as:
- Github
- GCConnex
- GCCollab
- GC Message
- GCPedia
Document the business side of WET 5
Create some documentation material to ease potential contributor to justify their work on WET 5.
- Justification template. (What it means for web team, what is the impact, what it the business need,…)
- Develop a plan and a strategy to address concern between moving from WET 4 to WET 5.
- Develop a plan and a strategy to address some WET user fears, like removing the jQuery library from WET core.
- Produce a documentation that could be easilly aligned with the TBS Digital Standard
Accessibility check and WCAG 2.1
Lead by Brad Souster Reviewing plugin and ensuring it meet accessibility as per WCAG 2.1 Level AA.
Documentating WET API/Blueprint
Lead by Pierre Dubois. Documentating WET API/Blueprint as per the design decision #5
Blog
Maintain a blog and keep it up to date about any progression made to WET 5 project.
Migration - WET 4 to WET 5
Collect early community feedback about moving from WET 4 to WET 5.
Web developer
We are looking for senior and junior javascript developper to help with coding and testing the WET 5 core. Migrating WET 4 plugin to WET 5 plugin.
Just want to contribute
Let us know and we can match you with a group.
List of todo:
- Reach out and try to being active on social media.
- Create a page with of thing that need to be addressed and/or taken care of.
- Build small prototype and have it tested with different audience (web developer, web author, WET core developer)
- Produce a documentation that could be easilly aligned with the TBS Digital Standard
- Find contributor across the spectrum and seek their feedback on the product.
- Develop a plan and a strategy to address concern between moving from WET 4 to WET 5.
- Develop a plan and a strategy to address some WET user fears, like removing the jQuery library from WET core.
Suggestion/Idea
- Use a top bar overlay to advertise the user that he are in the Basic HTML mode
- Having two build system, one for quick local developpement and the full build that may require nodeJS. Some opposition was expressed about having two different type of build.
- Support and promote mobile first design
- Create a business plan about the markup for WET 5, use focus group and explore if it makes senses
- Consider a way to have organisation to lead some WET plugin.