RFCs
Want to influence what gets built next? Core is built for web professionals: agencies, SaaS companies, web shops and large platforms. We build it together with the people who use it, so before we start on a larger feature, we publish the plan here first.
An RFC (Request for Comments) is that plan: a proposal for a feature Cyberfusion is considering. Partners and customers can say whether it solves their problem before the work starts.
This article describes how RFCs are structured and how to send your feedback.
Open RFCs
| RFC | Status |
|---|---|
Manifest file (core.yml) |
Open for comments |
Send your feedback
Email support@cyberfusion.io with the RFC name in the subject, for example "RFC: Manifest file". Answer the questions under 'Questions' in the RFC. A short answer is useful too: "I wouldn't use this, because …" tells us as much as a long one.
How every RFC is structured
Every RFC has the same sections, in this order:
- Idea: what would change, in a few sentences and one example.
- Advantages: numbered, so you can refer to them.
- Questions: what we want you to answer.
- How it works: the behaviour, in enough detail to judge it.
- Examples: complete, working examples of what using it would look like.
An RFC can end with Future additions: what could follow if the first version is built.
Names of commands, packages and fields in an RFC may still change before anything is built.