Here's everything the site needs prior to launching. I did some QC today. This includes content and code. I was really hoping to have most of these things done before my wife went into labor, but it was a race against the clock and I lost.
I certainly think it's possible to launch the site before end-of-year, if prioritized, but it's also likely that I'll be finishing this work in early January.
Content Considerations
Alumni memberships/import
How will alumni be added? Do we have a database/listing of existing alumni? Yes, they'll be imported.
Will we add batches of alumni to the site when they 'graduate' the program, or offer a registration page where they can sign up on their own? Manually add batches for now
Forum
We are using bbPress for forums. We can either have 1 forum, or multiple. The original design allows for one, so I just want to confirm that's the desired behavior. A single central feed to which users can post topics. 1 forum
The original design is missing some pages we need, so those pages are currently using default styles:
"full view" of a single forum post
user edit view
We compromised here and added some styles to the forum that meet in the middle.
After merge we need to tag a release and deploy, or manually upload a .zip of the theme (we would have to temporarily enable upload permissions by editing the wp-config manually via ssh)
Remove duplicate files (CODE_OF_CONDUCT.md, CONTRIBUTING.md) from the repository to ensure alignment with organizational defaults as outlined in GitHub Repo Guidelines.
Also, update the readme file.
On home page, I'm seeing the default color for links ($color-forest-green) in different green versions. During hover, the color changes to a color that is not the $color-brighter-forest-green
Expectation
All green colors should be the same. While hover state should use the $color-brighter-forest-green one.
Page: Course
The attribution information in the featured image (right-aligned) should work as an editable component. All courses will have this section and, therefore, using different images.
Page: Home
The see all FAQs button, below the question list, uses an incorrect button style. The style should be normal (documented in the Design Library).
The certificates site is a WordPress Multisite installation, comprised of one main site and several sites in the form of books, powered by pressbooks. For this project the book sites should remain the same as much as possible, using the currently active theme, styles, and settings. The only changes made should be to update dependencies.
The following sections are notes on styling and functionality, scoped to the relevant page section.
The answer displayed in the accordion item looks too similar to the question. That's because of the styles of both texts. My suggestion is to apply a bold style for question text.
The arrow aligns on the right should be 20px size (1.25rem).
The same icon does not rotate when opening the question to see the answer. It should rotate in 180ΒΊ to indicate the box expanded.
Pressbooks mPDF is deprecated, so we cannot currently download books as PDFs. There are some options but they require addtional dependencies. One thing we could try doing is exporting .epub books inthe future, and then converting the epub files to PDFs, but we'll have to test the stying.
LTI functionality has been preserved. I'm not sure if it actually works or is being used!
The Candela Attributions and Candela Utilities plugins are kept, but I can't tell if they are being used or not. These plugins are deprecated and difficult to install with git+composer. If we can remove or ignore them, we should.
I tried to test several book pages but couldn't actually find any with attributions.
Breadcrumb NavXT is removed in favor of Yoast SEOs breadcrumbs. The breadcrumbs on this site are simple enough where we don't need a more complex implementation, and
Content questions
There was no archive page for courses mocked up. How do we want to handle that?
The Registration link(s) is a global setting on the options page but can also be overwritten per-course if necessary. Does this sound like good behavior?
General
Code was formatted with phpcbf --standard=WordPress . --ignore=vendor --extensions=php 0. If there's a better approach please let me know; I've always struggled to find good PHP linters and formatters where I was happy with the output.
Because this theme was unable to use Gutenberg blocks and, while relatively simple, has a lot of custom templates, I decided to use Advanced Custom Fields Pro to register metaboxes on page templates, as opposed to our usual combination of Queulat and widgets. I think this provides a really great experience for content editors, and reduces the amount of boilerplate code we have to write to register metaboxes with rich, complicated functionality. If there's a critical reason we do not want to go this direction, we can switch back to Queulat with some work. The templates wouldn't need to change much but we'd need to write all the Queulat code to register metaboxes.
Page: Home
The padding-top in second section, where FAQ section begins, should use the padding-top-bigger style instead of padding-top-big. This spacing will match the 64px of distance when adding the padding of above section.