qr-code-link

byChuene Ramohale

Yes — now I understand exactly. We should make Divine Light small first. Don't build the cargo system, payments, complicated accounts, or large platform yet. The first MVP should be a simple QR + Link Creator that you operate for customers. The idea is: Customer comes to you → tells you what they want to share → you enter it → Divine Light creates a QR code + link → customer receives it → other people scan/open it. For example, someone could ask: > “Create me a QR code for my WhatsApp, Facebook, TikTok and phone number.” You create one page containing all of those. Or someone says: > “I have a story about my village. I want people to open my video and information.” You create a Divine Light page and give them a link. Here is the small MVP I recommend starting with: DIVINE LIGHT SIMPLE QR CODE + LINK CREATOR 1. PURPOSE Divine Light is a small service tool operated by the Founder. Customers come to the Founder and ask for a QR code or a shareable link. The Founder enters the customer's information and creates a simple digital page. The system then creates: QR CODE + SHAREABLE LINK The customer can send the link to people or give people the QR code to scan. Do NOT build cargo, payments, subscriptions, complex customer accounts, or advanced tracking in this first version. Keep the MVP simple and functional. --- 2. FOUNDER DASHBOARD The Founder logs into a private dashboard. Show: DIVINE LIGHT CREATE NEW MY PAGES SETTINGS --- 3. CREATE NEW PAGE When the Founder selects: CREATE NEW show: WHAT DO YOU WANT TO CREATE? Options: BUSINESS For a small business or large business. PERSONAL For a person. CONTACT For phone, WhatsApp, email and social accounts. STORY For a story, village story, project, article, video or information. LINK For an existing website, app, video or online page. CUSTOM For anything else the customer wants to share. --- 4. CONTACT PAGE This is one of the most important features. Allow the Founder to enter: Name Phone Number WhatsApp Number Facebook Link TikTok Link Instagram Link YouTube Link Email Website Profile Photo/Logo Description The system creates one simple page containing all selected information. Example: BLACK MIKE [Photo] About Short description. CONTACT 📞 CALL 💬 WHATSAPP ✉️ EMAIL SOCIAL Facebook TikTok Instagram YouTube --- 5. BUSINESS PAGE For a business customer, enter: Business Name Logo Phone WhatsApp Email Facebook TikTok Instagram YouTube Website Business Description Address Opening Hours Business Photos The system creates a simple business page. Example: BLACK MIKE VILLAGE BUSINESS [Logo] Business description. CALL WHATSAPP FACEBOOK TIKTOK INSTAGRAM YOUTUBE WEBSITE LOCATION --- 6. STORY PAGE This is for something like: Black Mike Village or a village story/project. The Founder can enter: Title Description Main Image Video Link Website/App Link Facebook Link YouTube Link TikTok Link Other Link The system creates a public page. Example: BLACK MIKE VILLAGE [Main Image] Story description. WATCH VIDEO VISIT WEBSITE OPEN APP FACEBOOK YOUTUBE TIKTOK --- 7. LINK PAGE If the customer already has something online, the Founder can simply create a Divine Light link for it. Example: Customer gives: "https://example.com" Divine Light creates a page/link that directs people to that destination. This can be used for: - Website - Video - App - Social media - Online story - Online form - Other public webpage --- 8. UNIQUE DIVINE LIGHT LINK Every page created should receive a unique link. Example: "https://divinelight.app/p/black-mike-village" or: "https://divinelight.app/p/mamas-business" The Founder can: COPY LINK OPEN LINK SHARE LINK --- 9. QR CODE Every published page can automatically receive a QR code. The QR code points to the Divine Light page. Example: QR Code ↓ "https://divinelight.app/p/black-mike-village" When someone scans it: The Divine Light page opens. --- 10. WHAT THE PERSON SCANNING SEES Example: Someone scans the QR code for Black Mike Village. The phone opens: BLACK MIKE VILLAGE [Image] Story information. WATCH VIDEO OPEN APP FACEBOOK YOUTUBE TIKTOK SHARE The person does not need a Divine Light account. They simply scan and view the page. --- 11. QR RESULT SCREEN After the Founder creates a page, show: YOUR QR CODE IS READY Display: QR CODE PUBLIC LINK Buttons: DOWNLOAD QR Download the QR image. COPY LINK Copy the public link. SHARE Share the link/QR. OPEN PAGE Preview the public page. PRINT Open a print-friendly QR version. --- 12. EDIT PAGE The Founder can open any page and select: EDIT Change: - Name - Phone - WhatsApp - Social links - Images - Description - Video - Website - Other information Save changes. The existing Divine Light link remains the same. The QR code continues pointing to the same page. --- 13. MY PAGES The Founder dashboard shows all created pages. Example: Black Mike Village Type: Story Status: Active Link: "divinelight.app/p/black-mike-village" Actions: OPEN EDIT QR COPY LINK SHARE DEACTIVATE --- 14. DEACTIVATE The Founder can deactivate a page. If someone opens the link after it has been deactivated, show: THIS PAGE IS CURRENTLY UNAVAILABLE The Founder can reactivate it later. --- 15. SIMPLE PAGE CREATION FLOW The Founder does: CREATE NEW ↓ Choose: BUSINESS / PERSONAL / CONTACT / STORY / LINK / CUSTOM ↓ Enter information. ↓ PREVIEW ↓ PUBLISH ↓ Divine Light creates: PUBLIC LINK + QR CODE ↓ Founder gives the customer the link and QR code. --- 16. EXAMPLE — PHONE NUMBER Customer says: «"I want people to scan my phone number."» Founder selects: CONTACT Enters the phone number. Divine Light creates the page. The public page has: CALL The QR code points to that page. Person scans. ↓ Page opens. ↓ Person taps: CALL --- 17. EXAMPLE — WHATSAPP + SOCIAL MEDIA Customer says: «"I want one scanner for my WhatsApp, Facebook and TikTok."» Founder enters: - WhatsApp - Facebook - TikTok Divine Light creates one page. The QR code points to that page. Person scans once. ↓ They see: WHATSAPP FACEBOOK TIKTOK They choose what they want. --- 18. EXAMPLE — BUSINESS Customer says: «"I have a business. I want people to scan and see my business."» Founder enters the business information. Divine Light creates: Business page + Link + QR code The customer can put the QR code on their business card, poster, vehicle, shop, flyer or social media. --- 19. EXAMPLE — STORY Founder creates: BLACK MIKE VILLAGE Adds: - Story - Photos - Video - YouTube - Facebook - Other links Divine Light creates: "divinelight.app/p/black-mike-village" Then create a QR code for that page. Now the Founder can say: "Scan this to see the Black Mike Village story." Or simply send: divinelight.app/p/black-mike-village --- 20. IMPORTANT DESIGN RULE The QR code itself should normally contain the Divine Light public URL. Do not put a large amount of personal information directly inside the QR code. Use: QR → Divine Light page → Information This means the Founder can update the page later without changing the QR code. --- 21. PRIVATE FOUNDER AREA Only the Founder can create and manage pages. Normal visitors cannot access the dashboard. The Founder can: - Create pages - Edit pages - Delete/deactivate pages - Generate QR codes - Download QR codes - Copy links - Share links - Preview pages --- 22. SIMPLE DATA STRUCTURE PAGES Each page should contain: - Page ID - Page type - Page name - Public URL slug - Description - Phone - WhatsApp - Email - Facebook - TikTok - Instagram - YouTube - Website - Images - Video links - Address - Status - Created date - Updated date Only fields actually used by a page need to be displayed publicly. --- 23. MOBILE-FIRST DESIGN Divine Light must work well on phones. The Founder should be able to create a page from a phone. The public page must also work well on phones. QR codes must be large and easy to scan. Do not allow text or buttons to be cut off. --- 24. MVP DESIGN Use a simple Divine Light identity: DIVINE LIGHT SCAN. CONNECT. SHARE. Clean interface. Simple navigation. Large buttons. Clear QR-code display. Fast public pages. Do not overload the first version with unnecessary features. --- 25. FIRST VERSION ONLY Build these features first: FOUNDER - Login - Dashboard - Create Page - Edit Page - My Pages - Generate QR - Download QR - Copy Link - Share Link - Preview Page - Print QR PAGE TYPES - Business - Personal - Contact - Story - Link - Custom PUBLIC - Public page - Phone button - WhatsApp button - Social-media buttons - Website button - Video button - Share button --- FINAL DIVINE LIGHT MVP The entire first product should be based on this simple idea: YOU COME TO DIVINE LIGHT. YOU TELL US WHAT YOU WANT PEOPLE TO SEE. WE CREATE IT. WE GIVE YOU A LINK. WE GIVE YOU A QR CODE. PEOPLE SCAN OR OPEN THE LINK. THEY SEE YOUR INFORMATION. The system is: CUSTOMER REQUEST ↓ FOUNDER CREATES PAGE ↓ PUBLIC LINK ↓ QR CODE ↓ SCAN ↓ INFORMATION Start with this small version. Build it successfully first. Later, Divine Light can be upgraded with cargo, payments, customer accounts, analytics, custom domains, printing services, and other business features.This is the version I would build first. It gives you one simple service you can actually demonstrate: “Give me what you want people to see, and I'll create your link and QR code.”

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for qr-code-link

