Conversation
|
Curvenote Preview
|
tarleb
left a comment
tarleb
left a comment
There was a problem hiding this comment.
Thumbs up from here 👍
I'd like to throw out there the idea of renaming Code to CodeListing, just because that seems like a nice name and would keep naming closer to HTML. But I also like the "blocks first" naming convention.
| - **Emphasis** | ||
| - **Strong** | ||
| - **Superscript** | ||
| - **Subscript** |
There was a problem hiding this comment.
We could also include Strikethrough/Strikeout and Underline. Although they are slightly more contentious.
There was a problem hiding this comment.
Lets punt those to a new RFC. Going to do an implementation for this for now.
|
|
||
| Excluding these nodes at this stage is a deliberate choice to keep the initial core small, stable, and easy to implement. | ||
|
|
||
| ## Naming Conventions and Design Trade-offs |
There was a problem hiding this comment.
This is an excellent, well-considered, section. Thank you!
There was a problem hiding this comment.
Awesome.
@tarleb I am going to add that we considered CodeListing / Code, but going to take your thumbs up!! :)
rowanc1
added
active
|
I am going to move this one forward. RFCs are editable (keeping the same scope) so we could always revisit...! |
3 participants
This opens up the initial nodes. I have opted not to talk about a document/root type yet (maybe a mistake?). I am hoping these are not controversial. The naming convention needs some review, I went back and forth and don't quite remember the conversations in November or where we landed.