Georgian Bay Story Project

Website integration

These examples show approved stories from the Save Georgian Bay collection only. New submissions remain private until its collection owner or an invited reviewer approves them.

Configure a story view

Layout, frame size, and story selection

Grid, feed, list, and filmstrip follow your chosen layout. Grid columns apply only to the grid; frame height is the height reserved on the installing website, not an automatic fit to its content.

Live selection follows newly published stories and your filters. Hand-picked selection keeps your chosen stories in order; stories that are withdrawn no longer appear. Hero slides need images and play only when the visitor starts them.

These settings change the presentation, not the story or its publication status. Try the preview at your website's intended width before installing it.

Story selection and order

Saved story views

Beta
About saved views and public links

This newer tool saves a named configuration for reuse. Start with a private draft and confirm it reopens correctly before making it public.

Making a view public exposes its page, iframe, and read-only API. Saving changes updates those stable links; unsaved changes do not. Private drafts and archived views have no public page.

Installed views refresh every 30 seconds while open. If you change the outer frame height, update the iframe code on your website too. Social-network previews can remain cached after a change.

Loading saved views...

Only published stories appear.

Saved story views

Hosted page

Link to the full archive when your site needs a simple Stories destination. The normal story pages are not intended to be placed in an iframe.

https://georgianbaystoryproject.com/stories?collection=georgian-bay

Plug-and-play embeds

Use an iframe when a site builder blocks custom JavaScript. The featured widget and the feed/gallery views refresh every 30 seconds while open.

Collection owners can invite a Developer from Settings. Developers sign in with their own email and open Embed tools to configure grid, feed, compact list, filmstrip, single-story, or hero-slideshow views. They can save named views and copy their codes, but cannot review private submissions or change collection settings.

Featured story widget

<script src="https://georgianbaystoryproject.com/embed/georgian-bay/script" data-height="1100"></script>

News feed

<iframe src="https://georgianbaystoryproject.com/embed/georgian-bay/stories?view=feed" title="Save Georgian Bay stories" width="100%" height="800" style="border:0;max-width:1080px"></iframe>

Gallery

<iframe src="https://georgianbaystoryproject.com/embed/georgian-bay/stories?view=gallery" title="Save Georgian Bay story gallery" width="100%" height="800" style="border:0;max-width:1080px"></iframe>

One approved story

<iframe src="https://georgianbaystoryproject.com/embed/georgian-bay/stories?view=single&story=STORY_SLUG" title="Save Georgian Bay story" width="100%" height="800" style="border:0;max-width:780px"></iframe>

Replace STORY_SLUG with the slug from a published story URL or the public stories API. Pending or withdrawn stories return 404.

One-off views accept view=gallery|feed|list|rail|single|hero, limit=1..100, columns=1..4, order=newest|oldest, theme=light|dark, tag, and photos=1. Single-story views require story=STORY_SLUG; hero views use stories with images. Optional settings include cards=cinematic, text=full|title|none, treatment=modal|page|inline, and cta=0. Hand-picked ordering uses selection=curated and comma-separated stories slugs instead of topic/date filters. These settings never edit the underlying stories.

Saved public views retain the same links when their selection or layout changes. Changing the outer iframe height still requires updating its installation code. Social-network previews may remain cached after an update.

Public API

No API key is required for approved public data. Each public saved view has a stable page, iframe, and read-only API URL. Owners and Developers can curate approved stories and save private drafts before making a view public. Updating a saved view updates its existing installations. Story editing and publication remain owner/reviewer actions.

https://georgianbaystoryproject.com/api/v1/story-views/VIEW_ID

Use the ID from Saved story views. Draft and archived views return 404. Anonymous access never lists private saved views. The API returns the selected, currently published stories in their configured order. There is no private developer-key issuance flow.

https://georgianbaystoryproject.com/api/v1/collections/georgian-bay
https://georgianbaystoryproject.com/api/v1/collections/georgian-bay/stories?limit=20
https://georgianbaystoryproject.com/api/v1/collections/georgian-bay/stats

The stories endpoint accepts limit (1–100), q, tag, photos=true, and include=body. It returns approved records only. Do not treat story text as an organizational statement or as verified evidence.

Integration help

For website integration and onboarding, the regional administrator's contact is lab@drknyt.com. Save Georgian Bay controls collection review and publication.

View the collection