1. Introduction

Divine Light is a small service tool operated by the Founder. Customers come to the Founder and ask for a QR code or a shareable link. The Founder enters the customer's information and creates a simple digital page. The system then creates a QR code and a shareable link. The customer can send the link to people or give people the QR code to scan.

The product intent is a simple QR + Link Creator that the Founder operates for customers: the customer tells the Founder what they want to share, the Founder enters it, Divine Light creates a QR code + link, the customer receives it, and other people scan or open it. The audience is the Founder working from a phone plus everyday scanners in mobile-first, often low-bandwidth contexts.

Page 1 of 20

2. System Overview

Divine Light currently delivers a Founder-operated page minting service. The Founder logs into a private dashboard, selects a page type, enters the customer's information, previews, and publishes. Publishing produces a durable public link in the form https://divinelight.app/p/<slug> and a QR code that points to that public page. The Founder can then download the QR image, copy the link, share the link/QR, open the public page, and print a print-friendly QR version. The Founder can edit any page later without changing its link or QR destination, and can deactivate or reactivate a page.

Two accepted human personas act in the current product: the Founder (Divine Light Operator), who creates and manages pages, and the Page Visitor (Scanner / Link Opener), who scans the QR code or opens the shared link and views the public page without needing a Divine Light account.

Current delivery is a first-party web application with application-owned identity for the Founder only. The Founder account is provisioned or invited before first use; the Founder completes returning verification through Login before protected dashboard access. Public pages are anonymously reachable. Normal visitors cannot access the dashboard.

