EyeCare Content Library (Optics)

Paid pluginsize Mplanned, not built

Indicative price, not an offer: €19/mo; 500+ articles, optometry-reviewed, SEO-tagged

Generated from docs/plan/paid/eyecare-content-library/PLAN.md in the AstroBaaS repository. Nothing described below is implemented — it is the written plan for it.

EyeCare Content Library provides opticians with a pre-written, optometry-reviewed library of 500+ eye-health articles and educational content. Merchants can drag-and-drop articles into their blog, customize them, and auto-publish. Articles cover topics like ‘How to Care for Contact Lenses’, ‘Understanding Astigmatism’, ‘Blue Light Protection Guide’, all SEO-optimized and compliant with medical standards. This is a paid plugin requiring optometry expert review and weekly content updates (support commitment).

The problem

Opticians need trusted eye-health content to build authority and educate customers. Writing 500+ articles in-house costs €50,000+; hiring a medical writer is €100+/hour. Opticians compete on trust but lack the resources to produce ongoing educational content. Customers distrust product pages without supporting education.

What it does

• Pre-written library of 500+ articles on eye-health topics (care, conditions, products, lifestyle)
• Optometry-reviewed content (certified by an optometry expert; compliance attestation per article)
• SEO-optimized titles, meta descriptions, internal linking suggestions
• Weekly new content additions (2-3 new articles every week)
• Drag-and-drop import to merchant’s blog: one-click publish or customizable draft
• Customization: merchant can edit title, intro paragraph, or add optician-specific context
• Medical compliance notes: articles marked for GDPR medical data, HIPAA (US), or jurisdiction-specific compliance
• Attribution: article shows optometry expert byline and date reviewed
• Analytics: track article views, time on page, bounce rate per article
• Content categories: Navigation menu structure (Conditions, Care, Lifestyle, Products)
• Monthly changelog: library version 1.2 adds 3 new articles and updates 2 existing

What it deliberately does NOT do

Each boundary carries its reason. A boundary without a reason gets crossed by the next person who reads this.

• Personalized health advice — articles are educational, not medical diagnosis or treatment recommendation
• AI personalization (recommend article based on customer search) — scope is static library; AI is separate feature
• Live consultation booking (book eye test via article CTA) — scope is content only; booking is storefront responsibility

Data model

Plugin-owned collection: LibraryArticle (id, title, body, category, expertReview_id, dateReviewed, medicalCompliance_flags, seoKeywords). Merchant’s imported articles get articleSource_id reference to library. No core schema migration.

API

• GET /api/eyecare-library/articles — list all library articles with filters (category, compliance flags)
• GET /api/eyecare-library/articles/:id — fetch single article with SEO metadata
• POST /api/eyecare-library/articles/:id/import — import article to merchant’s blog (creates draft or published)
• GET /api/eyecare-library/updates — changelog: new articles, updates, version number
• GET /api/eyecare-library/compliance?jurisdiction=DE — filter articles by GDPR compliance

Every route added here must also appear in src/pages/openapi.json.ts — a test fails the build if it does not.

Admin

Library browser view: categories (Conditions, Care, Lifestyle), article cards showing title, summary, expert, review date, medical compliance badges. Import button opens customization form: edit title/intro or use default. ‘Import and Publish’ or ‘Import as Draft’. Analytics view shows article views, avg time on page, bounce rate per article. Changelog shows new articles this week.

The seam — why this is paid

Paid plugin owns: content creation and optometry expert review, medical compliance certification, weekly content updates, analytics. Core owns: blog storage, import workflow, content versioning.

Support commitment: optometry expert review, weekly new content, medical compliance

Dependencies

• rich-text-editor (articles are HTML/markdown)
• bulk-content-import (import mechanism)
• core-analytics (article view tracking)

Acceptance checks

Each of these must be able to fail. Before claiming this is done, break the code deliberately and watch each one go red.

• Library has 500+ articles covering eye conditions, contact lens care, and eyewear topics
• Each article shows optometry expert name and review date; compliance badges indicate GDPR/HIPAA status
• Merchant imports ‘Understanding Astigmatism’ article; article appears in draft blog with default title/content
• Merchant edits imported article title to ‘Astigmatism: A Guide for Our Customers’; changes persist after publish
• Library changelog shows ‘2 new articles added this week’ (version bump to 1.2)
• Analytics view shows ‘Understanding Astigmatism’ received 1,200 views this month, 3m 42s avg time on page

Risks

Medical compliance attestation not current (expert review date > 6 months old) exposes liability; refresh cycle must be enforced. Articles are derivative of source material (published without citation) creates IP risk. Imported articles edited by merchant are no longer under expert review; quality degrades post-import. Analytics requires cookie consent; disabled analytics breaks feature on privacy-first storefronts.

Commercial context

The anchor is what the nearest equivalent charges on Shopify or Magento today. It is context for a pricing decision, not the decision.

---

Generated from the commerce plan. See docs/COMMERCE-PLAN.md for the full catalogue and ../../AI-GUIDE.md for how to work on this repository.