-
Notifications
You must be signed in to change notification settings - Fork 357
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
Byrne looks broken in the site editor #8379
Comments
This is likely the case for many Blockbase child themes (I checked Payton, Arbutus, Russell - all have it). |
I think that's fine, the people who already have the themes are presumably ok with the weirdness and we won't be exposing new people to it. There's also some issues open about blockbase children and the blockbase style variations, so possibly we could close those too, or at least they become even less urgent 🤔 I think these are all of the blockbase children:
Looking at the theme trends Marl was the fourth most popular onboarding theme (9th most popular in LITS) and it looks like it's been consistently up there over the last few months. Russel was 15th. None of the others were top twenty. |
Do you mean that we should fix Marl and Russell anyway because they are very popular? Marl is so popular because it's one of two free themes in the Store category. I recently launched Aether, and will be launching Batch shortly to replace Marl and Attar, which I plan to delist. |
Just raising awareness that they're popular so we should be careful, sounds like you already know and have a plan though, so it seems fine to go ahead with delisting 👍 |
Quick summary
The Byrne demo and front-end site, doesn't match what you see in the site-editor, which looks rather broken.
Steps to reproduce
A clear and concise description of what you expected to happen.
I expected the site editor view to look like the theme demo
What actually happened
The site editor view looked really narrow and broken. Visiting the site looked like the theme demo though.
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
If the above answer is "Yes...", outline the workaround.
Platform (Simple and/or Atomic)
No response
Logs or notes
No response
The text was updated successfully, but these errors were encountered: