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

Replace the need for the customizer when using a FSE theme #915

Open
carstingaxion opened this issue Jan 30, 2023 · 3 comments · May be fixed by #919
Open

Replace the need for the customizer when using a FSE theme #915

carstingaxion opened this issue Jan 30, 2023 · 3 comments · May be fixed by #919

Comments

@carstingaxion
Copy link

Hello everyone here,
hello @westonruter,

when using a full-site-editing theme together with the pwa plugin, the only need for having the customizer visible is the setting to set the site_icon_maskable option.

I thought about creating a higher-order-component for the core/site-logo block to fill this gap.

What do you think?

@westonruter
Copy link
Collaborator

Hey, I'm not very familiar with it, but that sounds good.

@carstingaxion
Copy link
Author

carstingaxion commented Jan 31, 2023

Hello again,

I'm sorry that my initial statement was maybe not that clear.

I was looking for a native way to handle the site_icon_maskable setting within a full-site-editing context, more clearly - adding this setting to the <InspectorControls> panel of the existing core/site-logo-block. Currently we have this UI only available inside the customizer, which is not that futureproof. Take a look at my first try.

pwa-wp__maskable-Icon-for-the-site-logo-block

I would like to contribute this to the plugin, if you're interested and we are able to solve some last issues.

@carstingaxion
Copy link
Author

carstingaxion commented Feb 1, 2023

To bring theese changes to life, I think the following needs to be looked at:

  • Where to put the source files, currently in ./site-icon-maskable?
  • Integrate with npm run build and find a place for the (files of the) build directory?
  • Use _pwa_print_build_needed_notice instead of the current throw new Error.
  • Add more inline-documentation
  • Add tests

For later

  • Replace Flex & FlexItem with a non-experimental version of __experimentalHStack as soon as soemthing is available
  • Replace __unstableBase with something non-experimental as soon as soemthing is available

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants