My understanding is that if a person is able to learn Markdown, a person can learn the basics of CSS. I can have red h1 for Markdown content in core text, in nodes with the Style Important, but not in Markdown content in note of the same nodes, or on different nodes (with other Styles). Using Styles provides the same benefits we already know from styling nodes, e.g. The idea is to provide the ability to format not only Markdown but also the rich-text content of details, notes and core text (if User chooses to use rich text). What I am proposing is to add the possibility to define CSS instructions for each HTML/Markdown content (separately for core, details, note), on a Style level. And the standard way to style HTML is by using CSS. Therefore my assumption is that, in Freeplane, Markdown can be styled the same way as HTML can be styled. Each Markdown directive has its HTML counterpart and in most cases (frameworks/libraries) Markdown is converted to HTML to be displayed. Markdown is a special way of creating rich-text content - one could say it's a simplified HTML. Freeplane stores such rich-text content as HTML. In Freeplane, I can format nodes (including plain text of node core) as part of Style formatting - be it a predefined or user-defined Style, or an ad-hoc/manually applied style in Tool Panel > Format.įor rich-text content (SimplyHTML dialog), I can apply specific formatting on a paragraph/word/letter level. I should have started by describing the as-is functionality. If this solution is agreed, we can work out the implementation Yes, I believe we are thinking along the same lines when it comes to Markdown: to provide the option to style the specific tags (h1, etc) In terms of conflicts, the Markdown styles would be a layer with higher priority than manually assigned individual node styles, but lower priority than text styles designated by HTML tags on individual would this solution satisfy you? If I put a H1 # indicator in a note, it should be formatted according to the H1 style in the Style Editor. The configuration should apply to node core, details, and notes. Should the configuration be different for node core, details and notes? It would apply only to specific Markdown categories Should this configuration apply only to markdown or also to any other html which is edited in the embedded rich text editor? Use existing UI interface for node formatting. Should user configure it by editing a CSS snippet or using UI to select fonts, font sizes, bold/italic properties and so on? Should markdown formatting become a part of a user configuration (making the markdown look different on different computers and for different users), a map or of individual nodes/ styles? So my answers to Dimitry's questions are: It would allow all of the style changes needed without requiring users to learn css. Users could style these nodes using the existing FP interface, and these styles could be saved to individual maps or templates as current styles are. The new category would be called "Markdown styles" and would auto-populate with the limited number of categories relevant to Markdown. Here is my suggestion for feedback: allow users to create a category in Style Editor parallel to technical styles, user-defined styles, and level styles. I think that it is a slightly different issue than Markdown formatting specifically because it could be implemented in the current interface and apply to more than just Markdown. I am thinking that the best solution would use FP's current Style Editor so users can use the same familiar interface to format both nodes and Markdown categories, as mentions in their "So that" your suggestion to allow CSS styling overrides in the Style Editor is interesting and I am not against it.
0 kommentar(er)
