Files
wekan/docs/Design/Design-Principles.md
T
Lauri Ojansivu 54cc0ec614 docs: organize docs/Features into categories and update all links
Move the flat feature docs and feature subdirectories under category
parents: Admin-Panel/ (+ Problems/), Board/, Cards/, Editor/, Reports/,
Automation/, Lists/, Troubleshooting/. Every relative markdown link in
docs/ (and the docs GitHub URLs in CHANGELOG.md and the code-span path
in Undo.md) is recomputed so it still resolves to the same target after
the move.

Done with a scripted move + relative-link rewriter that verifies link
integrity: all 160 rewritten links resolve, and a full scan confirms the
reorg introduces zero new broken docs-internal links (the pre-existing
53 unrelated to the move are unchanged).
2026-07-20 13:37:44 +03:00

2.0 KiB

WeKan Design Principles

  • 2024-08 Design discussion here: https://github.com/wekan/wekan/discussions/5507
  • Original WeKan Design:
    • Uses WeKan style confirm popups Popup.afterConfirm( , translations etc. Please look at existing code to keep same style.
    • Kanban, the good parts. Like was done when figuring out best design for Swimlanes https://github.com/wekan/wekan/issues/955
    • Intuitive, easy to figure out, prevent messing up something Monkey Proof Software
    • Polished UI/UX
    • Menu options are there where you would expect then to be.
    • Try to fix anything unexpected.
    • New features added there where it makes most sense.
    • Not too many toggles and settings, because that is worse. For example, Discord settings has too many toggles and settings. Just select some default.
    • FOSS with MIT license
    • Swimlanes
    • All the use cases of WeKan feature/fix contributors
    • Cross-platform. Support many CPU/OS/Browsers for Desktop and Mobile.
    • Support many browsers Browser compatibility matrix . Add support for more.
    • PWA PWA
    • On-Premise:
  • Not like other software:
    • But note that design of all software changes often, when they are in active development.
  • Not bad parts of Trello:
    • Not the exact design of Trello FAQ
    • Not so many duplicate menus and texts like Trello
    • Not so much empty space
  • Some good parts of Trello:
  • Some good parts of Jira:
    • Multiple assignees