Narrow exclusions for this first version: cargo, payments, subscriptions, complex customer accounts, and advanced tracking are not built. Cargo, payments, customer accounts, analytics, custom domains, printing services, and other business features are deferred to later upgrades.

Page 2 of 20

2a. Product Interpretation and Delivery Boundary

Divine Light is a wayfinding service: a QR is a signpost, a public page is a sign, and the Founder dashboard is the sign shop. The current product is deliberately small and functional. The Founder is the only operator; customers do not log in and do not manage their own pages. Visitors never need an account — they simply scan and view.

Access ownership is split cleanly. The Founder's private area (dashboard, create, edit, my pages, QR result, settings) is application-owned and protected by Founder verification. The public page and the landing screen are anonymously reachable. The QR code itself normally contains the Divine Light public URL rather than a large amount of personal information, so the Founder can update the page later without changing the QR code: QR → Divine Light page → Information.

Everything beyond this first version — cargo, payments, subscriptions, complex customer accounts, advanced tracking, analytics, custom domains, and printing services — is a future horizon and is not part of current pages or acceptance.

2b. Source Content Inventory

The uploaded brand reference image shows the "Divine Light" gold wordmark over a warm golden-hour photograph with a "C-M-R" badge. It is used as brand and visual direction for the Divine Light identity. No verified factual entities, collections, contact records, or media references beyond this brand/visual direction were supplied as content source material.

2c. Page Content and Component Coverage

Page 3 of 20

Landing

  • Information/state: Anonymous first impression explaining Divine Light's scan, connect, and share service. Full-width warm-paper field with a 3px red line running edge to edge at the top. Left-aligned 76px Fira Sans headline in ink — "SCAN. CONNECT. SHARE." — set as three stacked words with the middle word dropped one grid column and set in red. To its right, a single large white QR plate (240px) that is a real, scannable code pointing at a live example page, with its /p/ slug in mono beneath it. Below, a numbered 01–04 row explaining CUSTOMER REQUEST → FOUNDER CREATES → LINK + QR → SCAN, drawn as a transit-line diagram with red line segments and yellow interchange dots. A schematic "QR → PAGE → INFORMATION" diagram appears once as the product's core explanation.
  • Primary actions: Reach the Founder Login entry.
  • Supporting actions: Scan the example QR plate to open a live example public page.
  • Domain entities: Example public page reference, /p/ slug.
  • Component responsibilities: Hero headline block, hero QR plate with mono slug caption, numbered transit-line explainer row, QR → PAGE → INFORMATION diagram.
  • States: Loading (hero QR plate resolving), empty (no example page configured — explainer row still renders), success (QR plate renders scannable), error (example QR unavailable — explainer row and Login entry remain usable), recovery (retry QR plate render).
Page 4 of 20

Login

  • Information/state: Founder identity access surface. The privileged Founder account is provisioned rather than opened for arbitrary public enrollment. Warm-paper ground, white card, 2px ink border, hard 2px offset shadow.
  • Primary actions: Founder completes returning verification to reach the private dashboard.
  • Supporting actions: None beyond verification.
  • Domain entities: Founder credential.
  • Component responsibilities: Verification form, submit control, error messaging.
  • States: Loading (verification in progress), empty (no credentials entered), success (redirect to DIVINE LIGHT dashboard), error (invalid credentials — clear message, retry), recovery (re-enter credentials).
Page 5 of 20

Public Page

  • Information/state: Anonymous destination opened from a Divine Light QR code or public link. Single 640px column: big name, photo plate, description, then a stacked list of full-width action rows. A 3px red rule runs across the top. Only fields actually used by the page are displayed publicly. Example: BLACK MIKE VILLAGE, [Image], story information, WATCH VIDEO, OPEN APP, FACEBOOK, YOUTUBE, TIKTOK, SHARE.
  • Primary actions: Tap CALL, WHATSAPP, EMAIL, WEBSITE, WATCH VIDEO, or a social row (FACEBOOK, TIKTOK, INSTAGRAM, YOUTUBE) to reach the customer's destination.
  • Supporting actions: SHARE the page.
  • Domain entities: Page name, page type, description, phone, WhatsApp, email, Facebook, TikTok, Instagram, YouTube, website, images, video links, address, opening hours, status.
  • Component responsibilities: Name heading, photo plate (white plate, 1px ink frame, uncropped-to-square, muted caption line), description block, stacked 56px action rows each with left pictogram, ALL-CAPS label, mono destination hint, and chevron.
  • States: Loading (page resolving), empty (no optional fields supplied — only used fields render), success (page renders with action rows), error (page not found), unavailable (deactivated page shows "THIS PAGE IS CURRENTLY UNAVAILABLE"), recovery (visitor returns to the QR or link source).
Page 6 of 20

DIVINE LIGHT

  • Information/state: Private Founder dashboard entry showing Divine Light navigation and access to page-management work. Left rail (desktop) / bottom bar (phone) with four numbered nav items — 01 CREATE NEW, 02 MY PAGES, 03 SETTINGS, 04 LOGOUT — each with a small pictogram and a red 3px active line. A 3px red rule runs under the dashboard header.
  • Primary actions: Navigate to CREATE NEW, MY PAGES, SETTINGS, LOGOUT.
  • Supporting actions: None.
  • Domain entities: Founder session.
  • Component responsibilities: Numbered nav rail/bottom bar, active-line indicator, header rule.
  • States: Loading (session resolving), empty (no pages yet — nav still available), success (dashboard renders), error (session expired — return to Login), recovery (re-verify through Login).

CREATE NEW

