<!-- Please complete the following sections when you want to propose a new feature. You are encouraged to keep this top level comment box updated as you develop and respond to reviews. If you have write access to the repository, please also assign the appropriate label (or labels) to your issue. Note that text within html comment tags will not be rendered. --> ## Summary <!-- Please provide a detailed description of the feature you are writing or proposing. If you have started writing the feature, also provide details about the pull request you've made as well as the branch you've been working from. Please provide as much context as possible and link to other related issues and/or pull requests. Think about answering the following questions: - What is the name and purpose of your feature? Provide a unified but flexible way to maintaining the Common Voice Playbook. - Why are you proposing it? Community chat on matrix highlighted the differences in English US and UK on the playbook. - What section of the playbook is the feature for? It Would cover all of it but would need to be adapted to localisation needs - What branch are you working on? Not at the moment. - Have you made any Pull Requests Not at the moment. ### Discussion Points <!-- Use this section to highlight the outcomes of any discussions you have had with regard the development of this feature. YOU MAY SKIP THIS SECTION --> - [ ] *Develop a Style Guide for Common Voice Playbook* ### Resources <!-- List and describe any external resources that may be helpful when writing the feature. We suggest using bullets (indicated by * or -) and filled checkboxes [x] here --> - [ ] *Example style guide from l10n, https://mozilla-l10n.github.io/styleguides/* - [ ] *Example style guide from MDN, https://developer.mozilla.org/en-US/docs/MDN/Guidelines/Writing_style_guide* - [ ] Turing Way Style guide https://the-turing-way.netlify.app/community-handbook/style.html ## Who can help? <!-- We suggest using bullets (indicated by * or -) and filled checkboxes [x] here --> * *TBC from Community .* * *Editorial Team.* ## Updates <!-- To avoid that others have to read through the full thread of comments, update the initial issue with important updates (for example, actions or decisions taken) regularly so that all the important information is available at one glance. You may use the checklist here to get started, feel free to modify this list. We suggest using bullets (indicated by * or -) and filled checkboxes [x] here --> - [ ] Drafting Style Guide - [ ] Ccommunity review - [ ] Accessibility and Inclusion Assessment
Summary
Resources
Who can help?
Updates