Support
Cornerstone Components is built for Cru and FamilyLife product teams. Both packages are published publicly on npm and anyone can install them, but the support model follows who the library is built for: it is staffed by the Cru and FamilyLife teams rather than run as an open-source project, so expect an internal cadence rather than a community one. Bugs and requests go to the repository. If you have not used the library before, start with Where to start on the home page; if you are wondering whether something is already planned, the roadmap lists the efforts underway.
Bugs and requests
Open an issue so it can be triaged and tracked. One issue per problem, and say which version you are on.
- For a bug, give the steps that reproduce it and what you expected instead.
- For a component that behaves differently across browsers, say which ones you checked.
- For a new component or a new option on an existing one, describe the case it has to serve rather than the API you would like.
A report that is accepted is often closed here with a pointer rather than left open, because this tracker holds the project's open questions rather than its task queue — scheduled work is tracked by the team internally. A closed issue is not a declined one, and the roadmap is where an effort shows up once it is underway.
The repository
Watch the repository to follow releases and see what is being worked on. The changelog records what changed in each version, including the breaking changes.