CSS Pro Needed: Match Custom HTML Article to Spectra Pro Layout (WordPress)

CSS Pro Needed: Match Custom HTML Article to Spectra Pro Layout (WordPress)

CSS Pro Needed: Match Custom HTML Article to Spectra Pro Layout (WordPress)

Upwork

Upwork

Remoto

4 hours ago

No application

About

Budget: Fixed price — $50 Scope: 1 article (CSS-only in Appearance → Customize → Additional CSS; very limited HTML class additions allowed within the article markup) Stack: WordPress (Astra/Spectra Pro), Gutenberg Custom HTML block The Job I have a new article built mostly inside a Custom HTML block. I need a CSS specialist to style it—primarily via Additional CSS—so it matches an older reference article built with Spectra Pro blocks or looks even more professional/better. No theme/plugin edits. No global style overrides. Minimal HTML tweaks allowed: you may add lightweight class attributes to elements within this article only to help scope styles. Every HTML change must be documented (selector and/or class, purpose, before/after snippet). What You’ll Deliver Pixel-accurate (or better) visual match to the reference Spectra Pro article Typography, spacing, buttons, lists, cards, blockquotes, tables, images, CTAs aligned with the reference or better. Tasteful hover/interaction states on cards and buttons (e.g., subtle elevation, outline/underlay, shadow/transform, focus-visible styles)—only if it improves UX and stays on-brand. Spectra-like utilities re-created in CSS where needed (gaps, grids, columns, etc.) Responsive polish across existing breakpoints. Cross-browser check (Chrome, Firefox, Safari) Clean, well-organized CSS with comments (sectioned by component). No layout shifts/CLS; minimal specificity; and no !important bombs unless absolutely crucial. Change log (Markdown or Google Doc) listing: Any HTML classes you added (e.g., .article--custom, .hero__title) and where. The scoped wrapper used (e.g., an ID or top-level class). What was matched vs. what was improved. Quick before/after screenshots (desktop + mobile) of key sections. Must-Haves Expert-level CSS (Grid/Flex, fluid type, preferably with clamp(), modern responsive patterns). Strong understanding of Gutenberg markup and Spectra semantics. Ability to scope styles to one article (wrapper-first approach, BEM naming). Accessibility-aware choices (contrast, focus states, readable line length). Performance-minded (lean selectors, small CSS payload). Nice-to-Haves Familiarity with Astra + Spectra Pro Experience matching designs when original block styles aren’t present. How We’ll Work I’ll provide: URL of the reference Spectra articles. URL of the new Custom HTML article You’ll provide: A short scoping plan (e.g., #post-123 .article--custom...) Final CSS in Additional CSS. Start your first sentence with 'BubbaOrange' so I know you read this. Documented list of any HTML class attributes added (with line/section references). Notes on what you matched vs. improved. To Apply (read carefully) Share 2 live URLs where you improved layout via CSS (note if you added minimal classes). In one sentence, explain how you prevent style bleed when targeting a single page. Bonus: in a phrase, when do you reach for clamp()?