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

Converting the Style Guide to the Theme's theme.json file #969

Closed
Tracked by #821
jonathanbossenger opened this issue Sep 26, 2022 · 0 comments
Closed
Tracked by #821

Converting the Style Guide to the Theme's theme.json file #969

jonathanbossenger opened this issue Sep 26, 2022 · 0 comments
Assignees

Comments

@jonathanbossenger
Copy link
Collaborator

jonathanbossenger commented Sep 26, 2022

IMPORTANT

This lesson belongs to part of a greater course, Extend a Low Code Block Theme which depends on the completion of Create a Custom Block Theme #1

Please reach out to @jonathanbossenger (Jonathan Bossenger) in the #training team Slack if you would like to help with this lesson.

Topic Description

The goal of this lesson is to understand the basics of taking a theme design Style Guide, adding the settings to theme.json, and applying those settings through the Global Styles interface.

Objectives

After completing this lesson, participants will be able to:

  • Create a new setting in theme.json
  • Apply the setting in the Global Styles interface
  • Apply the setting in the theme.json file

Participants will also be given a base "theme.json" with most of the theme settings and styles already included, in order to help speed up the "build" process, and as an example of what the final file should look like.

Guidelines

Review the [team guidelines] (https://make.wordpress.org/training/handbook/guidelines/)

Lesson for Review

Please note that this content is being migrated over to Learn WordPress, and during that process, updates and corrections are being implemented on the lesson content. If you don't have access to Learn WordPress, you can review using the source markdown file, but that information might be out of date.

Review checklist

Reviewers: this is not an extensive list, but it would be helpful if you can keep the following questions in mind while reviewing.

  1. Are there any spelling/grammar issues or anything that doesn't make sense?
  2. Is the content technically correct?
  3. Does the layering of information successfully build from lesson to lesson
  4. Can you follow the steps outlined in the course
  5. Does the lesson contain enough relevant links to documentation (WordPress documentation, or any other relevant documentation)
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

No branches or pull requests

1 participant