getvie.com, read closely

A script at the top of index.html strips the fragment from the URL whenever the visitor did not arrive from getvie.com. So getvie.com/#plan sent by text, email, Instagram or a QR code opens the homepage instead of the plan. Clicking the same link inside the site works perfectly, which is why it survived a month without being spotted.

This is the one that costs money. Every link in a newsletter, every link in a post, every link you paste into a DM to a prospective subscriber points at a specific thing and delivers the front door instead. The visitor does not report it. They assume they tapped the wrong thing, or that the page is not there, and they leave.

Delete the script. It was written to stop the page opening below the fold, and it never did that, because the scroll came from settle() inside showHome() rather than from the fragment. Fixing the real cause lets the fragment stay, so deep links work again.

The card is position:absolute, but it lived in the left column of the hero while .hero was the only positioned ancestor above it. Every comment in the stylesheet assumes it anchors to .herostage, the photo column. It never did. Anchored to the whole hero, bottom:0 parks it across the pill row.

The pills are the only navigation on the homepage that names what Vie does. Covering them hides the five things a first visitor most needs to see, and it makes the page look broken rather than busy, which is a harder thing to come back from on a site whose whole argument is care.

Move the card inside .herostage so the positioning resolves against the element it was written for, and reserve enough room under the photo for it to hang without clipping the byline.

boot() finished by calling showHome(), and showHome() always called settle(), which glides to the top of the enclosing band. On a first load that scrolled past the headline, the photograph and the pills, and opened the site on the Wednesday section.

The hero carries the whole proposition: meal plans that save you money, the sentence about reading the sale prices, and the photograph that tells someone a real person cooks this. Skipping it means a first visitor starts in the middle of an argument whose opening they never saw.

Treat the first paint as what it is. There is nowhere to scroll back to before anyone has navigated, so settle only on a real navigation, and set scrollRestoration to manual so a reload starts at the top too.

The folder that gets dragged to Netlify contains package.json with a real dependency, a src/ directory, add_plausible.py, check-preview.py, two .bak files and three markdown handoffs. The functions are already bundled, so none of it is needed at deploy time.

Your own deploy notes already record this one: a package.json or a src/ directory in a drag and drop folder makes Netlify run an install it was not asked to run. It is deploying cleanly today, so this is a trap rather than a fire, but it is the kind that goes off during a launch rather than on a quiet Tuesday. The .bak files are also a second copy of the site sitting next to the site.

Move the sources and the handoffs up one level into vie/, the way your other builds already do it, and leave only what is served in the deploy folder.

A week's list is laid out as a fixed table. On a phone the columns keep their widths, so the quantity column slides under the thumb and the aisle column leaves the screen entirely.

The shopping list is the one screen that gets used standing up, in a store, one handed, on a phone. If any part of Vie has to be perfect on a small screen it is this one, and a layout that works everywhere except the aisle is a layout that fails at the only moment that counts.

Drop the table below 600px and stack each line as its own row: item first, quantity underneath in the lighter weight, aisle as a small tag. Keep the tick target at 44px so it can be hit while walking.

Submitting the email form clears the field and leaves the status line empty. Nothing confirms the address was taken, and nothing appears if it was not.

Silence after a form reads as failure. People submit again, or they assume it is broken and go. On the band that exists purely to collect addresses, a quiet success is indistinguishable from a dropped one, and you cannot tell the difference either when you look at the numbers afterwards.

Read the real response and say what actually happened. On success, name the next thing: the plan lands Wednesday. On failure, keep what they typed, say so plainly, and offer a mailto fallback so the address is not lost.

One of the links in the footer resolves to a path with nothing behind it and returns the 404.

A dead link in the footer is a small thing that does a specific kind of damage: it tells a visitor the site is not maintained. On a subscription product, where the whole ask is that someone trusts you to turn up every Wednesday, looking unmaintained is expensive.

Either build the page or remove the link today, and add a link check to the pre ship list so the next one is caught before it ships rather than after.

Two images carry alt text written for earlier photographs. The words describe a dish that is no longer in the frame.

Wrong alt text is worse than none. A screen reader announces a confident description of something that is not on the page, and a search engine indexes the same mistake. It also undoes the thing these photographs are for, which is proving that you cooked and shot every one.

Rewrite both against what is actually in the frame, in the same register as the rest: what the dish is, what it is on, what is around it. Then make alt text part of the image swap, so it moves when the photo moves.

The feather card headings sit inside link and button wrappers and never set their own color. They inherit the browser default, which is near black, and the cards go dark when the system is in dark mode.

Dark text on a dark card is not hard to read, it is invisible. The card looks empty, so the page looks broken, and the person it happens to has no way to tell you what they saw beyond saying it did not work.

Set an explicit palette color on every heading rather than letting it inherit. This is already written down as a house rule, so it is a compliance fix rather than a new decision.

The description tag repeats the brand line rather than saying what the page gives someone. Search results show it verbatim.

The description is the only sentence you get to write in a search result. A tagline asks the reader to work out whether this is for them. A plain answer tells them, and the click rate follows the difference.

Write it as the answer to the question that brought them: a weekly meal plan built from your own store's sale prices, with the shopping list done. Keep it under 155 characters so it is not cut, and make it different from the title rather than a restatement of it.

There is no FAQ block, no question shaped heading and no short self contained answer anywhere on the page.

A growing share of the people who would like Vie will never see a list of blue links. They will ask an assistant how to plan meals around what is on sale, and it will answer out of pages that have a question as a heading and a complete answer in the next forty words. Pages written only as marketing prose do not get quoted, because there is nothing liftable in them.

Add five real questions with real answers, each answer complete on its own without the paragraph above it. How does Vie know what is on sale. Which stores. What if my store is not covered. Do I have to cook all five. What does it cost. Mark them up as FAQPage so the structure is machine readable, and keep the answers honest about current limits.

The recipe pages carry no Recipe markup: no ingredients, no times, no yield, no ratings in a form a search engine reads.

Recipe markup is the single largest lever this archive has, and it is the one piece of SEO where the format is fixed and the payoff is visible. Without it the recipes compete as plain pages against sites whose entries show a photo, a time and a star rating in the results. The archive is the moat and it is currently invisible.

Generate the markup from the parsed recipe data rather than writing it by hand. The fields are already in recipes.json: ingredients, instructions, times, yield. Emit it per recipe at build time, and skip any recipe missing a time rather than guessing one.

One of the rotating lines uses it's where its belongs.

On a page selling care and craft, a misplaced apostrophe is read as a signal about everything else. It is a small thing that gets noticed by exactly the sort of reader who would otherwise be impressed.

Fix the line, then add the pair to the spelling check that already runs in the suite, alongside the British spellings it is catching now.

Several images are served at their full dimensions and scaled down by the browser, rather than being resized and served in a modern format.

These photographs are the proof that a real person cooks this, so they have to stay beautiful. But on a phone on a weak connection the hero can be most of what loads first, and a hero that arrives late undoes the impression it was there to make.

Serve each one at the size it is actually displayed, in AVIF with a JPEG fallback, and keep the explicit width and height so nothing jumps while it loads. The hero keeps fetchpriority high. The rest stay lazy.