-
Notifications
You must be signed in to change notification settings - Fork 263
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
Playground User Documentation #1074
Comments
Adding some parts of our private conversation to keep as record, the information will be very useful when writing these articles. @adamziel mentioned the following:
|
Maybe we can use/repurpose the no-code and low-code sections of my Developer Blog article? |
Updated a bunch of pages as starting points, many with links to relevant issues
The developer blog content for sure needs to be included here... working on consolidating all of the information to a single source for now :) |
@ironnysh - Just getting back to this - I tried to organize everything and didn't get it quite ready. Yes, your introductory post is very helpful for end-users, and should be repurposed. What I did a couple of weeks ago was to go through all of the issues and organize as well as I could into a single repo, The workflow I went through was to look at all available docs, print them out, mark them up, and they have been somewhat cross-referenced in the docs updates. But it's not past the finish line yet Had no idea how much of an undertaking this would be :) Over the next week or so I'll put some time into this and get some PRs in for it assigned, I'll get some content in soon! |
@adamziel - if you can please remove me as assigned, this is beyond the scope of what I can do for right now |
Let's create resources for Playground users to cover topics such as:
Related #772
CC @estelaris
The text was updated successfully, but these errors were encountered: