[Feature Request] Enhance Shopping List with Rich Attributes (Notes, URLs, Reminders & Document Linking) via Minimalist Approach

[Wanderknight3]

Hi there,

First of all, as a self-hosted enthusiast, I would like to express my sincere gratitude to the developers and the community for this amazing project. Yuvomi’s elegant UI and lightweight architecture make it a real joy to use for family management.

While exploring the Shopping module, I noticed a practical pain point in real-world family provisioning: a shopping item often requires more context than just a name and quantity. For example, when buying specific hardware replacements, pantry stock, or brand-specific items, we desperately need to track extra metadata.

To align with Yuvomi’s brilliant core philosophy of "No build steps, no extra heavy frameworks, and keeping independent modules", I would love to propose a minimalist yet powerful enhancement for the Shopping list items.

1. Core Feature Requirements (The 4 Attributes)

Instead of a simple text string, an item in the shopping list could optionally support:

• Notes/Description: For entering specific sizes, flavors, or instructions.
• URLs: For quick access to online store links (multi-platform comparison).
• Images/Attachments: For visual verification at the supermarket.
• Reminders: Due dates for recurring purchases (e.g., "Buy water filters every 3 months").

2. The Minimalist Implementation (Leveraging Existing Modules)

To avoid rewriting the wheel or bloating the codebase, we can achieve this purely through modular cross-linking:

• Image/File Attachment: Instead of creating a new file-upload system inside the Shopping module, allow shopping items to link to an existing file/id in the Documents module.
• Reminders: Directly hook into the existing internal Reminders engine to trigger system notifications or Web Push/ntfy alerts.

3. Cross-Module Synergies

• Finances Integration: When checking off a high-value item in the shopping list, optionally prompt a toggle: "Log this into Finances?", automatically syncing the item name and price into the budget logs to prevent double-entry fatigue.
• Tasks/Calendar Linkage: Allow a Task or Calendar event to link to a specific shopping item/list (e.g., the task "Fix Kitchen Sink" links to the shopping item "Water Hose").

4. UX & "Restrained Design" Balance

To preserve the ultra-clean UI, we can use Progressive Disclosure:

• Default View (Inline): The main shopping list remains exactly as it is now—clean text rows with checkboxes. If an item contains extra details, display a tiny, subtle icon (e.g., 🔗, 🖼️) next to the text.
• Detail View (Drawer): Clicking the item or a "More" button slides out a sleek side drawer/modal containing the rich text notes, clickable links, image previews, and reminder configurations.

This approach brings asset-level depth to the shopping flow without introducing any heavy database footprints or UI noise.

Thanks again for everyone's hard work and dedication to this project! Looking forward to hearing your thoughts.

[ulsklyc]

Hi @Wanderknight3 — thank you for such a thoughtful, well-structured proposal (and the kind words 🙏). You framed it around Yuvomi's "independent modules / no bloat" philosophy, and that framing is exactly what guided how I scoped it.

Shipped in v0.87.0 — the minimalist core of your idea

• Notes and a product/store link on every shopping item.
• Edited in a compact per-item detail drawer (progressive disclosure) opened from a small pencil button — the quick-add row stays exactly as clean as before, and a subtle inline icon marks items that carry extra info. That's your "clean text rows + tiny icon + slide-out drawer" design, essentially as you sketched it.
• Notes are indexed in the global search, and links open in a new tab (only http(s) URLs are accepted, for safety).

Intentionally left out for now — and the honest reasoning

• Reminders ("buy filters every 3 months") — Yuvomi's reminders are one-shot; recurrence lives in Tasks. A shopping item is ephemeral (you check it off and it's gone), so a recurring purchase is really a recurring task that generates an item, not an item that reminds itself. That already exists via recurring tasks, so bolting recurrence onto items would fight the data model.
• Finances sync on check-off — this needs a price field on items (turning the list into a mini purchase-tracker) plus a shopping-category ↔ budget-category mapping. Real cost for a fairly niche workflow.
• Document attachment & Task/Calendar linking — technically cheap (one FK each), but each adds a new cross-module coupling. Keeping those as separate, individually-weighed requests is the most faithful reading of the "independent modules" principle you cited.

None of those are a "no" forever — they're just better as their own threads so each can be judged on its own merits. But the everyday win (notes + links) is live today.

Thanks again for the excellent write-up! 🛒