mirror of
https://github.com/NixOS/rfcs.git
synced 2025-11-08 11:36:12 +01:00
Make the detailed design terse by separating examples (#60)
This commit is contained in:
parent
17e6306f41
commit
337b3d7962
1 changed files with 13 additions and 4 deletions
|
|
@ -22,10 +22,19 @@ outcome?
|
|||
# Detailed design
|
||||
[design]: #detailed-design
|
||||
|
||||
This is the bulk of the RFC. Explain the design in enough detail for somebody
|
||||
familiar with the ecosystem to understand, and implement. This should get
|
||||
into specifics and corner-cases, and include examples of how the feature is
|
||||
used.
|
||||
This is the core, normative part of the RFC. Explain the design in enough
|
||||
detail for somebody familiar with the ecosystem to understand, and implement.
|
||||
This should get into specifics and corner-cases. Yet, this section should also
|
||||
be terse, avoiding redundancy even at the cost of clarity.
|
||||
|
||||
# Examples and Interactions
|
||||
[examples-and-interactions]: #examples-and-interactions
|
||||
|
||||
This section illustrates the detailed design. This section should clarify all
|
||||
confusion the reader has from the previous sections. It is especially important
|
||||
to counterbalance the desired terseness of the detailed design; if you feel
|
||||
your detailed design is rudely short, consider making this section longer
|
||||
instead.
|
||||
|
||||
# Drawbacks
|
||||
[drawbacks]: #drawbacks
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue