The website is a simple "brochure" site — six pages of information about the store, with no
logins, no shopping cart, and no database. It is built once into plain web files and served from
Replit's hosting. Because it's so simple, there is very little that can break on its own.
The pages: Home, Donating to LCM, plus the other four interior pages listed in
the top navigation.
2The one golden rule
Changes are never live until you Republish.
You (or anyone helping you) can edit and preview all day — visitors keep seeing the old version
until you press Publish/Republish in Replit. This is a safety feature: nothing
goes live by accident.
3Routine tasks
Making a text or photo change
Open the project in Replit and describe the change to the Agent in plain English
(e.g. "Change the store hours on the home page to 9–4").
Look at the preview pane to confirm it looks right.
Press Republish.
Open lastchancemercantile.org in a private/incognito browser window to confirm the live site
updated.
If the live site looks broken but the preview looks fine, the safest move is usually to
roll back to a previous checkpoint in Replit and republish (see section 10).
Sharing links (texts, Facebook, etc.)
When you share a page link, phones and Facebook show a preview card with the page's title
and a photo of the storefront with the logo.
Previews are cached. If you fix something and the old card still appears,
it can take hours to refresh on its own. Trick: add ?v=2 (or any new number) to the
end of the link to force a fresh card, e.g.
https://lastchancemercantile.org/donating-to-lcm?v=2
4How to ask the Agent for a change
The Agent does the work; your job is to be specific about what you want. Most problems come
from a request that left something to guess.
A good request has three parts: where, what, and the exact words.
"On the Find Us page, change the Business Hours to Tuesday–Saturday, 9:00 AM to 4:00 PM.
Update the hours anywhere else they appear on the site too. Don't change anything else."
"Update the hours."
Habits worth keeping:
Give the exact wording you want. If you write it out, you get it. If you
describe it, you get the Agent's version of it.
Name the page. "On the About page…" saves a round trip.
Say "don't change anything else." It keeps a small edit small.
One change at a time. Five changes in one message makes it much harder to
tell which one broke something.
Ask it to check the rest of the site, in these words: "Check whether
this information appears anywhere else on the site and update it there too." See section 5
for why this matters.
Ask for confirmation before you republish:"Run the site's built-in
checks and tell me they pass." The project has automatic tests for missing photos and
broken pages, and this is how you make it run them.
If the Agent proposes something bigger than you asked for, say no and ask
why it thinks it's needed. Small edits should stay small.
5Information that lives in more than one place
Some details are stored once and appear everywhere. Others are typed out on several pages, and
changing one place is not enough.
Detail
Where it lives
What to say
Phone, address, map links
Stored once; used everywhere
"Change the phone number to …"
Menu names and order
Stored once
"Rename the 'Find Us' menu item to …"
Copyright year in the footer
Updates itself
Nothing — leave it alone
Store hours
Typed on three pages — Home, Find Us, Donating to LCM — and in the
hidden description Google shows
"Change the hours to … everywhere they appear"
Store hours are the one to be careful with. They appear as shopping hours and
donation-gate hours, which are different times, in several spots. After an hours change,
personally check the Home page, the Find Us page, and the Donating to LCM page before you
republish.
6Adding a new section to a page
A "section" is one horizontal band of a page — a heading, some text, maybe a photo or a button.
The site already has a set of standard looks, so ask for one of these rather than describing a
design from scratch:
a plain white band
a light grey band
a dark slate band with white text (used for the "Support LCM" call to
action — good for making something stand out)
two things side by side — text on one side, a photo on the other (stacks
automatically on a phone)
a row of photo cards, two or three across
Tell the Agent all five of these things:
Which page, and where on it — "at the bottom of the About
page, just above the footer"
Which look from the list above
The heading, exactly as you want it
The words, exactly as you want them
A photo and a button, if you want them — including where the button should
go
"On the Jobs Program page, add a new section at the bottom, above the existing 'Support LCM'
band. Use the light grey background. Heading: 'How to Apply'. Text: 'Ask any staff member at the
donation gate, or call us at (831) 264-6900.' Add a button that says 'Find Us' linking to the
Find Us page."
Then check the preview on both a wide window and a narrow one before you republish.
7Adding a whole new page
This is a bigger job than a section, but it's still one request. A new page has to be wired
into five different places to work properly, and the Agent handles all of them — you just need to
check the result.
Tell the Agent:
The page name as it should appear in the top menu — e.g. "Volunteer"
Where in the menu it should sit — e.g. "between Find Us and About"
The web address you want — e.g. /volunteer (keep it short, all
lowercase, dashes instead of spaces)
The heading and the words for the page
A one-sentence description for Google — this is the grey text under the
link in search results. Roughly 25 words.
Then ask, in these words: "Add it to the menu, the sitemap, and the page descriptions, and
run the site's built-in checks."
After it's done, check all five of these before republishing:
Then republish and open the new address directly in a private window — typing
lastchancemercantile.org/volunteer into the address bar, not clicking through from
the menu. That's the case most likely to be broken, and the one visitors will hit from Google.
8Things to leave alone
These are set up correctly and quietly cause trouble if changed.
The web addresses of existing pages. Changing /donating-to-lcm
to something else breaks every link ever shared and every Google result. If a page truly needs
renaming, say so explicitly and ask the Agent to redirect the old address to the new one.
The domain and DNS settings. They're done. See section 9.
Photo files that are already on the live site — renaming them breaks
anywhere the photo was used. Adding new photos is fine.
The styling system. If the Agent ever offers to "add Tailwind" or
"modernise the styling," say no. The site's styling is hand-written and a
change like that would collide with it and break the layout in ways that are tedious to
undo.
The www vs non-www setup, and the site's address
structure. Both work today; leave them be.
9Things already set up (don't redo these)
Domain: Both lastchancemercantile.org and www.
are connected and secure (the padlock). DNS lives in GoDaddy; the hosting lives
in Replit. Renew the domain in GoDaddy each year.
Page titles & preview images: Each page has its own title and
description baked in for search engines and link previews. These update automatically when the
site is rebuilt — no maintenance needed.
Back-to-top button and mobile navigation — built in.
Automatic checks: the project tests itself for missing photos, broken page
links, and pages that were only half-added. Ask the Agent to run them whenever you've changed
more than a few words.
10When something goes wrong
Don't panic — the site can always be restored. Replit saves a checkpoint
after every change. Rolling back to a checkpoint that worked, then republishing, undoes almost
any problem.
Describe the problem specifically: which page, what you expected, what you
saw, and on what device (phone/computer). A screenshot helps enormously.
Verify fixes on the live site, not just the preview. Hosting behaves
slightly differently than preview — a lesson learned the hard way. Ask whoever helps you to
confirm the fix at the real lastchancemercantile.org address, page by page.
A few specific symptoms
What you see
What it usually is
A photo shows as a broken icon
The photo file is missing or was renamed. Ask the Agent to run the built-in checks — it
names the missing file.
A page shows "404 / Page not found" on the live site but works in preview
A new page wasn't fully wired in. Ask the Agent to check that page is in the sitemap and
page descriptions, then republish.
The live site still shows the old version
Either you haven't republished, or your browser cached it. Check in a private window
before assuming anything is wrong.
A shared link shows the wrong preview card
Caching. Use the ?v=2 trick in section 3.
The preview pane shows a big red error box
The last change broke something. Ask the Agent to undo it, or roll back to the last
checkpoint.
11Where to get help
Problem
Who to ask
Content changes, broken pages, design tweaks
Replit Agent (in the project) — describe it in plain English
Billing, account, or publishing questions on Replit
The replit.md file in the project has technical notes
12The safety-deposit box (backups)
The export zip file is a complete, standalone copy of the site's code. Any
web developer can rebuild and host the site from it, anywhere — it does not depend on Replit.
Keep the latest version saved somewhere safe (email it to yourself, or keep it in cloud
storage).
Photo masters: keep your original full-resolution photos archived
separately — the site only contains web-sized copies.
After any big round of changes, ask for a fresh export zip and replace the old one.
For a developer picking this up cold
Unzip, then in the folder run:
npm install
npm run build
The finished site appears in dist/public/ — plain files, hostable on any static
web host. See README.md for details.
13The checklist for every change
Tape this to the wall.
Ask — name the page, give the exact words, add "don't change anything
else."
Ask it to check the rest of the site for the same information.
Look at the preview — wide window and narrow window.
Ask the Agent to run the built-in checks and confirm they passed.
Republish.
Open the live site in a private window and confirm it — the real address,
not the preview.
If step 6 looks wrong: roll back to the last good checkpoint, republish, and start again.
Nothing is ever lost.