WordPress Basics
This page covers the essentials for adding and editing content in WordPress. If you're new to the site or returning after time away, start here before diving into a specific content type.
Understanding Blocks
WordPress uses a block-based editor. Think of blocks as building blocks for your page—you stack them to build a layout.
Core Blocks
Standard WordPress blocks—paragraphs, headings, images, lists, etc.
Custom Blocks
Built specifically for this site. Always use these when available.
If there's a custom block available for what you need, always use it instead of the core block.
Best Practices
1
Save Frequently
- Click "Save Draft" every few minutes while working
- Don't wait until you're finished to save
2
Don't Apply Styling
- Don't change text colors, font sizes, or spacing in the editor
- Don't add custom alignment or inline styles
- All styling comes automatically from the theme—overriding it creates inconsistencies and technical debt
3
Use the Right Block for the Job
- Use heading blocks for headings—not bold text
- Use list blocks for lists—not dashes or asterisks typed manually
- Use custom blocks whenever one exists for what you need
4
Assign Program Terms Before Publishing
- Every custom post type must have at least one Program Term
- Untagged content won't appear in filters, program pages, or related content sections
- Use the most specific term that applies—see Using Program Terms for the full guide
5
Design Standards
Refer to Teal's Figma file for custom blocks and page layout guides. If you're not sure what a block looks like or how it behaves, check there first.
Quick Tips
- If you're unsure which block to use, check the Block Reference or ask the developer.
- Not all content types save revisions. If you have major changes, check with the developer to be sure you can save a revision before making major changes to published content.
- Don't publish until you've assigned a Program Term—it can't be automated after the fact.
- If something looks unexpected in the editor, it will likely look correct on the live site—the editor preview is not 1:1 with the theme.