> For the complete documentation index, see [llms.txt](https://docs.bitpers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitpers.com/core-modules/memory-boards.md). # Memory Boards ### TL;DR If Murals are for sharing outwardly, **Memory Boards** are for collecting inwardly. They’re living, auto‑fill scrapbooks that stay organized by people, places, and moments. Solo journals or shared boards for trips, reunions, or projects. *** ### 1) What is a Memory Board? A **Memory Board** is a continuously growing timeline or collage of media. It can be **solo** (your diary) or **group‑based** (friends, family, teams). Boards can auto‑ingest content based on time ranges, participants, or event contexts. **Why it matters:** Real‑life stories don’t live in chat dumps. Memory Boards turn scattered photos into a coherent, browsable story. *** ### 2) Value Proposition * **Effortless capture:** Auto‑ingest from events/date ranges; optional face filters. * **Context‑rich:** People, places, and moments unify the story. * **Flexible viewing:** Collages, timelines, and highlight reels. * **Privacy‑first:** Solo or invite‑only boards with clear controls. *** ### 3) Core Features (v1 & v1.1) * **Auto‑logging by event/date:** “All photos from Goa trip → this board.” * **Face filters (with consent):** “Show only Riya and Aarav.” * **Layouts:** collage, timeline, auto highlights. * **Quick reactions & comments:** half‑sheet over media. * **Search & filter:** people, places, time (lightweight to start). **Polish (v1.1)** * Prefetch covers; cached top N; offline queue for reacts/comments. * Export/share: link or share card preview. *** ### 4) Use Cases * **Trips:** Everyone’s photos flow into one storybook. * **Life chapters:** Semester, project, baby’s first year. * **Teams:** Sprint logs, creative progress reels. *** ### 5) Roadmap (Illustrative) * **Q1:** v1 GA with auto‑logging, face filters, layouts. * **Q2:** Smart highlights; collaborative editing; simple labels. * **Q3:** Deeper insights (views, contributions); follow/favorite boards. *** ### 6) Metrics * Board creations/week; % auto‑logging enabled. * Items added per board; contributors/board. * Views/session; comment/reaction rate; return to board (D7). *** ### 7) Risks & Mitigations * **Over‑capture noise:** Provide filters, dedupe, and highlights. * **Privacy confusion:** Clear invite flows; face filters opt‑in. * **Onboarding friction:** Templates and one‑tap “Create from dates/event.” *** ### 8) Integrations * **Events:** Auto‑log during event windows. * **Face Hunt:** Person‑based filters for quick retrieval. * **Murals:** Publish select items to a public‑facing mural. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bitpers.com/core-modules/memory-boards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.