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

[Tracking Issue] Block Based Themes Training #175

Open
7 tasks
fabiankaegy opened this issue Jan 8, 2025 · 3 comments
Open
7 tasks

[Tracking Issue] Block Based Themes Training #175

fabiankaegy opened this issue Jan 8, 2025 · 3 comments

Comments

@fabiankaegy
Copy link
Member

This tracking issue is for defining the overall stricture of the Block Based Theme training section of the site.

The training itself happens using the https://github.com/10up/block-based-theme-training repository.

In terms of setup the plan is to have two CPT's with some meta fields etc. One of them already has all the templates properly configured & built and the other one is bare bones with only the CPT itself built out. Tasks then are creating the various templates etc.

Proposed Structure:

  • Lesson 1: Anatomy of a block based theme
  • Lesson 2: Creating a new single template for a CPT
  • Lesson 3: Displaying meta fields in the custom template
  • Lesson 4: Making sure the meta fields are editable in the admin
  • Lesson 5: Creating a new archive template for the CPT
  • Lesson 6: Extending the Query Loop
  • Lesson 7: Working with patterns (inserter false, the wp:pattern block, etc.)
@fabiankaegy
Copy link
Member Author

@colinswinney
Copy link
Contributor

colinswinney commented Jan 14, 2025

@fabiankaegy Can you clarify a little on how you envision lessons 3 & 4? Are you thinking of using meta fields via block bindings or as small atomic blocks (or both?). Or is there a third way I'm not thinking of?

@fabiankaegy
Copy link
Member Author

@colinswinney I think we'll have to showcase both and add a bit more context about when to choose what.

Block bindings are great when the field is never conditional. But more often than not I end up needing atomic custom blocks because as of right now block bindings also aren't editable when they are used inside a template. Which is not the case for atomic blocks. They can be editable in the template

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

No branches or pull requests

2 participants