Page 7 of 20
  • Information/state: Founder workspace for selecting a page type, entering customer information, previewing, and publishing. Numbered stepper pinned to the top: 01 TYPE → 02 DETAILS → 03 PREVIEW → 04 PUBLISH. Step 01 shows "WHAT DO YOU WANT TO CREATE?" with options BUSINESS (for a small business or large business), PERSONAL (for a person), CONTACT (for phone, WhatsApp, email and social accounts), STORY (for a story, village story, project, article, video or information), LINK (for an existing website, app, video or online page), CUSTOM (for anything else the customer wants to share).
  • Primary actions: Select a page type; enter information; PREVIEW; PUBLISH.
  • Supporting actions: Move between stepper steps.
  • Domain entities: Page type, page name, public URL slug, description, phone, WhatsApp, email, Facebook, TikTok, Instagram, YouTube, website, images, video links, address, opening hours, status.
  • Component responsibilities: Numbered stepper with yellow interchange dots, page-type selection list, type-specific detail form, preview render, publish control.
  • Type-specific detail fields: CONTACT — Name, Phone Number, WhatsApp Number, Facebook Link, TikTok Link, Instagram Link, YouTube Link, Email, Website, Profile Photo/Logo, Description. BUSINESS — Business Name, Logo, Phone, WhatsApp, Email, Facebook, TikTok, Instagram, YouTube, Website, Business Description, Address, Opening Hours, Business Photos. STORY — Title, Description, Main Image, Video Link, Website/App Link, Facebook Link, YouTube Link, TikTok Link, Other Link. LINK — destination URL for an existing website, video, app, social media, online story, online form, or other public webpage. PERSONAL and CUSTOM — the customer's requested shareable information.
  • States: Loading (form initializing), empty (no type selected), success (page published, advancing to QR RESULT SCREEN), error (validation failure — inline field messages, entered data retained), recovery (correct fields and re-publish).
Page 8 of 20

QR RESULT SCREEN

  • Information/state: Result destination showing the generated QR code and public link. Banner reads "YOUR QR CODE IS READY". Centres a large QR plate with the public URL in mono directly beneath, followed by a 2×3 grid of action buttons. QR sits in a white plate with a 1px ink frame and a 12px quiet zone.
  • Primary actions: DOWNLOAD QR (download the QR image), COPY LINK (copy the public link), SHARE (share the link/QR), OPEN PAGE (preview the public page), PRINT (open a print-friendly QR version).
  • Supporting actions: None.
  • Domain entities: QR code, public link, /p/ slug.
  • Component responsibilities: Ready banner, QR plate, mono URL caption, 2×3 hard-shadow button grid.
  • States: Loading (QR generating), empty (not yet published), success (QR and link displayed), error (QR generation failed — retry), recovery (regenerate QR for the same unchanged link).
Page 9 of 20

MY PAGES

  • Information/state: Founder browse and management destination for created pages, statuses, links, and lifecycle actions. A ruled tabular list, not a card grid: columns Name | Type tag | Status dot | /p/slug (mono) | row actions, with horizontal rules between rows, like a departure board. Example row: Black Mike Village, Type: Story, Status: Active, Link: "divinelight.app/p/black-mike-village". Page-type tags render as small ALL-CAPS chips with a 1px ink border and a yellow left block.
  • Primary actions: OPEN, EDIT, QR, COPY LINK, SHARE, DEACTIVATE.
  • Supporting actions: Reactivate a deactivated page.
  • Domain entities: Page name, page type, status, public URL slug, created date, updated date.
  • Component responsibilities: Ruled table, type-tag chips, status dots (green #2E6B4F for Active, red for Unavailable), mono slug column, row action controls, 3px red left rule on hover.
  • States: Loading (list resolving), empty (no pages created yet — clear prompt to CREATE NEW), success (rows render), error (list failed to load — retry), recovery (reload list).
Page 10 of 20

EDIT PAGE

  • Information/state: Focused Founder workspace for changing an existing page while retaining its public URL and QR destination. Allows changing Name, Phone, WhatsApp, Social links, Images, Description, Video, Website, and other information.
  • Primary actions: Save changes.
  • Supporting actions: Return to MY PAGES or the public page.
  • Domain entities: All page fields; unchanged public URL slug; unchanged QR destination.
  • Component responsibilities: Pre-filled edit form, save control, confirmation that the link and QR are unchanged.
  • States: Loading (page loading into form), empty (no changes made), success (changes saved, link and QR unchanged), error (save failed — entered changes retained), recovery (retry save).

SETTINGS

  • Information/state: Preserved private Founder navigation destination for the specified Divine Light settings area.
  • Primary actions: Access Founder settings.
  • Supporting actions: None.
  • Domain entities: Founder settings.
  • Component responsibilities: Settings surface within the private Founder area.
  • States: Loading, empty, success, error, recovery consistent with the private Founder area.
Page 11 of 20

3. Functional Requirements

FR-1 — Founder-operated QR + Link creation service (explicit) As the Founder (Divine Light Operator), I should take a customer's request for what they want to share, enter it, and have Divine Light create a QR code + link that the customer receives and others scan or open, so that the customer gets a working shareable page.

  • Lifecycle: Trigger — a customer tells the Founder what they want to share. Input — the customer's information. Observable result — a published page with a public link and QR code. Access — Founder authenticated. Failure/recovery — validation errors are shown inline and entered data is retained for correction. Continuation — the Founder hands the customer the link and QR code.

FR-2 — Private Founder dashboard (explicit) As the Founder, I should log into a private dashboard showing DIVINE LIGHT, CREATE NEW, MY PAGES, and SETTINGS, so that I can reach all page-management work from one place.

  • Lifecycle: Trigger — Founder opens the application. Input — Founder verification. Observable result — dashboard with the four navigation entries. Access — Founder authenticated; normal visitors cannot access the dashboard. Failure/recovery — expired session returns the Founder to Login. Continuation — navigate to CREATE NEW, MY PAGES, or SETTINGS.
Page 12 of 20

FR-3 — Page type selection (explicit) As the Founder, I should see "WHAT DO YOU WANT TO CREATE?" with the options BUSINESS, PERSONAL, CONTACT, STORY, LINK, and CUSTOM when I select CREATE NEW, so that I can start the right kind of page for the customer's request.

  • Lifecycle: Trigger — Founder selects CREATE NEW. Input — page-type choice. Observable result — the matching detail form opens. Access — Founder authenticated. Failure/recovery — no type selected keeps the selection list available. Continuation — enter information for the chosen type.

FR-4 — CONTACT page type (explicit) As the Founder, I should enter Name, Phone Number, WhatsApp Number, Facebook Link, TikTok Link, Instagram Link, YouTube Link, Email, Website, Profile Photo/Logo, and Description, and have the system create one simple page containing all selected information with CALL, WHATSAPP, EMAIL and social buttons, so that a customer's contact details are reachable in one scan.

  • Lifecycle: Trigger — customer asks for a contact page. Input — the listed contact fields. Observable result — a public page rendering the selected information with CALL, WHATSAPP, EMAIL, and Facebook/TikTok/Instagram/YouTube buttons. Access — Founder authenticated to create; public page anonymous. Failure/recovery — invalid or missing required fields are flagged and retained. Continuation — preview, publish, and hand over the link and QR code.
Page 13 of 20

FR-5 — BUSINESS page type (explicit) As the Founder, I should enter Business Name, Logo, Phone, WhatsApp, Email, Facebook, TikTok, Instagram, YouTube, Website, Business Description, Address, Opening Hours, and Business Photos, and have the system create a simple business page with CALL, WHATSAPP, FACEBOOK, TIKTOK, INSTAGRAM, YOUTUBE, WEBSITE, and LOCATION, so that a business customer can be scanned and seen.

  • Lifecycle: Trigger — customer asks for a business page. Input — the listed business fields. Observable result — a public business page with the listed action buttons. Access — Founder authenticated to create; public page anonymous. Failure/recovery — invalid or missing required fields are flagged and retained. Continuation — preview, publish, and hand over the link and QR code.

FR-6 — STORY page type (explicit) As the Founder, I should enter Title, Description, Main Image, Video Link, Website/App Link, Facebook Link, YouTube Link, TikTok Link, and Other Link, and have the system create a public page with WATCH VIDEO, VISIT WEBSITE, OPEN APP, FACEBOOK, YOUTUBE, and TIKTOK, so that a village story, project, article, video, or information can be shared.

  • Lifecycle: Trigger — customer asks for a story page. Input — the listed story fields. Observable result — a public page with the listed action buttons. Access — Founder authenticated to create; public page anonymous. Failure/recovery — invalid or missing required fields are flagged and retained. Continuation — preview, publish, and hand over the link and QR code.
Page 14 of 20

FR-7 — LINK page type (explicit) As the Founder, I should create a Divine Light page/link that directs people to an existing destination the customer already has online, so that a website, video, app, social media, online story, online form, or other public webpage can be shared through Divine Light.

  • Lifecycle: Trigger — customer supplies an existing URL such as "https://example.com". Input — the destination URL. Observable result — a Divine Light page/link that directs people to that destination. Access — Founder authenticated to create; public page anonymous. Failure/recovery — an unusable destination URL is flagged and retained for correction. Continuation — preview, publish, and hand over the link and QR code.

FR-8 — PERSONAL and CUSTOM page types (explicit) As the Founder, I should be able to create a PERSONAL page for a person and a CUSTOM page for anything else the customer wants to share, so that requests outside the other types are still served.

  • Lifecycle: Trigger — customer request that fits a person or an unclassified share. Input — the customer's requested information. Observable result — a published public page. Access — Founder authenticated to create; public page anonymous. Failure/recovery — invalid or missing required fields are flagged and retained. Continuation — preview, publish, and hand over the link and QR code.
Page 15 of 20

FR-9 — Unique Divine Light link (explicit) As the Founder, I should have every created page receive a unique Divine Light link in the form https://divinelight.app/p/<slug> (for example /p/black-mike-village or /p/mamas-business), with COPY LINK, OPEN LINK, and SHARE LINK, so that each customer has one stable address to distribute.

  • Lifecycle: Trigger — page published. Input — page name/slug. Observable result — a unique public link with COPY LINK, OPEN LINK, SHARE LINK. Access — Founder authenticated to manage; link publicly openable. Failure/recovery — a slug collision is resolved to a unique slug before publishing. Continuation — distribute the link.

FR-10 — Automatic QR code (explicit) As the Founder, I should have every published page automatically receive a QR code that points to the Divine Light page URL, so that scanning opens the Divine Light page.

  • Lifecycle: Trigger — page published. Input — the page's public URL. Observable result — a QR code pointing to https://divinelight.app/p/<slug>. Access — Founder authenticated to generate; QR publicly scannable. Failure/recovery — QR generation failure offers retry against the same unchanged link. Continuation — download, print, or share the QR code.

FR-11 — QR result screen (explicit) As the Founder, I should see "YOUR QR CODE IS READY" with the QR CODE, the PUBLIC LINK, and the buttons DOWNLOAD QR, COPY LINK, SHARE, OPEN PAGE, and PRINT after creating a page, so that I can immediately distribute the result.

  • Lifecycle: Trigger — page published. Input — the published page. Observable result — the ready banner, QR code, public link, and the five buttons. Access — Founder authenticated. Failure/recovery — a failed action reports clearly and the QR and link remain displayed. Continuation — download the QR image, copy the link, share the link/QR, preview the public page, or open a print-friendly QR version.
Page 16 of 20

FR-12 — Edit page (explicit) As the Founder, I should open any page, select EDIT, change Name, Phone, WhatsApp, Social links, Images, Description, Video, Website, and other information, and save, with the existing Divine Light link remaining the same and the QR code continuing to point to the same page, so that corrections never invalidate distributed QR codes.

  • Lifecycle: Trigger — Founder opens a page and selects EDIT. Input — changed fields. Observable result — saved changes with an unchanged public link and unchanged QR destination. Access — Founder authenticated. Failure/recovery — a failed save retains the entered changes for retry. Continuation — return to MY PAGES or open the public page.

FR-13 — My Pages list (explicit) As the Founder, I should see all created pages with name, Type, Status, Link, and the actions OPEN, EDIT, QR, COPY LINK, SHARE, and DEACTIVATE, so that I can manage every page from one list.

  • Lifecycle: Trigger — Founder opens MY PAGES. Input — existing pages. Observable result — a list showing name, Type, Status, Link, and the six actions per page. Access — Founder authenticated. Failure/recovery — a failed list load offers retry. Continuation — open, edit, view QR, copy link, share, or deactivate a page.

FR-14 — Deactivate and reactivate (explicit) As the Founder, I should deactivate a page so that opening its link shows "THIS PAGE IS CURRENTLY UNAVAILABLE", and reactivate it later, so that a page can be taken out of service without losing its link or QR code.

  • Lifecycle: Trigger — Founder selects DEACTIVATE on a page. Input — the target page. Observable result — the public link shows "THIS PAGE IS CURRENTLY UNAVAILABLE" to visitors; the Founder can reactivate it later. Access — Founder authenticated to deactivate/reactivate; public page anonymous. Failure/recovery — a failed status change reports clearly and the prior status remains. Continuation — reactivate when the page should return.
Page 17 of 20

FR-15 — Page creation flow (explicit) As the Founder, I should follow CREATE NEW → choose BUSINESS/PERSONAL/CONTACT/STORY/LINK/CUSTOM → enter information → PREVIEW → PUBLISH → Divine Light creates PUBLIC LINK + QR CODE → give the customer the link and QR code, so that every page is produced through one predictable sequence.

  • Lifecycle: Trigger — Founder starts CREATE NEW. Input — page type and customer information. Observable result — a published page with a public link and QR code. Access — Founder authenticated. Failure/recovery — validation or publish failure keeps the entered information for correction. Continuation — hand the customer the link and QR code.

FR-16 — Public page action buttons (explicit) As a Page Visitor (Scanner / Link Opener), I should see and use a phone button, WhatsApp button, social-media buttons, website button, video button, and share button on the public page, so that I can act on the shared information in one tap.

  • Lifecycle: Trigger — visitor scans the QR code or opens the shared link. Input — a tap on an action row. Observable result — the visitor reaches the customer's destination (call, WhatsApp, email, social, website, or video) or shares the page. Access — no Divine Light account required. Failure/recovery — an unavailable destination reports clearly and the visitor can choose another row. Continuation — return to the page and choose another action.
Page 18 of 20

FR-17 — Page data structure (explicit) As the Founder, I should have each page hold Page ID, Page type, Page name, Public URL slug, Description, Phone, WhatsApp, Email, Facebook, TikTok, Instagram, YouTube, Website, Images, Video links, Address, Status, Created date, and Updated date, with only fields actually used by a page displayed publicly, so that pages carry complete records without exposing unused fields.

  • Lifecycle: Trigger — page created or edited. Input — the listed fields. Observable result — a stored page record; only used fields render publicly. Access — Founder authenticated to manage records; public page anonymous. Failure/recovery — a failed save retains entered values. Continuation — edit or publish.

FR-18 — Mobile-first operation (explicit) As the Founder, I should be able to create a page from a phone, with the public page also working well on phones, QR codes large and easy to scan, and no text or buttons cut off, so that the service works in the field.

  • Lifecycle: Trigger — Founder or visitor uses a phone. Input — touch interaction. Observable result — usable Founder creation and public viewing on a phone, with large scannable QR codes and no clipped text or buttons. Access — Founder authenticated for creation; public page anonymous. Failure/recovery — layout issues are corrected so nothing is cut off. Continuation — complete creation or viewing on the phone.
Page 19 of 20

FR-19 — Divine Light identity and interface (explicit) As the Founder, I should work in a clean interface carrying the Divine Light identity — DIVINE LIGHT, SCAN. CONNECT. SHARE. — with simple navigation, large buttons, a clear QR-code display, and fast public pages, so that the first version stays simple and functional.

  • Lifecycle: Trigger — any use of the product. Input — navigation and actions. Observable result — consistent Divine Light identity with simple navigation, large buttons, clear QR display, and fast public pages. Access — Founder authenticated for the private area; public page anonymous. Failure/recovery — degraded states keep navigation and core actions usable. Continuation — continue the current task.

FR-20 — First-version feature set (explicit) As the Founder, I should have exactly the first-version features — Founder: Login, Dashboard, Create Page, Edit Page, My Pages, Generate QR, Download QR, Copy Link, Share Link, Preview Page, Print QR; Page types: Business, Personal, Contact, Story, Link, Custom; Public: Public page, Phone button, WhatsApp button, Social-media buttons, Website button, Video button, Share button — so that the MVP stays uncluttered.

  • Lifecycle: Trigger — Founder or visitor uses the product. Input — the listed features. Observable result — the listed features are available and no unnecessary features are added. Access — Founder authenticated for Founder features; public features anonymous. Failure/recovery
Page 20 of 20

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.