This document provides guidance for how YOU can collaborate with our project community to improve this technology.
Meet and join our Team of Contributors.
This section includes ways to get started with your open source project. Include links to documentation and to different communication channels:
- Github Discussions
- Used for questions and discussions of interest to the broader community.
- Link: https://github.com/discoverfinancial/a11y-theme-builder/discussions
- Slack
- Used for questions to project maintainers or for private chat.
- Link: https://a11y-l464962.slack.com
- Blog/Wiki
Participating in our project community spans a variety of activities:
- Reporting bugs and enhancements requests
- Contributing bug/feature solutions
- Improving documentation
- Identifying and tracking new use cases
- Create an example of the project in real world by building something or showing what others have built.
- Blog about other people’s projects based on this project. Show how it’s used in daily life. Take screenshots and make videos!
To join our community see the Onboarding Resources page in the wiki.
Our project uses a combination of GitHub Issues and Project Kanban Dashboards to manage sprint plans.
Our vision for the maturation of this project is outlined in the Project Roadmap which is reflective of our intended milestones/release plan.
Logistics for Project Triage Sessions:
Project Management:
When submitting Issue/Feature Reports, please use the provided templates and try to convey answers for the following:
- Is the bug reproducible as explained?
- Is it reproducible in other environments (for instance, on different browsers or devices)?
- Are the steps to reproduce the bug clear? If not, can you describe how you might reproduce it?
- What tags should the bug have?
- Is this bug something you have run into? Would you appreciate it being looked into faster?
Strategically, Discover Financial Services intends for this repository to be promoted for maturation upstream within a yet-to-be-identified community such as FINOS, The A11y Project, or OpenJS. Once we see broader community contributions we will aggressively work towards that the promoting of this project. If and when such a transfer occurs, normal pull request
based contributions will be possible.
For the tactical timeframe (for as long as this repo resided within the DFS GitHub organization), pull request
will not be accepted. For those willing to
answer our call for contributions, please proceed by:
- 'forking` one of the project repositories
- Developing a contribution within your forked repo
- Opening an issue or feature enhancement report where a redirect to the new contribution (forked repo) is captured.
- Add the GitHub Topic
a11y-tb
to your forked repo for that we can query all of GitHub for available features and fixes to import.
- ReactJS:
PascalCase
: ReactJS components, interfaces, component file names (tsx, jsx, css)camelCase
: JavaScript data variables, functions, non-component file names (ts, js, css)- Tab: 4 spaces
- NodeJS:
camelCase
: JavaScript data variables, functions, non-component file names- Tab: 4 spaces
- CSS:
kebab-case
: CSS variables- Tab: 2 spaces
- Other
kebab-case
: Directories and file namesUPPERCASE
: Some root markdown files that are commonly all caps
References:
- ReactJS coding conventions
- React Best Practices
- Case Styles: Camel, Pascal, Snake and Kebab Case
- camelCase
Testing new releases and/or features is a great way to contribute to the community. If you find issues, please submit an Issue/Feature Report.
Learn how to develop, build, test, and contribute to the online docs.
Our project aspires to be globally applicable but that requires internationalization support beyond the English language. We seek help in:
- Providing instructions for extending internationalization support;
- Providing specific language translation enhancements.