This week was a wild ride. It consisted of focusing on documentation again which led to some major refactorings along the way.
Then we had a wholesome and interactive virtual coffee meet with the wonderful KarenTestsStuff(here is the Meetup if you want to join us some time).
Right after the meetup I noticed my Twitter account got permanently suspended, which was a real bummer with no chance to appeal as the mailserver of Twitter Support broke down 😥. Any help is appreciated to get it back...
And I tried out Github Codespaces and Stackblitz out of curiosity.
Docs Again
With our goal for the next two and a half months to improve our onboarding drastically, we looked again at our docs.
We found several issues and solutions:
- Too many clicks to even get to the Getting Started-Page -> Remove everything before it and link straight to it.
- Our terminology is all over the place having several terms for the same thing -> Create a menu item Terminology to get a clear understanding (I learned something there, too 😂)
- Rework the whole structure, so a user can follow along a given path. Before it was all mixed up.
- Add a Start-page where you can choose between two paths to trying out our product and local installation.
Trying out Github Codespaces and Stackblitz
First impressions of Github Codespaces:
- Easy to start directly from your Repository without any configuration
- With blazingly fast startup times for default containers (they are prebuilt I believe)
- Feels like Gitpod
- If you use a customized container the startup times are the same as with Gitpod
First impressions of Stackblitz:
- The startup times are in the seconds
- Webassembly based, thus running completely in your browser
- Stripped down operating system
Maybe I will try out Stackblitz for my personal blog as it feels really well done 🥳
Top comments (0)