Skip to content

Design Principles

Lauri Ojansivu edited this page Aug 9, 2023 · 6 revisions

WeKan Design Principles

  1. Prevent messing up something https://github.com/wekan/wekan/wiki/Monkey-Proof-Software
  2. Original WeKan Design, that WeKan currently has: Intuitive, easy to figure out, 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. And not so many duplicate menus and texts like Trello.
  3. Not the exact design of Trello https://github.com/wekan/wekan/wiki/FAQ#why-does-wekan-look-so-different-now-compared-to--v09 . Also not the exact design of any other software. But note that design of all software changes often, when they are in active development.
  4. Some features like Trello:
  1. Some features like Jira:
  • Multiple assignees
  1. Some features not in Trello, like:
  • FOSS with MIT license
  • Self-hosting
  • Swimlanes
  1. All the use cases of WeKan feature/fix contributors

Wekan

General

Security

Scaling

Migrating

Support priorities for new features and bugfixes

  1. Commercial Support
  2. Community Support
  3. Debugging

Backup

Repair

Themes

Markdown Syntax

Login Auth

Metrics, Logs, Stats

Integrations

Time

Features

Email

Required Settings

Download

Webservers

REST API Docs

REST API issue

REST API client code

Webhooks

Case Studies

Development

Issues

Clone this wiki locally