Skip to content

Home

Jump to bottom
Rob Knight edited this page Mar 17, 2022 · 47 revisions

Meeting notes are below. Goals & milestones are here.

2022-03-17

  • Individual story sharing to social: use a plugin that modifies the core social links block. We'll table this for now and come back to it.
  • Breadcrumbs: using another plugin, Hybrid Breadcrumbs. Test to see if it will work with Truss.
  • Questions for the coming week:
    • Should we cement multi-column layouts into the theme on listing pages like news front?
    • Article layout and typography: line-length, image size (need docs for this)
    • Site building and example for web users

2022-03-08

  • Reusable blocks are freaking crazy. They can be exported and imported (as json). Can we include them in the theme?
    • Great for footers and headers and other repeated content.

2022-03-02

  • Rob: PR for setting site title and page titles
  • .alignfull class is shifted too far left

2022-02-25

  • Further reduce the redundant template parts files since they aren't necessary for content areas
  • CampusPress has our account info for the theme and plugins repo
  • CampusPress is still on WP 5.8.3. We need them to upgrade to 5.9 to support our theme.
  • Initial performance test on CP network is disappointing. We're going to need a huge improvement or news and the homepage will have to live elsewhere.

2022-02-16

  • Name the two stylesheets properly for their contexts (we were able to use just one sheet for both)
  • Test the 'one sass partial per core block' setup (this should work just fine)

2022-02-14

  • We made sure the editor enqueues the same sass partials as the front end.
  • We will go forward assuming that we will have an individual sass partial file for each core block only when we need to change it.
  • We learned that theme.json has the final say in the style cascade, in both the front and the back end of the site.

2022-02-11

  • Home page templates wrap the site title in an <h1> tag. All other page templates wrap the site title in a <p> tag.
    • Why? Because the home page typically doesn't have a discrete h1. All other pages do. Also, you are on the home page, so the site title is a logical h1 when no other h1 is on the page.
    • In WCMS, we have the same problem. We opted for site titles always being in <p> tags. That means only home pages don't have a proper h1 tag, and all sub pages do.

2022-02-07

Notes

  • We've entered a re-factoring stage. Important to clean up in prep for the next phase.
  • Focus on sass files, templates, and linting sass, PHP, and HTML files.

2022-02-04

Notes

  • Release betas with standard-version: standard-version --release-as 1.0.0-beta.V where 'V' is the beta number.
  • Refactored the header files to pull out the campus page top region into a separate template part.
  • Jason found an official way™ 😆 for modifying block output in PHP before it is rendered.

Tasks

  • The other header template parts can also be refactored to remove redundant parts
  • Need a build script to create the installable theme folder

2022-02-02

  • Jason organizing and abstracting templates and parts according to the latest block theme standards:
    • Abstract parts out and create sub-templates only when need is obvious (logo display differences between campus home and subsites)
    • Name template abstractions for widest use case
      • ✅ header-subsite.html rather than
      • 🛑 header-department.html
  • First release on 2022-02-04
  • Theme release process:
    • standard-version locally to bump version and create/update the CHANGELOG
    • Create a zipped folder of the built theme files for WordPress users to download
    • Push to Github and include tags
    • Create a pre-release (title is the tag) and attach working build
    • Save the release (Slack will be notified 🎉)

2022-01-31

  • Pull content creation functions from theme
    • Include a wordpress.xml file along with the theme that creates a couple of pages, posts, and menus, and puts them in the correct spots in the theme.
    • Treat this as a first-run experience for new theme users who may or may not be in CampusPress.

2022-01-28

  • Automatic page "About this theme" (We're changing this)
  • Shove footer to bottom
  • Remove title from home page template
  • Gap in some flexed objects (menus in global header)
  • Walk through the front versus back end CSS.

2022-01-26

  • Deployment strategy
  • Patterns workflow: how do we create/customize patterns for the block editor interface
  • Sample content (in a WordPress.xml file)
  • Individual block theming workflow
    • Add a folder for blocks
    • One CSS/SCSS file for each block
    • Enqueue block styles in functions.php once for each block, so WP knows which custom styles to load on a page.
  • Capturing feedback from team and from users (web form -> GH issues AND structured issue creation)

2022-01-21

  • Development workflow added to README:
    1. Have Docker running and wp-env installed.
    2. In your themes subfolder, gh repo clone ucsc/theme-ucsc ucsc
    3. In the ucsc folder, npm install && npm run build to compile theme file
    4. cd to root folder and run wp-env start
    5. Login (admin:password) and navigate to http://localhost:8888/wp-admin/import.php

2022-01-18

  • Whether or not to have specific home page template? Not yet, but can do if it seems necessary
Clone this wiki locally