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

TT1-Blocks update #307

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

TT1-Blocks update #307

wants to merge 12 commits into from

Conversation

carolinan
Copy link
Collaborator

  • Moved templates and parts to the new folders
  • Moved patterns to the new patterns folder
  • Updated theme.json to version 2
  • Removed some CSS that is no longer needed.
  • Removed theme_support that is no longer needed, since it is added automatically.

Move templates and parts to the correct folder
Update theme.json version
@carolinan carolinan changed the title Theme update TT1-Blocks update Jul 6, 2022
@MaggieCabrera
Copy link
Collaborator

I think this one closes #193

@carolinan
Copy link
Collaborator Author

I think this one closes #193

Tested, confirmed (chrome, windows 10)

@carolinan carolinan marked this pull request as ready for review July 6, 2022 10:53
@@ -160,42 +156,15 @@
# Separator
--------------------------------------------------------------*/

hr,
.wp-block-separator {
.wp-block-separator :not(.has-text-color) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The old CSS prevented the color options from working.

@MaggieCabrera
Copy link
Collaborator

Closes #260 too then

tt1-blocks/style.css Outdated Show resolved Hide resolved
* Slug: tt1-blocks/large-text
* Categories: tt1-blocks
* Block Types: core/heading
* ViewportWidth: 1440
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be Viewport width not ViewportWidth?

But I wonder if this pattern should be removed, does it bring any value?

Copy link
Collaborator Author

@carolinan carolinan Jul 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Secondly if the patterns that don't use custom CSS were moved to the pattern directory, the theme would not need to include them...)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's Viewport width

And about the pattern directory, yes, that would be the case. I've never included a pattern from the directory on a theme yet, don't know if they work fine or if it still needs more work.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if it is a true bug or, if there is a limit to how many patterns are loaded from the directory, or something; but it does not work as I expected, if Gutenberg is active:
WordPress/gutenberg#41959

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mmh, I guess we could raise this in core-editor chat? I don't know who works on this. Maybe we could follow up on a future PR.

tt1-blocks/style.css Outdated Show resolved Hide resolved
tt1-blocks/readme.txt Outdated Show resolved Hide resolved
@MaggieCabrera
Copy link
Collaborator

Looks like we lost the separator style on index? I don't know if this is still a WIP, let me know for a full review

Screenshot 2022-07-06 at 14 46 30

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 this pull request may close these issues.

2 participants