FarosCMS 0.1.54

• The main content can be written visually, and is still saved as Markdown. Visual (the default) shows the text as it will look on the site, with a toolbar: a style menu (paragraph, headings 2 to 4, code block), bold, italic, strikethrough, code, link, lists, quote, image (library or address, with a description), table (with + Row and + Column), divider, undo and redo. Typing ## , - , 1. or > at the start of a line makes a heading, list or quote; pasting from Word, Google Docs or a web page keeps bold, italic, headings, lists and links and drops the rest; pasting Markdown draws it. Markdown is the plain text with its buttons; the choice is remembered. If the visual editor cannot start, the Markdown is shown and nothing is lost
• The file does not change under your hands. The server draws the Markdown block by block with the lines each block came from (POST /admin/markdown-visual, VisualMarkdown); nothing is written until you type, and a block you did not touch is written back exactly as it was, so only what you changed is rewritten and the History shows that. Raw HTML is shown as an HTML box that is never run in the admin and is kept character for character, so embeds survive and the raw-HTML guard for editors still recognises them; underline and embeds are offered only to people who may write HTML
• Strikethrough works on the site: ~~text~~ is now drawn as struck text (the Strike button always wrote it)
• The entry screen is rebuilt in the style of the other settings screens. The first tab is Content: a large title with the web address under it, the main content in a wide editor, and the excerpt, with a side card to publish (status, language, template, date, author, visibility) and the title area. The title shows a pill for draft or published beside the language. Media has a small preview next to the address of the image and its buttons; Taxonomies are choices you tick as chips; Custom Fields, Translations and History are compact rows; SEO shows how the entry will look in a search result as you type, and the sharing fields follow it
• Tests: a unit test of how the Markdown is drawn (tests/unit/visual-markdown.php), an HTTP test of the screen, the endpoint, who may use it and what is saved (tests/http/editor_visual_test.py). The part of the editor that turns the page back into Markdown runs in the browser; it was checked by hand against 28 pieces of Markdown (headings, nested and loose lists, quotes, code, tables with alignment, escapes, shortcodes, raw HTML, links, images, definitions, Greek text) by writing each back and comparing what the server draws, and has no automatic test yet. The full suite and CI were not run