Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Improve the writing on the "why Toolpad" doc #3377

Merged
merged 8 commits into from
Apr 11, 2024
10 changes: 4 additions & 6 deletions docs/data/toolpad/studio/getting-started/why-toolpad.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Low-code tools can be hard to extend. When the tool can't handle a particular ta

This lack of flexibility often results in being stuck or having to write custom code inside these apps and storing the business logic within their configuration files.

Would it be great if the tool would use code in your filesystem as the source of truth?
Wouldn't it be great if the tool would use code in your filesystem as the source of truth?
Janpot marked this conversation as resolved.
Show resolved Hide resolved

### Duplication of logic

Expand Down Expand Up @@ -94,13 +94,11 @@ Similar to any Node.js application, you have the flexibility to self-host a Tool

Like any Node.js app, you can self-host a Toolpad Studio app on your own server or any hosting provider of your choice (such as AWS, Render, Railway, or Heroku). Toolpad Studio does not lock you into its cloud hosting.
Janpot marked this conversation as resolved.
Show resolved Hide resolved

### Seamless collaboration
### Collaborate as programmers

The Toolpad Studio application configuration is saved in YAML files, which can be conveniently added to Git or any preferred version control tool for collaborative maintenance. Maintaining a private code repository is a fundamental practice for enhancing the security of user data. This eliminates the need to create new collaboration mechanisms for engineers, as the existing tools can be effectively leveraged.
The single source of truth for Toolpad applications is stored in plain YAML files. This means your whole Toolpad application is stored the same way you store your other code. You are therefore free to use whichever source control system you like and collaborate with your team members as you are used to from your other developer workflows.
Janpot marked this conversation as resolved.
Show resolved Hide resolved

### Trust and safety

While organizations make every effort to protect highly sensitive data and conduct thorough vendor due diligence and compliance assessments, data breaches continue to be a significant concern. Toolpad Studio ensures that you can maintain control over your data, helping to address this issue.
Storing Toolpad application configuration in plain text files on disk allows for storing the Toolpad project in the same repository as your other code and version, test, and deploy it together. Thus eliminating split brain situations between your applications.
Janpot marked this conversation as resolved.
Show resolved Hide resolved

## How is Toolpad Studio different from other tools?

Expand Down
Loading