Skip to content

WebApp Redesign #1561

Closed as not planned
Closed as not planned

Description

@adamziel

Now that Playground supports multiple offline sites, we need a UI redesign to actually enable using it. The redesign will also unlock:

  • Support Storing Playgrounds by default
  • Managing multiple stored sites
  • Multiple data sources and targets (e.g. local → hosted, GitHub → local, etc.)
  • Integrating the Blueprints builder into the Playground webapp (and open the doors to other integrations)

Done is

@jarekmorawski is exploring it.

Activity

  1. converted this from a draft issue on Jul 1, 2024
  2. changed the title [-]playground.wordpress.net UX redesign[/-] [+]WebApp Redesign[/+] on Jul 1, 2024
  3. adamziel commented on Jul 2, 2024

    @adamziel
    CollaboratorAuthor

    Offline Playground support: Some PHP and WP versions might not be available when offline if they have 't been downloaded yet. We might need to somehow communicate that in the ux redesign, even if not in v1.

  4. jarekmorawski commented on Jul 3, 2024

    @jarekmorawski

    👋 I put together the first design draft for the new web app. It accounts for all the new functionality and reshapes WP Playground to work more like a site hub, aligning closely with the new wp-admin.

    See it in Figma

    Most notable changes

    New PG toolbar on the front-end

    I redesigned the top bar on the front-end to include a button for the new site management view. I also cleaned it up, removed some settings, and compressed all site-related options into a command bar-like UI at the top. There's no URL bar anymore because it can be accessed through the browser's regular UI.

    pg_topbar.mov

    Site management view

    Users can jump to a new site overview screen by clicking a button in the new top bar. There, they'll be able to view all their sites (temporary, saved in the browser, and local) as well as perform actions, like adding or importing sites, previewing PRs, deleting sites, duplicating sites, and editing individual settings, e.g., WP/PHP version, features, etc.

    Admin

    New layout

    The admin view borrows design cues from the upcoming WordPress admin redesign. It consists of three panels: a sidebar with a list of active Playground sites, a details area with an overview of site information and settings, and a preview frame. Users can resize the panels to accommodate their needs (handy if they want the preview frame to be larger or smaller).

    Resize

    Temporary site saving flow

    Temporary sites are Playground instances that will disappear when users close the browser tab (storage type = none). They're highlighted in the new UI to make users aware of their unique behavior and wary of possible data loss. Contextual icons, tooltips, and notices make it easy to save a temporary site in the browser (or locally) and vice versa.

    Temporary


    Other flows, including offline mode and site management actions, are described in Figma. Feel free to take a look and share your thoughts!

  5. adamziel commented on Jul 3, 2024

    @adamziel
    CollaboratorAuthor

    Surfacing the design for turning on the offline mode:

    IMG_8127

    This is the right direction, and I’d simplify this even further. We could only have two options there:

    • You have whatever you downloaded by visiting different Playground sites
    • You choose to download everything for working offline, and over time this keeps downloading new php and WP releases

    I wouldn’t offer the option to download things granularly at all. It might be useful to some, but my educated guess is most people either want full offline support or they don’t.

  6. adamziel commented on Jul 3, 2024

    @adamziel
    CollaboratorAuthor

    Aha, and the „libxml” etc checkbox can be removed as well. Let’s just ship the full-featured build.

  7. moved this from In progress to Needs review in Playground Boardon Jul 3, 2024
  8. jarekmorawski commented on Jul 3, 2024

    @jarekmorawski

    Thanks, @adamziel. Could something like this work? When online, we'd show an icon and let the user know the components (name WIP) will be downloaded automatically, but we also show a button that allows them to save everything at once. When they go offline, we'll let them know that PG can only use downloaded assets.

    image
  9. jarekmorawski commented on Jul 3, 2024

    @jarekmorawski

    Meanwhile, I put together a simple prototype to show how the user would transition from the PG site preview to the new app and vice versa. Let me know what you think.

    pg_sitemanagement_ux.mov
  10. bgrgicak commented on Jul 5, 2024

    @bgrgicak
    Collaborator

    @jarekmorawski Thank you! This is exciting.

    Here are some things that came up for me. @jarekmorawski let me know if you would like to schedule some time to chat about these.

    Design feedback

    First load

    Playground is one-click WordPress, but this UI adds more clicks on the first load. Let's adjust the flow so the user gets a temporary site first without any clicks and can store it later.

    Temporary sites

    What's the goal of saving temporary sites? For regular users, this would quickly result in a lot of sites in the sidebar or would require them to maintain the list.
    What if we don't show temporary sites in the sidebar?

    This makes me wonder if the new settings UI is a blueprint builder. I see value in storing a temporary site blueprint in Playground and loading it with one click, but only if the user decides to save the temporary site blueprint, not by default.

    We had multiple attempts at building one, but having it here makes sense.
    If we do that, let's allow users to edit settings/blueprints directly in JSON like we do in the blueprint builder.

    If we combine the ability to store blueprints with showing demos in Playground we have a blueprint gallery.
    @adamziel if we have support to display demos here, we could move the blueprint gallery into the demo section.

    Header expand/collapse

    I would skip the header expand/collapse feature. The seamless mode is intended for integration where someone wants to embed Playground as-is and allowing users to customize Playground would break that. Also, it would create an easy way for users to download the site content which we want to avoid in case of premium plugin demos.

    Changing URLs

    The current website UI has an address bar that allows us to go to different pages by updating the URL. For example, if I'm not logged in I would change the URL to /wp-admin/ to get to the login page.

    Because the Playground website is basically a browser inside a browser, we need to communicate to users where they can update the URL and make it easy.

    Logs tab

    I like the positioning of the logs tab.

    It's missing the ability to search logs like we have today.

    With the current data structure, it will be hard to implement the suggested UI because logs are stored as strings. To get info like date, we would need to parse these strings or change how we store data.

    Other comments

    • Should we have a device icon, if we have a temporary icon? This would show up when someone would use device storage, on hover it could show the path.
    • Could we also design a warning when you try to refresh a temporary site?
    • Bug: We currently can't auto login users with custom usernames and passwords, we should fix this before building the UI.
  11. 54 remaining items

  12. brandonpayton commented on Jul 31, 2024

    @brandonpayton
    Member

    I left one comment about possibly keeping temporary sites in browser storage for a short time.

  13. moved this from Project: Up soon to Done in Playground Boardon Jul 31, 2024
  14. bgrgicak commented on Jul 31, 2024

    @bgrgicak
    Collaborator

    We have a new issue for tracking project development.

    I'm closing this one because the design is completed.

    Thank you @jarekmorawski!

  15. adamziel commented on Jul 31, 2024

    @adamziel
    CollaboratorAuthor

    I'll reopen and add it to the "Projects" section of the project board to have a high level overview of the ongoing work. @bgrgicak I assume we'll also need either a milestone or a project board property?

  16. moved this from Inbox to Project: In Progress in Playground Boardon Jul 31, 2024
  17. adamziel commented on Jul 31, 2024

    @adamziel
    CollaboratorAuthor

    Ah, #1655 is playing that higher level role. Alright, let's close this one.

  18. moved this from Project: In Progress to Done in Playground Boardon Jul 31, 2024
  19. moved this from Done to No status in Playground Boardon Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions