Cedar Lake Park Association

Website Guide

Welcome to your new website! It’s built on Webflow, a platform that lets you update text, photos, documents, and lists yourself—no code required. This guide walks you through everything you’ll need for day-to-day content. You won’t break anything by reading and clicking around, so feel free to explore.

Two audiences: Most of this guide is for you, the content editor. A few sections are marked [For your web partner]—those cover behind-the-scenes setup you can leave to whoever maintains the design.

1. The two ways to work on the site

Webflow gives you two ways in. For everyday updates you’ll use the first one—a simplified content view that keeps the design safely locked.

A 2026 change worth knowing: Webflow is retiring its old “Editor” (the on-page bar you used to open by adding ?edit to the web address). Content editing now happens inside Webflow itself, in a simplified view tied to your Content editor seat. If you see older tutorials that mention the “Editor,” this is its replacement.

Content editing (use this)

Designer (leave this alone)

What it’s for

Changing words, photos, documents, and CMS content

Layout, colors, structure, new page types

Who uses it

You

Your web partner

How to open

Sign in at webflow.com and open the site—your Content editor seat opens a simplified view with the design locked

Opening the site in full Design mode

In the content view you get four panels—Pages, CMS, Assets, and Settings. Click directly on text or an image to change it, or open the CMS panel to edit your content lists. It’s safe—you can edit content and publish, but you can’t change the design.

2. How the site is organized

Main pages (fixed content)

  • Home (/)
  • Why—why the park matters (/why)
  • Who We Are—about the Association (/who-we-are)
  • Places—the eleven landscapes of the park (/places)
  • Experiences—ways to enjoy the park (/experiences)
  • Things to Notice—details to look for (/things-to-notice)
  • Stewardship—the ongoing care work (/stewardship)
  • History & Archives—the park’s story, with newsletters, photos & documents (/history)

Most of these pages pull their content from Collections (your content lists), which is what the next section is about.

3. What the CMS is

The CMS (Content Management System) is a set of Collections—think of each one as a spreadsheet. Every row is an item (one place, one photo, one document), and the columns are fields (its name, image, description, and so on).

The big advantage: you edit an item once, and it updates everywhere it appears—the listing page, its own detail page, and any card that links to it.

Your collections and where they show up

Collection

What it holds

Where it appears

Places

The 11 landscapes of the park

The Places page + each Place’s own page

Experiences

Ways to enjoy the park

The Experiences page (and home-page cards)

Things to Notice

Details to spot at each place

The Things to Notice page; also on Place pages

Timeline Events

Dated moments in the park’s history

The historical timeline

Newsletters

Past newsletter PDFs

The Newsletters page

Historic Photos

Archival photographs

The Historic Photos gallery

Documents

Plans, reports, key records

The Documents page

4. Editing content, step by step

To change an existing item

  1. Sign in at webflow.com and open the site. With your Content editor seat you land in the simplified content view.
  2. Go to the page where the item appears (e.g. a Place), or open it from the CMS panel.
  3. Click the text or image you want to change—an editing panel opens.
  4. Change any field. Each field has a short note under it explaining what it’s for—read those if you’re unsure.
  5. Save your changes, then Publish when you’re ready for them to go live (see Section 7).

To add a new item

  1. Open the CMS panel and choose the relevant collection (e.g. Newsletters).
  2. Click New (the “+”) to create an item.
  3. Fill in the fields. Name is required; the Slug fills in automatically.
  4. Set its Display Order so it lands in the right spot (see Section 5).
  5. Save, then Publish.

To remove an item

You can Archive (hide it but keep it) or Delete (remove permanently). Archiving is the safer choice if you might want it back. Deleting an item also removes its detail page—don’t delete something other pages link to unless you mean to.

5. Controlling the order items appear in

Every collection has a Display Order field (a number). Items are sorted lowest number first. To move an item, change its number.

Tip: leave gaps—number things 10, 20, 30 instead of 1, 2, 3. That way you can slip a new item in at “15” without renumbering everything.

  • Places and Experiences also have a Numeral field (i., ii., iii. …) shown on the card. Keep the numeral matching the Display Order so the labels read in sequence.
  • Timeline Events sort by Display Order, set to follow the Year.

6. A closer look at your collections

Almost everything on the site is CMS content—you edit an item once and it updates everywhere it appears: the listing page, its own detail page, and any card that links to it. Every field also has built-in help text in the CMS panel, so the maps below are just the big picture.

How your collections connect

Three collections are linked through reference fields (one item pointing at another). The rest stand alone.

Places11 landscapes — the hub
Experiences
Things to Notice
Newsletters · Historic Photos · Documents · Timeline Events

Standalone — no links to other collections.

Field by field

Places

Field

What it does & where it appears

Name

The place’s full name. Page title, card heading, and nav label.

Short Name

Abbreviated name for cards, nav, and map labels.

Numeral

Roman numeral (i., ii., iii.) shown on the place card.

Category

Landscape type (Beach, Woodland, Prairie, Wetland, Trail). Used for filtering and labels.

Display Order

Manual sort order; lower numbers first.

Hero Image

Large image at the top of the place page.

Hero Caption

Caption on the hero (e.g. “Skating on Cedar”).

Hero Sub Caption

Smaller caption under the main one (e.g. a date).

Hero Extra Info

Location / context line on the hero (e.g. “South Point Beach”).

Tagline

Subhead shown under the place name on the page.

Short Description

One-line tagline used in cards and meta descriptions.

Body

Main descriptive content for the place page.

Place Intro

Short intro above the checklist on the Things to Notice card.

Map Slug

Matches this place to its marker on the home-page map.

Map X / Map Y

Marker position (percent) on the home-page watercolor map.

Related Places ref

Other Places suggested in the sidebar (pick 2–4).

Related Experiences ref

Experiences you can do at this place.

Things to Notice ref

Notices to surface on this Place’s page.

Slug

URL-friendly ID; avoid changing after launch.

Experiences

Field

What it does & where it appears

Name

The experience’s name (e.g. “Walking & Hiking”). Section heading and home-page card title.

Numeral

Card numeral (i., ii., or 1.). Leave blank to hide.

Display Order

Manual sort order; lower numbers first.

Anchor

Hash slug used by the sidebar contents links (e.g. #walking-hiking).

Card Image

Thumbnail shown on the home-page card.

Card Icon

Small icon on the home-page card.

Card Description

One-line description on the home-page card.

Hero Image

Lead image for this experience’s own page and the Experiences listing.

Hero Caption

Optional caption under the hero image.

Body

Rich-text main content for this experience’s own page. Supports headings, bold, and links.

Related Places ref

Places where this experience is appropriate.

Slug

URL / anchor ID; avoid changing after launch.

Things to Notice

Field

What it does & where it appears

Name

The notice title (e.g. “Great Horned Owl”). Heading on the card.

Category

Theme (Wildlife, Plants & Trees, Land & Water, Stewardship, History & Memory, Paths & Gathering). Card tag and filter.

Place ref

The Place this notice lives at (required). Surfaces it on that Place’s page.

Display Order

Sort within a place; lower numbers first.

Homepage Feature

Toggle on to include in the random home-page “Things to Notice” teaser.

Image

Optional feature photo.

Detail

Optional detail paragraph(s); title-only notices leave it empty.

Slug

URL ID; avoid changing after launch.

The archive collections

These four stand alone—no references in or out. Each is a straightforward list of items.

Newsletters — Name, Year, Volume Issue, Edition Name, Lead Article, Display Order, Thumbnail (cover), PDF (the file), Source URL (old-site link — re-host before launch), Pages, File Size, Slug.

Historic Photos — Name (internal), Category (Historic / Aerial / Founding), Display Order, Image, Caption (public text), Circa, Credit, Lightbox Caption (auto-built caption for the popup), Slug.

Documents — Name, Year, Display Order, Description, File (the upload), Source URL (old-site link — re-host before launch), File Size, Slug.

Timeline Events — Name, Year (numeric, for sorting), Year Label (display form, e.g. “c. 1870”), Display Order, Description, Slug.

7. Publishing your changes

Saving an edit stores it as a draft—it is not live yet. To make changes public, click Publish. Until then, visitors still see the previous version.

A good habit: make all your edits, review them, then publish once.

8. Images, files & SEO

  • Images: Upload a reasonably sized image (large but not enormous—roughly 2000px on the long edge is plenty). Always add alt text describing the image; it helps screen readers and search engines.
  • Search results (SEO): Each main page has a Title and Description that show up in Google. Edit these from the Settings panel (page settings). Keep titles short and descriptions to a sentence or two.

9. A few things to be careful with

  • Don’t change a Slug after launch. The slug is the item’s web address. Changing it breaks any existing links and bookmarks to that page.
  • Don’t delete fields or whole collections—that removes data from every item at once. Edit individual items instead.
  • Design changes (fonts, colors, page layout) belong in the Designer—leave those to your web partner.
  • When in doubt, Archive instead of Delete, and ask before removing anything that other pages might link to.

10. Pre-launch checklist For your web partner

  • Re-host linked files. Newsletters and Documents currently have a Source URL pointing at files on the old cedarlakepark.org. Upload those files into Webflow (the PDF / File fields) so nothing depends on the old host, then the Source URL can be retired.
  • Connect the custom domain. The site currently publishes to the Webflow staging subdomain; connect cedarlakepark.org when ready to go live.
  • Add content editors. Invite the client’s editors through Webflow’s Client Seats with the Content editor role, so they can update content and publish without full Designer access. (Webflow’s legacy Editor is retired in 2026—Content editor seats are its replacement.)

11. Getting help

You can’t break the design by editing content, so explore with confidence—and when something feels uncertain, save a draft and ask before publishing.

12. Brand assets

A brand asset pack accompanies this site — logos, favicon, social share cards, colors, and fonts. Keep the master files in a shared folder (for example the organization's Google Drive) so future editors and partners can always find them.

  • Logos: horizontal lockup (site header, email signatures), a stacked lockup, and the emblem/mark on light or forest-green backgrounds.
  • Favicon & social avatar: the small browser-tab icon, plus a square 1:1 profile image for the Facebook, Instagram, and YouTube accounts.
  • Share cards (Open Graph): the 1200×630 image shown when a page is shared on social media. The default card (lake scene with the “Nurture Nature” tagline) is already set across the site.
  • Colors: Forest Ink #1C3A24, Pine #2F5233, Sage #8D9B82, Paper #E9E3D4, Warm White #F3EEE4.
  • Fonts: the site loads Newsreader (headings) and Source Sans 3 (body) automatically from Google Fonts; the logo wordmark uses a Goudy-style face.

To change the browser icon, upload the favicon in Site Settings → General → Favicon & Webclip. To change a page’s share image, use Page Settings → Open Graph.