A feature's guide now sits under the menu it is used from, read from the templates rather than from where somebody once put it: Header-Bar, All-Boards, Pages, Board-Header (search and every Board View), Board-Sidebar (Board Settings, Filter, Members, Labels, Archive), Rules, Swimlanes, Lists, Cards, Member-Settings, Admin-Panel and Login-Page. Topics used from several menus (editor, history, theme, translations, email, troubleshooting) are in General. - Each area has a README mapping its menu entries to their guides and to the template or server module that implements them. Board-Header/README.md lists all 40 Board View entries with the template boardBody.jade renders; five views (Table, Calendar Mode, Time, Timeline, Map) have no guide of their own yet and say so. - Board-View.md listed 25 views while BOARD_VIEWS has 40; it now lists all of them with their English labels. - Pages keep their file names. Where a released changelog links an old path, a "# Moved" page stays there and points to the new one; test-menu.sh skips folders holding only those. - Undo was filed under Login; it is General/Undo now. - Every link in docs, code comments, scripts and tests follows the move; docsLinksResolve checks them all. Tests that read a doc follow it to its new place. boardViewSettings now fails when Board-View.md or Board-Header/README.md differs from BOARD_VIEWS, or names a template boardBody.jade does not render. Thanks to xet7 !
829 B
Markdown editor
WeKan uses a plain-text textarea to edit Markdown in card descriptions and comments, with mention suggestions and rendered previews. It does not use a WYSIWYG editor: no existing editor supports the complete combination of WeKan's Markdown, emoji, security requirements and other editing features.
Editing and rendering are separate. Markdown rendering, emoji, mentions, HTML-to-Markdown conversion and attachment links remain available. Uploaded files stay in the card's Attachments section and can be referenced from text. There is no environment variable or Snap option to enable a visual editor.
Notification email formatting is independent of the text editor. Default notification bodies use the shared HTML-escaping formatter; administrator-defined email body templates retain their existing behavior.