mirror of
https://github.com/nocobase/nocobase
synced 2024-11-16 08:35:13 +00:00
22 lines
1.7 KiB
Markdown
22 lines
1.7 KiB
Markdown
# Why NocoBase is different
|
|
|
|
## 1. Separate "data structure" and "user interface"
|
|
|
|
Most form-, table-, or process-driven codeless products create data structures directly in the user interface, such as Airtable, where adding a new column to a table is adding a new field. This has the advantage of simplicity of use, but the disadvantage of limited functionality and flexibility to meet the needs of more complex scenarios.
|
|
|
|
NocoBase adopts the design idea of separating the data structure from the user interface, allowing you to create any number of blocks (data views) for the data collections, with different type, styles, content, and actions in each block. This takes into account the simplicity of codeless operation, but also the flexibility like native development.
|
|
|
|
|
|
|
|
## 2. Integrate "system configuration" and "system use"
|
|
|
|
NocoBase enables the development of complex and distinctive business systems, but this does not mean that complex and specialized operations are required. With a single click, configuration options can be displayed on the usage interface, which means that administrators with system configuration rights can configure the user interface directly with WYSIWYG operations.
|
|
|
|
|
|
|
|
## 3. Everything is a plugin
|
|
|
|
NocoBase adopts plugin architecture, all new features can be implemented by developing and installing plugins. In the future, we will build a plug-in marketplace where extending functionality is as easy as installing an APP on your phone.
|
|
|
|
|