In QPixel, under `db/seeds/posts`, there are a number of HTML files which are starting points for various help guides and documents such as Terms of Service and Code of Conduct.
These can be edited through the user interface (by admins), at which point they accept Markdown. I've tested one of them (Formatting - which is the guide to Markdown) by converting to solely Markdown (no HTML). This saves successfully in the user interface, and can also be used to seed the database by overriding the HTML file to contain only Markdown and then running `UPDATE_POSTS=true rails db:seed`.
To me, it seems that it would be easier for editors if the files contained Markdown rather than HTML (or HTML only in those places where Markdown cannot suffice, such as to show buttons or style with classes, which seems to be rare in the existing files). This would also allow non-technical admins who are unfamiliar with HTML to edit the documents.
Is there any reason to avoid this? Is there any reason that these files need to be solely HTML?
trichoplax
·
2023-01-25T14:26:24Z (almost 2 years ago)