Replies: 14 comments 59 replies
-
|
AFAIK, CSS layers and brew themes are coming with v4, aren't they? I'll add to this the idea for the editor modes(pop out editor, or being able to change it to the right of the brew) as it is related to the responsive design. #2780 And if we can, Less and Sass support would be nice to have too, as well as CSS Folding. #2793 |
Beta Was this translation helpful? Give feedback.
-
Like a full refactor?
Do people do this? try to author on phones or is there something I don't understand? |
Beta Was this translation helpful? Give feedback.
-
|
d) simultaneous editing by multiple authors |
Beta Was this translation helpful? Give feedback.
-
|
e) spellcheck. F) snippet preview?
I) OUR OWN PDF RENDERING, i want bookmarks
K)BLEEDING |
Beta Was this translation helpful? Give feedback.
-
|
For adding comments to brews I simply use html comments. <!-- this is a comment -→There's even a keyboard shortcut for it, and it is easy to select whole brew paragraphs (etc) and then comment them out. (It does mean it still shows in the rendered html source. I'm OK with that.) |
Beta Was this translation helpful? Give feedback.
-
|
As talked about in Gitter today, we might want to add/change writing syntax for some things, like adding underline syntax:
also italics could use
L. Copy button next to Code blocks |
Beta Was this translation helpful? Give feedback.
-
|
Based on the discussion on Gitter chat, the next syntax ideas might be the ones actually used in v4:
Not agreed upon yet
In all of these cases the syntax can be somehow achieved using curly spans or block syntax, i don't want to add it every time or this table would be big as hell. If i have left something out, be sure to comment so i can edit this table. |
Beta Was this translation helpful? Give feedback.
-
|
Using This brew source.. .. renders to <ul>
<li>item</item>
<li>item</item>
<li>item</item>
</ul>
<ul>
<li>item</item>
<li>item</item>
</ulThis is useful. I have used this when writing up long bullet list outlines where I want to keep different sections separate. |
Beta Was this translation helpful? Give feedback.
-
|
What about adding thumbnail generation? It is fairly easy. |
Beta Was this translation helpful? Give feedback.
-
|
A couple more possibilities: Index Markers (already in #3133)Basically Which makes me think perhaps we can extend headers in a similar way to guide TOC generation instead of relying upon CSS TOC MarkersSome permutation of |
Beta Was this translation helpful? Give feedback.
-
|
Table column width syntax as talked about here #1528 |
Beta Was this translation helpful? Give feedback.
-
|
Another proposal for V4: Change Already in CommonMark, we have a way to generate To get a series of breaks. It seems we could just build on that to allow In the same way we already use |
Beta Was this translation helpful? Give feedback.
-
Table of ContentsI think we can move away from using headers in the formatting of the Table of Contents. So instead of this: {{toc,wide
# Contents
- ### [{{ cat}}{{ 3}}](#p3)
- #### [{{ dog}}{{ 3}}](#p3)
}}we have this: {{toc,wide
# Contents
- [{{ cat}}{{ 3}}](#p3)
- [{{ dog}}{{ 3}}](#p3)
}}Semantically, a table of contents shouldn't be written as headers itself. Further, it would make the HeaderNav easier, because right now we have special logic to keep the ToC headers from appearing in the HeaderNav. Edit We could go further in simplifying the ToC if we didn't care about semantics.....Instead of {{toc,wide
# Contents
- [*cat* *3*](#p3)
- [*dog* *3*](#p3)
}} |
Beta Was this translation helpful? Give feedback.
-
Font ImportsIt'd be nice to make font imports easier. So that in the Style Editor, one could do this: Or similar, and essentially get this: This utilizes the CDN for fontsource.org, which is basically Google Fonts (same library, plus some more). It's not google fonts, because Google changes their fonts with updates and are not versioned, whereas fontsource can be (or like above, set with Fontsource offers two regular patterns for their URLs, depending on variable or static: I would expect this to be something entered in the Style Editor, not the Markdown/Brew editor, so I think it'd be the first foray into processing a new syntax in the CSS document? And to keep it valid CSS, it would be wrapped in a CSS comment syntax, in case someone is taking the CSS portion and trying to use it elsewhere. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Opening this discussion to collect ideas in a 'next big version'. There are other discussion threads that focus on more specific aspects of Homebrewery, which I'll link to, but for things that don't have or need their own thing, here we go:
a. Typescript
b. Responsive/Mobile UI (and codemirror 6?)
c. Two-way interaction between renderer and editor (d3.js?)
Beta Was this translation helpful? Give feedback.
All reactions