[Evaluation] Filipe Coutinho - #30
Open
coutinhocouto wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two-part WordPress challenge submission, one commit per challenge so they can be reviewed independently.
Challenge 1 — AirPnP front page. Server-rendered Gutenberg block (airpnp/listing-cards) backed by a transient-cached WP_Query (cache busts on post lifecycle events). Responsive Tailwind layout, front-page-only asset enqueue, SEO meta tags, accessibility (skip link, ARIA, keyboard nav, reduced-motion), i18n-ready. Docker entrypoint imports a committed seed SQL on first boot so the site comes up fully populated.
Challenge 2 — Pug & Puggle backend. 6 CPTs, 3 taxonomies (one shared across CPTs), 9 Gutenberg blocks, a transient-backed cached query layer, ACF field groups defined in PHP, and a JSON-LD schema layer (Person, LegalService, Review, LocalBusiness, FAQPage, BreadcrumbList). One-click demo-content seeder via admin notice. Docker images pinned.
Both READMEs have the full run-through and design rationale.