Upcoming feed
Follow the features, fixes, and platform work LoreKeep is building next.
Use this feed to see what is planned, already in progress, and likely to land in the public updates history next.
Latest upcoming
Extension-first cover recovery is the next priority
LoreKeep needs a stronger no-AI-cost cover recovery pipeline for entries saved from reading pages, especially when the extension can only capture fallback artwork.
What is planned
- Extend the browser extension Quick Save payload with canonical URLs, source domains, meta images, JSON-LD images, headings, descriptions, breadcrumbs, chapter signals, and poster-like image candidates.
- Add backend cover verification so missing, broken, tiny, banner-like, logo-like, or known fallback images create a cover recovery job instead of becoming permanent bad covers.
- Create CoverRecoveryJob and CoverCandidate storage for recovery status, candidate image URLs, source URLs, confidence, dimensions, hashes, accepted/rejected state, and retry history.
Why it matters
- Entries saved from the extension should stop feeling broken when the original page does not expose a clean cover image.
- Good covers can be recovered automatically or suggested without charging for external AI usage on every failed save.
- Users keep control when confidence is uncertain through review, reject, retry, and manual cover URL actions.
Search visibility, clearer docs, and extension reliability are next
The next pass focuses on helping people actually find LoreKeep, making onboarding easier to follow, and continuing the highest-value extension reliability work.
Planned
- Set up the remaining SEO and indexing foundations so lore-keep.com is easier for search engines to discover and understand.
- Rebuild docs around onboarding, library setup, extension usage, and troubleshooting instead of broad placeholder sections.
Impact
- New users should have a better chance of finding the product without relying on direct links.
- People evaluating LoreKeep should understand how to use it faster, with less trial and error.
Planned browser support beyond Chrome
LoreKeep extension support is planned beyond Chrome, with Brave, Opera, and Firefox-compatible builds on the roadmap after the core Chrome flow is fully stable.
Planned
- Planned browser expansion after Chrome stability work
- Brave and Opera support are part of the near-term browser roadmap
Impact
- Users on non-Chrome browsers can see that broader support is on the roadmap
- Future extension support will be framed as expansion, not a separate product rewrite
Next up: extension reliability, resume flow, and private-beta polish
The next milestone is not broad feature expansion. It is making the extension trustworthy enough for repeat daily use: stronger popup cleanup, safer metadata detection, better duplicate prevention, clearer save and update feedback, and resume behavior that consistently returns readers to the right place.
Planned
- Clean up popup detector architecture so description, title, source, and chapter fixes stop regressing unrelated sites.
- Keep hardening the floating quick-save button as a strict update-only control for already tracked entries.
Impact
- Readers should trust that updating progress will touch the right entry instead of creating duplicate noise.
- Continue actions should feel dependable enough to use every day, not like a best-effort shortcut.
Featured collections and portfolio-style publishing are planned
The product direction already points beyond private tracking into featured collections and portfolio-style publishing, and that expansion is planned as one of the next larger experience steps.
Planned
- Build more intentional public-facing collection presentation.
- Support featured or showcase-style library surfaces beyond the private workspace.
Impact
- Users will have a clearer path from private organization to public presentation.
- Collections should feel more showcase-ready once this work lands.
Video support and richer entry media are next
Entry media already supports images cleanly, and the next planned step is expanding that layer toward video and richer presentation blocks.
Planned
- Expand entry media beyond image-only support.
- Add real video-aware handling where the media model already expects it.
Impact
- Collections will be able to present more varied content instead of relying on one cover image.
- Users who manage reference-heavy or media-heavy libraries should get a better presentation layer.
Guided screenshots and visual docs are planned
The documentation area is set up to expand with section-level screenshots and more visual walkthroughs instead of staying text-only.
Planned
- Add screenshots directly to major documentation sections.
- Add more step-by-step walkthrough content for the main workflows.
Impact
- New users should be able to understand the product faster without guessing what each screen is for.
- The docs area will become more useful as a reference during actual onboarding, not only as descriptive text.