# Lucent Digital — complete proposed website manuscript Proposed copy for design review. No page is authorized for publication by this manuscript. Version v9. Form field IDs and conditional requirements are aligned to the proposed CRM contract. This remains design content, not a live form. Sources: OWN-1, BASE-1, WEB-LD, CRM-2, CS-CONTENT1, CS-OWNER1, CS-SYS4. Private provenance is maintained separately. ## Site shell Desktop navigation: Services (/services/website-development) · How We Work (/how-we-work) · Who We Help (/who-we-help) · About (/about). Primary action: Discuss Your Project → /project-brief. Mobile: same named destinations in an accessible menu; wordmark and clear primary action remain visible. ### Footer copy Lucent Digital [NONPUBLISHABLE: verified operating/trading entity disclosure] [NONPUBLISHABLE: monitored contact route and actual staffed hours/timezone] Links: Privacy (/privacy) · Terms (/terms) · FAQs (/faqs) [NONPUBLISHABLE: correct rights holder and publication year] ### Image and proof direction Permissioned real work with Lucent role identified. Clearly label internal projects and concepts. No invented client logos/results. Use process diagrams and illustrative brief pages when portfolio proof is absent. - Use actual permissioned evidence only; omit unsupported testimonials, badges, counts and client logos. - Label process illustrations Example workflow and concepts Concept—not client work. - Never release NONPUBLISHABLE slots or internal editorial notes. - Confirm paid owners, qualified alternates and operating coverage before response-time or availability promises. - Order follows each page mobile_order; place hero CTA before decorative image. - Forms use one column and visible labels; errors link to fields and are announced. - No essential information on hover. Navigation exposes every service without hover. - No sticky element may cover controls, disclosures or status messages. - Vehicle fact tables become labeled field/value groups without dropping units, status or charges. - Respect reduced-motion preference; no autoplay film required for meaning. ## / — Build clearly. Grow deliberately. Page ID: `ld-home` · State: proposed SEO title: Websites, Apps & Digital Marketing | Lucent Digital SEO description: Define the right project, create the digital experience, and connect it to a clear marketing plan. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-home-hero → ld-home-s01 → ld-home-s02 → ld-home-s03 → ld-home-s04 → ld-home-s05 → ld-home-s06 → ld-home-action Mobile order: ld-home-hero → ld-home-s01 → ld-home-s02 → ld-home-s03 → ld-home-s04 → ld-home-s05 → ld-home-s06 → ld-home-action ### Build clearly. Grow deliberately. Section ID: `ld-home-hero` Eyebrow: Website Development · App Development · Marketing Strategy · Marketing Management Define the right project, create the digital experience, and connect it to a clear marketing plan. ### Creativity with direction Section ID: `ld-home-s01` Website development. App development. Marketing strategy. Marketing management. Start with the work your business needs. ### Four ways to begin Section ID: `ld-home-s02` Website Development: give visitors a clear route from understanding your offer to taking the next step. App Development: turn a defined user need or workflow into a scoped product. Marketing Strategy: clarify priorities and measurement. Marketing Management: coordinate the agreed recurring work. ### A clear starting point Section ID: `ld-home-s03` A development project begins with users, tasks and journeys. A marketing review begins with the offer, enquiry experience and available evidence. Scope, fee and timing are agreed before work begins. ### See the decisions behind delivery Section ID: `ld-home-s04` Our approach connects the problem to the proposed work, review criteria and handoff responsibilities. Where examples are shown, their role and evidence are identified; concepts are labeled as concepts. ### Define. Create. Review. Handoff. Section ID: `ld-home-s05` Agree the problem and scope. Develop the experience or action plan. Review against agreed criteria. Receive the deliverables and next-step responsibilities. Ongoing support is scoped separately where needed. ### What needs to work better? Section ID: `ld-home-s06` Bring the business problem, the people it affects and the outcome you want. You do not need to arrive with a finished technical specification. ### Discuss Your Project Section ID: `ld-home-action` Choose the next step when you are ready. Button: **Discuss Your Project** → /project-brief ## /services/website-development — A website with a clear job to do. Page ID: `ld-services-website-development` · State: proposed SEO title: Website Development | Lucent Digital SEO description: Help visitors understand your offer and move confidently toward the action that matters to your business. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-services-website-development-hero → ld-services-website-development-s01 → ld-services-website-development-s02 → ld-services-website-development-s03 → ld-services-website-development-s04 → ld-services-website-development-s05 → ld-services-website-development-creator-sites → ld-services-website-development-action Mobile order: ld-services-website-development-hero → ld-services-website-development-s01 → ld-services-website-development-s02 → ld-services-website-development-s03 → ld-services-website-development-s04 → ld-services-website-development-s05 → ld-services-website-development-creator-sites → ld-services-website-development-action ### A website with a clear job to do. Section ID: `ld-services-website-development-hero` Help visitors understand your offer and move confidently toward the action that matters to your business. ### Start with the visitor Section ID: `ld-services-website-development-s01` Launching, redesigning or untangling an existing site starts with the same question: what should a visitor understand and be able to do? We use that answer to define pages, content and journeys. ### See the plan before the build Section ID: `ld-services-website-development-s02` Review the sitemap, page purpose, proposed content and desktop/mobile designs before implementation. The proposal sets responsibilities for copy, imagery, review and approval. ### Define the delivery scope Section ID: `ld-services-website-development-s03` Agree pages, forms, integrations, migration, hosting, accessibility requirements, ownership, training and maintenance. Testing and acceptance criteria belong in the project scope; they are not replaced by a visual preview. ### Prepare the useful inputs Section ID: `ld-services-website-development-s04` Share your existing site, goals, decision-maker and approved brand assets. Tell us what must be retained or connected. Account access is requested later through an authorized process. ### After launch Section ID: `ld-services-website-development-s05` Support, hosting and ongoing changes are separate responsibilities unless included in the agreement. Scope changes receive an agreed response before additional work begins. ### Creator-branded member websites Section ID: `ld-services-website-development-creator-sites` For creator-branded member sites, the public pages and the signed-in experience need a shared plan. We can scope design and technical delivery with Novelle Veil’s creator-service team, with responsibilities and acceptance criteria agreed before implementation. ### Discuss Your Website Project Section ID: `ld-services-website-development-action` Choose the next step when you are ready. Button: **Discuss Your Website Project** → /project-brief?service=website **Editorial release dependencies (not public copy):** Creator-platform technical delivery remains proposed and separately resourced; confirm actual specialist capability, provider scope and operational acceptance. No completed client, secure production system or payment integration is implied by a concept. ## /services/app-development — Start with the user problem. Define the product around it. Page ID: `ld-services-app-development` · State: proposed SEO title: App Development | Lucent Digital SEO description: Explore an app or digital workflow through the people using it, the task they need to complete and the constraints that matter. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-services-app-development-hero → ld-services-app-development-s01 → ld-services-app-development-s02 → ld-services-app-development-s03 → ld-services-app-development-s04 → ld-services-app-development-s05 → ld-services-app-development-member-experiences → ld-services-app-development-action Mobile order: ld-services-app-development-hero → ld-services-app-development-s01 → ld-services-app-development-s02 → ld-services-app-development-s03 → ld-services-app-development-s04 → ld-services-app-development-s05 → ld-services-app-development-member-experiences → ld-services-app-development-action ### Start with the user problem. Define the product around it. Section ID: `ld-services-app-development-hero` Explore an app or digital workflow through the people using it, the task they need to complete and the constraints that matter. ### Name the task Section ID: `ld-services-app-development-s01` Describe who needs to do what, where the process becomes difficult and what a useful outcome looks like. Customer journeys and internal workflows both need a clear purpose. ### Prototype the important decisions Section ID: `ld-services-app-development-s02` Define core journeys and review key screens before committing to a delivery scope. A prototype helps test understanding; it does not prove a production integration or security control. ### Agree the product boundaries Section ID: `ld-services-app-development-s03` Devices, data, integrations, permissions, technical feasibility, ownership and support belong in the proposal. Native mobile delivery, app-store submission and specific system expertise must be confirmed for the actual project. ### Deliver in defined stages Section ID: `ld-services-app-development-s04` Requirements, prototype, scoped implementation, testing and acceptance create useful decision points. A smaller first release may be considered when it addresses the essential task. ### Protect sensitive inputs Section ID: `ld-services-app-development-s05` Start with a plain-language use case. Do not submit credentials, source code or customer datasets in the initial form. Any later transfer follows an agreed secure process. ### Member experiences with defined responsibilities Section ID: `ld-services-app-development-member-experiences` Creator and membership projects can involve accounts, content access, messaging and payment-provider connections. We start by defining the people, permissions and operating responsibilities behind those journeys. Provider approval, security testing, moderation and ongoing support are project requirements, not assumptions built into a prototype. ### Discuss Your App Project Section ID: `ld-services-app-development-action` Choose the next step when you are ready. Button: **Discuss Your App Project** → /project-brief?service=app **Editorial release dependencies (not public copy):** Creator-platform technical delivery remains proposed and separately resourced; confirm actual specialist capability, provider scope and operational acceptance. No completed client, secure production system or payment integration is implied by a concept. ## /services/digital-marketing-strategy — Decide what your marketing should do next. Page ID: `ld-services-digital-marketing-strategy` · State: proposed SEO title: Digital Marketing Strategy | Lucent Digital SEO description: Examine the offer, the customer journey and the evidence before choosing the next marketing priorities. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-services-digital-marketing-strategy-hero → ld-services-digital-marketing-strategy-s01 → ld-services-digital-marketing-strategy-s02 → ld-services-digital-marketing-strategy-s03 → ld-services-digital-marketing-strategy-s04 → ld-services-digital-marketing-strategy-s05 → ld-services-digital-marketing-strategy-action Mobile order: ld-services-digital-marketing-strategy-hero → ld-services-digital-marketing-strategy-s01 → ld-services-digital-marketing-strategy-s02 → ld-services-digital-marketing-strategy-s03 → ld-services-digital-marketing-strategy-s04 → ld-services-digital-marketing-strategy-s05 → ld-services-digital-marketing-strategy-action ### Decide what your marketing should do next. Section ID: `ld-services-digital-marketing-strategy-hero` Examine the offer, the customer journey and the evidence before choosing the next marketing priorities. ### Make the problem specific Section ID: `ld-services-digital-marketing-strategy-s01` Scattered activity, an unclear offer or a weak enquiry path needs diagnosis before more activity. Tell us what the business is trying to achieve and what evidence is available. ### Review three connected areas Section ID: `ld-services-digital-marketing-strategy-s02` We scope review of the offer and enquiry experience, creative and channel choices, and measurement readiness. The depth depends on the agreed question and access to reliable inputs. ### Leave with a usable action brief Section ID: `ld-services-digital-marketing-strategy-s03` An agreed brief can set out findings, priorities, reasons, dependencies and next steps. Sample formats illustrate the deliverable; they are not an analysis of your accounts. ### Choose channels for their role Section ID: `ld-services-digital-marketing-strategy-s04` Search, social, video and other channels should answer a defined business need. A review does not require buying a fixed channel bundle or a subsequent management engagement. ### Agree the commercial basis Section ID: `ld-services-digital-marketing-strategy-s05` Review depth, inputs, deliverable, fee and timing are agreed in advance. Recommendations depend on available evidence and cannot guarantee growth. ### Request a Marketing Review Section ID: `ld-services-digital-marketing-strategy-action` Choose the next step when you are ready. Button: **Request a Marketing Review** → /project-brief?service=strategy ## /services/marketing-management — Give ongoing marketing a clear owner and a working plan. Page ID: `ld-services-marketing-management` · State: proposed SEO title: Marketing Management | Lucent Digital SEO description: Coordinate the campaigns, content, approvals and reporting agreed for your business. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-services-marketing-management-hero → ld-services-marketing-management-s01 → ld-services-marketing-management-s02 → ld-services-marketing-management-s03 → ld-services-marketing-management-s04 → ld-services-marketing-management-s05 → ld-services-marketing-management-action Mobile order: ld-services-marketing-management-hero → ld-services-marketing-management-s01 → ld-services-marketing-management-s02 → ld-services-marketing-management-s03 → ld-services-marketing-management-s04 → ld-services-marketing-management-s05 → ld-services-marketing-management-action ### Give ongoing marketing a clear owner and a working plan. Section ID: `ld-services-marketing-management-hero` Coordinate the campaigns, content, approvals and reporting agreed for your business. ### Turn priorities into assigned work Section ID: `ld-services-marketing-management-s01` Define the channels, content, campaigns and reporting that belong in the engagement. Assign an owner for each action and the client approvals needed to move it forward. ### Know the division of responsibility Section ID: `ld-services-marketing-management-s02` Agency delivery, client approvals, sales follow-up and external production or technical dependencies must be explicit. A campaign is not complete simply because it is published. ### Review outcomes with context Section ID: `ld-services-marketing-management-s03` Distinguish enquiries, qualified opportunities, sales and channel engagement. Reporting should state the period, attribution method and what the evidence cannot establish. ### Keep the commercial pieces separate Section ID: `ld-services-marketing-management-s04` Management fees, media spend and outside production are distinct. Revisions, account access, asset handoff, cancellation and review cadence belong in the agreement. ### Begin with the current activity Section ID: `ld-services-marketing-management-s05` Tell us what is running, what is difficult and what help you need. Available delivery capacity is confirmed before a continuing scope is promised. ### Discuss Your Marketing Needs Section ID: `ld-services-marketing-management-action` Choose the next step when you are ready. Button: **Discuss Your Marketing Needs** → /project-brief?service=management ## /how-we-work — Clear scope. Useful checkpoints. Page ID: `ld-how-we-work` · State: proposed SEO title: How We Work | Lucent Digital SEO description: Understand who decides, what is delivered and how work is accepted. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-how-we-work-hero → ld-how-we-work-s01 → ld-how-we-work-s02 → ld-how-we-work-s03 → ld-how-we-work-s04 → ld-how-we-work-action Mobile order: ld-how-we-work-hero → ld-how-we-work-s01 → ld-how-we-work-s02 → ld-how-we-work-s03 → ld-how-we-work-s04 → ld-how-we-work-action ### Clear scope. Useful checkpoints. Section ID: `ld-how-we-work-hero` Understand who decides, what is delivered and how work is accepted. ### Brief Section ID: `ld-how-we-work-s01` Describe the problem, audience, desired outcome and constraints. We clarify the inputs needed to assess fit. ### Proposal Section ID: `ld-how-we-work-s02` Review the agreed deliverables, responsibilities, fee basis, schedule, exclusions and acceptance criteria. Discovery may be a separately scoped engagement. ### Review Section ID: `ld-how-we-work-s03` Use defined checkpoints to check the work against the brief. Changes to scope or assumptions need agreement rather than disappearing into an open-ended task list. ### Acceptance and handoff Section ID: `ld-how-we-work-s04` Review the agreed tests and deliverables, then confirm ownership, access and next-step responsibilities. Continuing support is included only where stated. ### Discuss Your Project Section ID: `ld-how-we-work-action` Choose the next step when you are ready. Button: **Discuss Your Project** → /project-brief ## /who-we-help — Different businesses. Specific problems to solve. Page ID: `ld-who-we-help` · State: proposed SEO title: Who We Help | Lucent Digital SEO description: Start with the situation your business is facing. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-who-we-help-hero → ld-who-we-help-s01 → ld-who-we-help-s02 → ld-who-we-help-s03 → ld-who-we-help-s04 → ld-who-we-help-action Mobile order: ld-who-we-help-hero → ld-who-we-help-s01 → ld-who-we-help-s02 → ld-who-we-help-s03 → ld-who-we-help-s04 → ld-who-we-help-action ### Different businesses. Specific problems to solve. Section ID: `ld-who-we-help-hero` Start with the situation your business is facing. ### Our website no longer explains the business Section ID: `ld-who-we-help-s01` A clearer offer, content structure and visitor journey may be the starting point. Explore Website Development. ### A manual process frustrates customers or staff Section ID: `ld-who-we-help-s02` Define the task, users and existing systems before choosing an app. Explore App Development. ### Marketing priorities are unclear Section ID: `ld-who-we-help-s03` Review the offer, enquiry experience and evidence before choosing further activity. Explore Marketing Strategy. ### Execution needs coordination Section ID: `ld-who-we-help-s04` Agree the recurring work, approvals, reporting and follow-up ownership. Explore Marketing Management. ### Find My Starting Point Section ID: `ld-who-we-help-action` Choose the next step when you are ready. Button: **Find My Starting Point** → /project-brief?service=help-choosing ## /about — Creativity with a clear purpose. Page ID: `ld-about` · State: proposed SEO title: About | Lucent Digital SEO description: Lucent Digital connects digital experiences and marketing work through a defined business brief. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-about-hero → ld-about-s01 → ld-about-s02 → ld-about-s03 → ld-about-action Mobile order: ld-about-hero → ld-about-s01 → ld-about-s02 → ld-about-s03 → ld-about-action ### Creativity with a clear purpose. Section ID: `ld-about-hero` Lucent Digital connects digital experiences and marketing work through a defined business brief. ### The work comes before the format Section ID: `ld-about-s01` A new website, app or campaign is useful when it helps the right people complete a meaningful task. We begin by defining that task and how the work will be assessed. ### Accountability in the scope Section ID: `ld-about-s02` Each engagement identifies the responsible delivery roles, client decisions and specialist input required. A role description is not a claim about permanent team size. ### Clarity at the handoff Section ID: `ld-about-s03` Ownership, access and continuing responsibilities should be understandable when work is accepted. See the process before discussing your project. ### Explore How We Work Section ID: `ld-about-action` Choose the next step when you are ready. Button: **Explore How We Work** → /how-we-work **Editorial release dependencies (not public copy):** Verify operating-company disclosure, actual delivery capabilities and named biographies. ## /work — The work, the context and the decisions. Page ID: `ld-work` · State: conditional-template SEO title: Work | Lucent Digital SEO description: Explore documented projects with the situation, agreed scope and supported outcome made clear. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-work-hero → ld-work-s01 → ld-work-s02 → ld-work-action Mobile order: ld-work-hero → ld-work-s01 → ld-work-s02 → ld-work-action ### The work, the context and the decisions. Section ID: `ld-work-hero` Explore documented projects with the situation, agreed scope and supported outcome made clear. ### Project stories Section ID: `ld-work-s01` NONPUBLISHABLE: insert only permissioned real projects, identifying client or internal status, Lucent role, dates, deliverables and defensible outcomes. Until at least one approved example exists, omit this route and Work navigation; link How We Work instead. ### Results in context Section ID: `ld-work-s02` Each published result must state the period and basis. A concept illustrates an approach; it is not a client outcome or a promise of similar results. ### Discuss a Similar Project Section ID: `ld-work-action` Choose the next step when you are ready. Button: **Discuss a Similar Project** → /project-brief **Editorial release dependencies (not public copy):** Approved project proof and publication permission. ## /faqs — Before you brief a project. Page ID: `ld-faqs` · State: proposed SEO title: FAQs | Lucent Digital SEO description: Understand the first enquiry, pricing and delivery responsibilities. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-faqs-hero → ld-faqs-s01 → ld-faqs-s02 → ld-faqs-s03 → ld-faqs-s04 → ld-faqs-s05 → ld-faqs-s06 → ld-faqs-action Mobile order: ld-faqs-hero → ld-faqs-s01 → ld-faqs-s02 → ld-faqs-s03 → ld-faqs-s04 → ld-faqs-s05 → ld-faqs-s06 → ld-faqs-action ### Before you brief a project. Section ID: `ld-faqs-hero` Understand the first enquiry, pricing and delivery responsibilities. ### What if I do not know which service I need? Section ID: `ld-faqs-s01` Choose Help me choose and describe the problem. The initial review clarifies the next step; it does not commit you to a project. ### Is discovery free? Section ID: `ld-faqs-s02` Discovery or a marketing review may be a separately scoped paid engagement. Scope and fee are agreed before work begins. ### How is pricing decided? Section ID: `ld-faqs-s03` The proposal reflects the agreed deliverables, complexity, inputs and responsibilities. Media spend and outside production are distinct from management fees. ### Are hosting and support included? Section ID: `ld-faqs-s04` Only when the agreement includes them. Ownership, hosting, maintenance, updates and continuing support need explicit responsibilities. ### Do I need to send passwords? Section ID: `ld-faqs-s05` No. The initial brief needs no credentials or private files. Later access follows an agreed authorized process. ### Can you guarantee results or a launch date? Section ID: `ld-faqs-s06` Outcomes and timing depend on scope, evidence, approvals and delivery conditions. A submitted brief does not reserve a date or guarantee business growth. ### Discuss Your Project Section ID: `ld-faqs-action` Choose the next step when you are ready. Button: **Discuss Your Project** → /project-brief ## /project-brief — What needs to work better? Page ID: `ld-project-brief` · State: proposed SEO title: Project Brief | Lucent Digital SEO description: Tell us the business problem, who it affects and the outcome you want. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-project-brief-hero → ld-project-brief-s01 → ld-project-brief-s02 → ld-project-brief-s03 → ld-project-brief-action Mobile order: ld-project-brief-hero → ld-project-brief-s01 → ld-project-brief-s02 → ld-project-brief-s03 → ld-project-brief-action ### What needs to work better? Section ID: `ld-project-brief-hero` Tell us the business problem, who it affects and the outcome you want. ### Choose your starting point Section ID: `ld-project-brief-s01` Website development, app development, marketing strategy, marketing management or help choosing. You can explain overlapping needs in the message. ### Share the essentials Section ID: `ld-project-brief-s02` Include your name, contact email, business and a short description. A public website, desired timing and phone contact are optional. No password or private customer file is needed. Website enquiries require the current-site situation and main visitor action. App enquiries require the users and main task. Strategy enquiries require the priority challenge. Management enquiries require the support needed. Help me choose does not require one of these service-specific branches. ### What happens next Section ID: `ld-project-brief-s03` The brief is reviewed for fit and routed to the appropriate delivery lead. Any discovery, proposal or project agreement follows separately. ### Send My Project Brief Section ID: `ld-project-brief-action` Choose the next step when you are ready. Button: **Send My Project Brief** → form:ld-project ## /privacy — How enquiry information is handled. Page ID: `ld-privacy` · State: conditional-template SEO title: Privacy Notice Template | Lucent Digital SEO description: [NONPUBLISHABLE: replace this draft with a reviewed notice matching the actual data practices before collecting enquiries.] Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-privacy-hero → ld-privacy-s01 → ld-privacy-s02 → ld-privacy-s03 → ld-privacy-s04 → ld-privacy-s05 → ld-privacy-action Mobile order: ld-privacy-hero → ld-privacy-s01 → ld-privacy-s02 → ld-privacy-s03 → ld-privacy-s04 → ld-privacy-s05 → ld-privacy-action ### How enquiry information is handled. Section ID: `ld-privacy-hero` [NONPUBLISHABLE: replace this draft with a reviewed notice matching the actual data practices before collecting enquiries.] ### Who is responsible Section ID: `ld-privacy-s01` [NONPUBLISHABLE: verified controller/operator identity and privacy contact.] ### What is collected and why Section ID: `ld-privacy-s02` [NONPUBLISHABLE: actual fields collected, enquiry purposes, applicable processing basis, optional marketing treatment and any sensitive-data exclusions.] ### Access, providers and transfers Section ID: `ld-privacy-s03` [NONPUBLISHABLE: actual recipients, systems/processors, access controls and relevant cross-border handling. No invented claim that data never leaves a country or is never shared.] ### Retention and choices Section ID: `ld-privacy-s04` [NONPUBLISHABLE: actual retention/deletion approach, applicable rights and request procedure. No promised deletion period without an implemented policy.] ### Cookies and measurement Section ID: `ld-privacy-s05` [NONPUBLISHABLE: actual necessary/optional technologies, consent choices where applicable, analytics recipients and withdrawal process. Do not claim live tracking from the design.] ### Discuss Your Project Section ID: `ld-privacy-action` Choose the next step when you are ready. Button: **Discuss Your Project** → /project-brief **Editorial release dependencies (not public copy):** Actual operator, jurisdiction/practices and appropriate review. No enquiry collection before adequate notice. ## /terms — Using this website and requesting information. Page ID: `ld-terms` · State: conditional-template SEO title: Website Terms Template | Lucent Digital SEO description: An enquiry starts a review. It does not create a booking, purchase, service agreement or accepted application. Readable hero followed by ordered content and one primary action. Desktop may pair image and text; mobile places meaning and action before image, then stacks sections without changing order. Desktop order: ld-terms-hero → ld-terms-s01 → ld-terms-s02 → ld-terms-s03 → ld-terms-action Mobile order: ld-terms-hero → ld-terms-s01 → ld-terms-s02 → ld-terms-s03 → ld-terms-action ### Using this website and requesting information. Section ID: `ld-terms-hero` An enquiry starts a review. It does not create a booking, purchase, service agreement or accepted application. ### Information and enquiries Section ID: `ld-terms-s01` Read the relevant service or vehicle information and ask about material details. A form receipt confirms only that the message has been received. ### Separate commercial agreement Section ID: `ld-terms-s02` Any actual engagement, service, appointment or transaction follows the applicable written terms and confirmation process. No unapproved commercial promise is created by this draft. ### Operator and applicable terms Section ID: `ld-terms-s03` [NONPUBLISHABLE: insert verified operator, website-use terms, jurisdiction, rights/contact provisions and links to adopted commercial terms after appropriate review.] ### Discuss Your Project Section ID: `ld-terms-action` Choose the next step when you are ready. Button: **Discuss Your Project** → /project-brief **Editorial release dependencies (not public copy):** Verified operator and adopted website/commercial terms. ## Form copy and states ### ld-project CRM form ID: `lu_project_brief`. | Field ID | Label | Requirement | Help text | Invalid-state copy | |---|---|---|---|---| | payload.contact.name | Your name | Required | Use the name you would like us to use. | Complete your name. | | payload.contact.email | Email | Required | Use a contact address for this request. Required for this form even if Phone is selected as the preferred reply method. | Enter a valid email address. | | payload.contact.phone | Phone with country code | Conditional | Enter +, the country code and phone number without spaces. | Enter a valid international phone number beginning with + and the country code. | | payload.contact.preferred_channel | Preferred reply method | Required | Choose Email or Phone from the channels offered. Phone requires a phone number; email requires an email address. | Complete preferred reply method. | | payload.contact.marketing_email_opt_in | Optional email updates | Optional | Optional Lucent Digital updates by email. This choice is separate from handling your enquiry. | Enter a valid optional email updates or leave blank when optional. | | payload.contact.marketing_sms_opt_in | Optional text-message updates | Optional | Optional Lucent Digital updates by text message. This choice is separate from handling your enquiry. | Enter a valid optional text-message updates or leave blank when optional. | | payload.business_name | Business or trading name | Required | Use the business or project name. If preparing to launch, state that plainly. | Complete business or trading name. | | payload.service_interest | Service interest | Required | Choose a service or Help me choose. Additional questions follow the selected service. | Complete service interest. | | payload.desired_outcome | Problem and desired outcome | Required | Who is affected and what should improve? No confidential records or credentials. | Complete problem and desired outcome. | | payload.public_business_url | Public business website | Optional | A public URL only; no private links or credentials. | Enter a valid public business website or leave blank when optional. | | payload.timing | Desired timing | Optional | A preference; availability and next steps are confirmed separately. Not sure yet is acceptable. | Enter a valid desired timing or leave blank when optional. | | payload.website_status | Current website situation | Conditional | Required for website projects. Describe whether this is a new site, redesign or other change. | Enter a valid current website situation or leave blank when optional. | | payload.website_primary_action | Main visitor action | Conditional | Required for website projects. What should a visitor be able to do? | Enter a valid main visitor action or leave blank when optional. | | payload.app_users_task | App users and main task | Conditional | Required for app projects. Who uses the app and what do they need to accomplish? | Enter a valid app users and main task or leave blank when optional. | | payload.app_system_context | Existing system context | Optional | Optional. Describe relevant systems at a high level; no access keys, source code or customer data. | Enter a valid existing system context or leave blank when optional. | | payload.strategy_challenge | Marketing strategy question | Conditional | Required for strategy enquiries. Describe the priority decision or challenge. | Enter a valid marketing strategy question or leave blank when optional. | | payload.management_support | Marketing support needed | Conditional | Required for management enquiries. Describe current activity and the help you want. | Enter a valid marketing support needed or leave blank when optional. | #### Conditional rules and allowed values - `payload.contact.email` required when: [{"properties": {"preferred_channel": {"const": "email"}}}]. - `payload.contact.phone` required when: [{"properties": {"preferred_channel": {"const": "phone"}}}]. - `payload.contact.preferred_channel` choices: Email (`email`); Phone (`phone`). - `payload.service_interest` choices: Website development (`website_development`); App development (`app_development`); Marketing strategy (`marketing_strategy`); Marketing management (`marketing_management`); Help me choose (`help_me_choose`). - `payload.website_status` required when: [{"properties": {"service_interest": {"const": "website_development"}}}]. - `payload.website_primary_action` required when: [{"properties": {"service_interest": {"const": "website_development"}}}]. - `payload.app_users_task` required when: [{"properties": {"service_interest": {"const": "app_development"}}}]. - `payload.strategy_challenge` required when: [{"properties": {"service_interest": {"const": "marketing_strategy"}}}]. - `payload.management_support` required when: [{"properties": {"service_interest": {"const": "marketing_management"}}}]. Submit: **Send My Project Brief** Pending: Sending your request. Please keep this page open. Invalid summary: Please correct the fields listed below. Your request has not been sent. Transmission failure: Your request was not sent. Please try again. If the problem continues, use the verified contact option shown here. Duplicate/uncertain receipt: A matching request may already have been received. Check your confirmation before sending again. Successful durable receipt: Your brief has been received. We will review the information and contact you about the next step. A submitted brief does not create a project agreement or reserve a delivery date. Editorial follow-up owner: SH04 intake; LU01 qualifies scope and reserves paid delivery and independent QA. Show receipt only after a durable accepted record. Never invent a reference number. Link error summary to fields, preserve safe entries on back/retry, announce status to assistive technology. No prechecked marketing consent. Verified alternative contact must replace the internal slot before release. Field IDs and constraints match the cited proposed CRM contract. System metadata is not collected from the customer. Enquiry consent is separate from optional marketing choices; only supported contact channels may be displayed. Editorial marketing control: initialize both opt-in fields unchecked. Show a channel-specific option only after the actual brand purpose, channel terms, consent recording and working unsubscribe/preference route are adopted and tested. Add the verified preference instructions beside the optional control before release; do not publish an invented link or the editorial release instructions as customer copy. No choice is required for service follow-up. ## Shared interface copy **Skip Link:** Skip to main content **Menu Open:** Open menu **Menu Close:** Close menu **Required Note:** Fields marked Required must be completed. **Back:** Back **Review:** Review your request **Submit Pending:** Sending… **Not Found Heading:** This page is not available. **Not Found Body:** The address may have changed. Return to the homepage or use the navigation to find the relevant service. **Not Found Action:** Return home **Contact Fallback:** [NONPUBLISHABLE: insert verified monitored contact alternative; do not display a fake address or number.] **Privacy Helper:** Read the privacy notice to understand how your enquiry information is handled. **Marketing Opt In:** Optional: send me relevant updates. I can unsubscribe. **Marketing Status:** Do not display until actual purpose, channel, consent recording and unsubscribe process are adopted. Leave unchecked. ## Conditional route decisions ## Readiness boundary Narrative copy is proposed for review, not proof of delivery capability. Conditional templates retain missing factual or legal inputs. No NONPUBLISHABLE slot may release. Visual review, operating approval, actual form delivery and publication are separate. No implementation or canonical completion is claimed.