Themes will make WebCull's appearance something you can choose, save, move between devices, schedule, and extend to public Collections. This page follows the product decisions and work behind that system.
A theme brings WebCull's colors, type, backgrounds, brightness, opacity, folder surfaces, and supported desktop appearance together as one reusable visual setup.
The boundary is deliberately visual. Choosing, saving, or sharing a theme will never include bookmarks, folders, account details, access settings, private URLs, or other personal data.
People should be able to preview a different look, apply it, adjust it, and return to the appearance they had before. Browsing curated themes or trying an imported file should not erase a custom setup.
Once applied, a theme becomes normal, editable WebCull display settings rather than locking the app to a file. If a theme is invalid or cannot be applied, the current appearance stays unchanged.
WebCull Themes will offer a curated collection of complete looks with real previews, descriptions, and details about where each theme works. New users can choose from the same collection during setup and revisit it later from Settings.
My Themes will hold the visual setups a person chooses to save. A current custom appearance or imported theme can be adjusted, named, updated, exported, or kept for later without turning every experiment into a permanent preset.
A portable WebCull theme file will carry a visual setup between accounts, devices, and supported WebCull apps. Importing one should provide a preview and a clear choice to apply or save it.
The same theme can adapt to its destination. The web app and browser extensions use the visual settings they support, while the desktop app can also include window transparency, native blur, and other desktop-only appearance choices.
Theme schedules will let someone choose a curated or saved theme for a specific local time, with optional brightness changes for morning, daytime, evening, or night.
Scheduled changes will update the same visible appearance controls as a manual change. A person can still make an immediate choice, and the next scheduled event can resume the planned rhythm without creating a separate hidden appearance state.
A public Collection is an authored experience, so its owner should be able to choose a curated theme or apply a compatible imported theme to the shared page.
The Collection's appearance remains separate from private WebCull settings. Visitors see the look chosen for that Collection without changing their own theme, and the author's private workspace stays untouched.
WebCull can export, import, preview, validate, apply, and revert portable theme files. Invalid or unsafe content is rejected without changing the current appearance.
Imported values are assimilated into normal visual settings so a theme remains editable instead of becoming a separate permanent state.
The Themes area brings curated presets, the current custom appearance, imported themes, and saved personal themes into one place.
Scheduled themes can change appearance by time of day, desktop themes can include desktop-only visual settings, and public Collection authors can choose an appearance without changing a viewer's private theme.
New accounts can also choose a theme during the first-run experience while retaining the standard WebCull appearance as a clear option.
The curated library has stable ordering, descriptions, compatibility details, attribution, and previews. Theme assets are prepared for the web app, desktop app, browser extensions, and native packages.
WebCull maintains the curated theme list so new themes and refinements can be added over time.
Run complete private theme, public Collection, desktop appearance, scheduling, onboarding, import, export, recovery, and feature-hidden workflows across supported environments.
Failures found here become new testing checkpoints or return to Developing when they require product changes.
Approve customer-facing copy, translate the experience, review the complete curated set, confirm release and rollback readiness, and deliberately enable Themes for everyone.
Until this checkpoint is complete, Themes remains partial so the full launch is not presented as finished.
