The gap between listing items was collapsing to 11-33px and varying per
item, despite a 50px margin. The thumbnail floats left and nothing
contained it, so whenever the excerpt was shorter than the 150px image
-- which is most of them now the column is the full 930px rather than
the theme's 650px -- the image overflowed the item and the margin below
it was absorbed.
.post/.hentry now use display: flow-root, so the item wraps its own
float and the margin is measured below the image. Measured against the
live old site: it has no overflow (-6px) and a steady 42px gap; this was
overflowing by 39-61px. Both sites now sit at a consistent 60px.
That also makes the theme's trailing <br /> and clear div redundant --
they existed only to escape the float -- so the listing markup drops
them and the wrapping Fragment with them.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
.post/.hentry margin-bottom goes from the theme's 20px to 50px, giving
about 72px between items once the heading margins and the clearing
<br /> are counted.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three things were off in the front-page and blog listings.
The floated thumbnail was never cleared, so the next item's heading
wrapped around it instead of starting below -- front-page.php emits
<br /><div class="clear"> </div> after each post, which is now
reproduced.
The post wrapper was missing the classes WordPress adds via
post_class(); .post/.hentry carry the margin-bottom: 20px that separates
items.
And the listings sat in the theme's #content, which is float: left and
650px because it expects a 230px sidebar alongside. There is no sidebar
here -- the search and widget boxes were WordPress-specific chrome and
were dropped -- so that just left dead space to the right. BaseLayout
already wraps the slot in the full-width #content-full, so the inner
wrapper is removed and the sections span the full 930px.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The theme styled the nav, all headings and the comments watermark with
'Coda', cursive, sans-serif, pulling Coda from Google Fonts. That font
load was never ported, so browsers moved to the next entry in the stack
-- the generic cursive family -- and rendered those elements as a script
face on any device that ships one, which phones do. It went unnoticed
because this server's Chromium has no cursive font installed and so fell
through to sans-serif.
Those three rules now use Arial, Helvetica, sans-serif, matching the body
text, rather than depending on a webfont that is no longer loaded.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Same approach as the vicidial.com migration: 58 pages, 6 posts, 41
attachments and the 4-item nav exported from wordpress_vicihost via
scripts/export-wp.mjs, with the layout and styling ported from this
site's own copy of the small-business theme.
That theme copy is not identical to vicidial's -- it carries the red
VICIhost palette, its own meta description, and shows 6 slides rather
than 5 (smallbusiness_ppp) -- so the CSS and slideshow are ported from
it rather than shared with the other site.
The export script gained handling for custom-link menu items, which this
menu uses for its "Home" entry and vicidial's did not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jamespandClaude Opus 5