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

Playground User Documentation #1074

Open
adamziel opened this issue Feb 29, 2024 · 4 comments
Open

Playground User Documentation #1074

adamziel opened this issue Feb 29, 2024 · 4 comments
Assignees
Labels
[Type] Documentation Improvements or additions to documentation [Type] UI / UX / User Experience
Milestone

Comments

@adamziel
Copy link
Collaborator

adamziel commented Feb 29, 2024

Let's create resources for Playground users to cover topics such as:

  • How to test new WordPress features?
  • How to translate WordPress?
  • How to test a plugin or a theme? (on different PHP and WordPress versions)
  • How to build a WordPress theme?
  • How to build a WordPress plugin?
  • How to publish my new WordPress theme / plugin?
  • How to just play with WordPress admin?
  • How to prepare for a WordPress meetup?
  • How to save my Playground site for later?
  • How to share my Playground site with the world?
  • How to build a live preview of a plugin or a theme?
  • How to build an app using WordPress Playground?
  • How to collaborate on my Playground with a friend?
  • How to prepare a WordPress site for a video or live presentation?
  • How to prepare interactive materials for a workshop? (Playground block, wp-now)

Related #772

CC @estelaris

@adamziel adamziel added [Type] Documentation Improvements or additions to documentation [Type] UI / UX / User Experience labels Feb 29, 2024
@adamziel adamziel added this to the Devrel milestone Feb 29, 2024
@estelaris
Copy link
Member

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:

  1. These Playground tutorials would be just WordPress tutorials prefaced with “Here’s a logged-in link to WordPress admin”
  2. The only Playground specific bit would be the ability to export your site or change the PHP/WP version with a click
  3. We’d also have to find an approach to the temporary nature of Playground. By default you lose your progress on page refresh. Sometimes that’s desired, other times that may be a problem. There’s a Playground feature that automatically saves your progress, but the caveat is that if you follow another link to Playground, you’ll go right back to your previous site. I’d love to work together to adjust Playground’s behavior as needed for the best possible user experience when interacting with the tutorials.
  4. WordPress Playground Block. It shows a code editor in the thumbnail but that’s optional, you can directly embed a preconfigured Playground without any code-related UI in a blog post.

@ironnysh
Copy link
Collaborator

ironnysh commented Apr 7, 2024

Maybe we can use/repurpose the no-code and low-code sections of my Developer Blog article?

@flexseth
Copy link
Collaborator

flexseth commented Apr 7, 2024

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 :)

@flexseth
Copy link
Collaborator

flexseth commented May 5, 2024

Maybe we can use/repurpose the no-code and low-code sections of my Developer Blog article?

@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 Playground Docs Updates. The info needs to be better organized, polished and eventually published.

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Documentation Improvements or additions to documentation [Type] UI / UX / User Experience
Projects
None yet
Development

No branches or pull requests

4 participants