You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Docs] Rework the documentation to focus it on use-cases #386
Split theUser guide into multiple Guides per use-case
Dev environments
Pipelines
Apps
Artifacts
Projects
Home page
Update the tagline
Rework the features section
Rename Tutorials to Examples
Restore Installation
Update the REAMDE.md
Fix minor TODOs (see the TODO [TASK] comments)
Add Best practices
FAQ
TO BE DONE SEPARATELY
There are still a lot of major limitations for each use case. The documentation will change once they are resolved. For the details, see the TODO [MAJOR] comments in the code.
Currently, we use "providers" as an abstraction to implement custom types of both "dev environments", "pipelines", and "apps" which is too low-level. We may need to rethink the concept of "providers" at least on the user level.
changed the title [-]Rework the documentation to focus it on use-cases[/-][+][Docs] Rework the documentation to focus it on use-cases[/+]on May 17, 2023
Activity
- [Docs] Rework the documentation to focus it on use-cases #386
- [Docs] Rework the documentation to focus it on use-cases #386 (the …
[-]Rework the documentation to focus it on use-cases[/-][+][Docs] Rework the documentation to focus it on use-cases[/+]- [Docs] Rework the documentation to focus it on use-cases #386 (the …
- [Docs] Rework the documentation to focus it on use-cases #386 (the …
- [Docs] Rework the documentation to focus it on use-cases #386 (#389)
- [Docs] Rework the documentation to focus it on use-cases #386 (the …
- [Docs] Rework the documentation to focus it on use-cases #386 (mino…
- [Docs] Rework the documentation to focus it on use-cases #386 (a fe…