Website Integrations are tools for website owners to add WebCull-powered publishing, saving, and sharing experiences to their own sites.
Let website owners embed a read-only WebCull public Collection in a blog, resource page, sidebar, or other existing site.
The widget reuses public Collection data and can offer a small set of list, preview, width, light, and dark variants without exposing bookmark management controls.
Give publishers a WebCull option alongside familiar sharing actions so readers can save the current page to their own bookmarks.
The first version is a URL-based handoff carrying the page URL, title, and optional metadata into WebCull. It can appear as a share-menu item, standalone button, or drop-down option.
Let a website owner publish a shared URL or public Collection through an approved custom domain and a curated read-only theme.
The owner continues managing bookmarks in WebCull while visitors see a fast publishing surface without editing controls. This remains a focused publishing feature rather than a general CMS.
The first Public Collection Widget is built. Website owners can reuse an existing public Collection as a read-only embedded surface instead of maintaining a second copy of the same links.
Build the URL-based Save to WebCull handoff so a publisher can add WebCull beside familiar sharing actions and pass the current page into the existing save flow.
Build the approved-domain publishing path and curated themes that turn an existing shared URL or public Collection into a dedicated read-only website.
Automated end-to-end tests will cover each integration from setup through real use: embedding and updating public Collection widgets, handing a page into Save to WebCull, and publishing read-only websites on approved custom domains.
The test suite will run these workflows across supported browsers, desktop and mobile layouts, light and dark themes, account states, Collection sizes, and changes to the source content. This coverage should catch broken connections between WebCull, publisher sites, and the public experience before launch.
Website Integrations place WebCull content and actions on outside domains, so every public, embedded, and URL handoff path will be treated as a hostile boundary and actively tested for abuse.
Adversarial testing will cover hostile publisher pages, malformed or forged save requests, content injection, authorization bypasses, cross-account access, custom-domain ownership, stale data, and attempts to expose private information or editing controls. Findings from this work will guide security and privacy improvements before the integrations fully launch.
Case studies will follow website owners using each integration in real publishing work: embedding a live public Collection, adding Save to WebCull to published content, and launching a read-only website on an approved custom domain.
Each study will document the publisher setup, ongoing use, reader experience, and any gaps that still need work. Together, they will show where Website Integrations are already useful and what should improve before the feature fully launches.
