search

WordPress / wordpress-playground

Run WordPress in the browser via WebAssembly PHP
https://w.org/playground/
GNU General Public License v2.0
1.58k stars 222 forks source link

(Meetup use case) Add interface-based solution for saving / re-using the result of the session #1537

Open IoanaAMuresan opened 1 week ago

IoanaAMuresan commented 1 week ago

In light of using Playground to effectively demonstrate the value of WP to first time users, it would be helpful to have a straight-forward way to keep the work done in the session.

This could be done by offering:

Ideally - for ease of use in the meetup - these would be present directly in the interface, possibly on the Home tab, or - alternatively - under Tools.

If it's not helpful to have it in the general tool, these could be part of the 'filtered' meetup blueprint (https://github.com/WordPress/wordpress-playground/issues/1536)

bgrgicak commented 1 week ago

This fits in nicely with the discussions we had about Playground inputs and outputs where a user could load Playground data from different sources like browser storage, ZIP, Git.. and save it to any of these destinations once they are done with using Playground.

bgrgicak commented 1 week ago

a no-fuss upload to WordPress.com - similar to the one in Studio

Playground shouldn't favour any hosts, but it would be great if it could support a custom export process that hosts like WP.com could use.

For example it could be a blueprint step:

{
  "step": "export",
  "URL": "https://host.com/start-from-playground/"
  "title": "Export to Host.com,
}

The custom export could send a ZIP with the full export to the specified URL if the user chooses to use this export mode.

bgrgicak commented 1 day ago

@jarekmorawski this could be related to your redesign work.

jarekmorawski commented 22 hours ago

Yup! It'd be part of a more robust exporting flow, which currently only includes downloading a .zip file and creating a GH PR, but could be extended to include other options, like publishing on WordPress.com and/or other hosts. I'm happy to mock it up and align with how Studio handles it, but we need to crystalize the overall approach to imports/exports first.