Skip to content

Feature Gallery #128

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.

Sign up for GitHub

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

Jump to bottom
Closed
artemiomorales opened this issue Feb 5, 2023 · 1 comment
Closed

Feature Gallery #128

artemiomorales opened this issue Feb 5, 2023 · 1 comment
Labels
[Type] Developer Experience [Type] Documentation Improvements or additions to documentation

Comments

@artemiomorales
Copy link
Collaborator

Playground has a lot of features, with ideas for more in the works. It would be good to have a feature gallery to show everything that Playground has to offer.

Implementation Ideas

By default, we could include a button to open the feature gallery when Playground is launched. The gallery would present the user with a list of checkboxes for the features, and another button to refresh Playground with the selected features enabled.

List of Features
@artemiomorales artemiomorales mentioned this issue Jun 2, 2023
Open
@artemiomorales artemiomorales mentioned this issue Feb 7, 2023
Closed
@adamziel adamziel mentioned this issue Apr 13, 2023
Closed
@adamziel adamziel added [Type] Documentation Improvements or additions to documentation [Type] Developer Experience and removed [Feature] WordPress Previewer labels Jun 2, 2023
@adamziel
Copy link
Collaborator

adamziel commented Jun 2, 2023

https://wordpress.github.io/wordpress-playground now plays the role of a feature gallery, even if the examples could be more consolidated

@adamziel adamziel closed this as completed Jun 2, 2023
bgrgicak pushed a commit that referenced this issue May 7, 2025
@ingeniumed @adamziel
[Plugin Proxy] Allow all WordPress, Automattic and Woocommerce repos (#…
0b998b2 
…128)

## Motivation for the change, related issues

Currently, the proxy is only open to very specific repos that was done
to avoid abuse when the public playground instance was used. Now that we
have a private one that we are in control of, we can open this up to all
Automattic, WordPress and Woocommerce repos. Those are trusted
Automattic repos that we control and can be assured of their security.

## Implementation details

There is a list of orgs that are allowed, and only the repos that match
these orgs are okay within the proxy. Anything else is rejected.

I've also tried to limit what's exposed via any exceptions that are
thrown for security reasons.

## Testing Instructions (or ideally a Blueprint)

- Run a php server within the public folder
- Attempt to test against an Automattic plugin that would previously not
be allowed, like Remote Data Blocks

---------

Co-authored-by: Adam Zieliński <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Type] Developer Experience [Type] Documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adamziel @artemiomorales