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

Term archive wc porto #183

Open
wants to merge 6 commits into
base: trunk
Choose a base branch
from
Open

Term archive wc porto #183

wants to merge 6 commits into from

Conversation

liviopv
Copy link
Collaborator

@liviopv liviopv commented May 17, 2024

Includes:

  • Clean up of the single and page templates from TT1 Blocks
  • Theme.json updates to TT1 blocks
  • Create Archive Template to Archivist
Fixes "This block contains unexpected or invalid content." in the Content and Comment sections
Update theme.json
Fixes "This block contains unexpected or invalid content."
Initial pass on the archive template block structure.

There are some inline styles that need to be cleaned up, and there more fine adjustments that need to be made in the border setup.
Copy link

github-actions bot commented May 17, 2024

Preview changes

I've detected changes to the following themes in this PR: TT1 Blocks, Term.

You can preview these changes by following the links below:

I will update this comment with the latest preview links as you push more changes to this PR.

⚠️ Note: The preview sites are created using WordPress Playground. You can add content, edit settings, and test the themes as you would on a real site, but please note that changes are not saved between sessions.

General block structure. It needs a fix for the bottom left, and some cleanup
@MaggieCabrera MaggieCabrera linked an issue Jun 5, 2024 that may be closed by this pull request
Comment on lines 3 to -4
<!-- wp:group {"tagName":"main"} -->
<main class="wp-block-group">
Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's separate the changes into different PRs so they can be reviewed individually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment