RFCs are a way to start a discussion around an new feature or enhancement to Bolt.
Provide the following when posting an RFC
- A clear, and succinct title, that indicates to a reader the general idea of what is being discussed
- A brief introduction, or "executive summary", to the RFC for tl;dr type people
- Some indication as to the use-case that the feature or enhancement
Also consider that new features and enhancement must be compatible with Bolt's manifesto guidelines, in particular:
- Our slogan is "Simple, sophisticated and straightforward". This embodies everything we strive to do with Bolt: It is as simple as possible, but not simpler. It uses sophisticated technology to achieve this, and use of the system should be straightforward and evident.
- Bolt aims at three groups of users: Editors (content writers and editorial staff), Frontend developers (HTML/CSS specialists and implementers) and Backend developers (coders, dev-ops and sysops). All three are equally important.
- We will never add new features, if they detract from any of the points mentioned above. If a proposed feature makes the system harder to use, it will not be accepted. If a proposed feature is for the benefit of one of our groups of users, but disadvantageous to another, it will not be accepted.
- We will prevent feature creep: Functionality not essential to Bolt, should be implemented as separate extensions.