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)
