Créez un site web de cabinet d'avocats qui clarifie votre travail et la prochaine étape

Build a mobile-first informational website for my law firm and a protected owner inbox for initial consultation requests. Make the first version polished and useful while keeping the workflow narrow, factual and easy for a lawyer to review. Do not treat generated text or code as evidence of regulatory compliance, confidentiality or production readiness.

MY FIRM DETAILS — REPLACE THE BRACKETS WITH REAL, APPROVED FACTS
- Public firm name and legal entity: [DETAILS]
- Country, state/province, city, site language, currency and time zone: [DETAILS]
- Regulator, bar or licensing body and jurisdiction: [DETAILS]
- Registration or authorisation facts that may or must be shown: [VERIFIED DETAILS / NONE SUPPLIED]
- Exact lawyer-reviewed advertising, regulatory and complaints wording and links: [TEXT / NOT YET SUPPLIED]
- Who we help and where we may act: [REAL CLIENT TYPES AND GEOGRAPHIC OR JURISDICTIONAL SCOPE]
- Practice areas and service boundaries: [ONLY WORK THE FIRM ACTUALLY OFFERS]
- Professionals: [REAL NAME, ROLE, VERIFIED ADMISSIONS, LANGUAGES, ACTUAL PRACTICE AREAS AND APPROVED BIO; ONE LINE PER PERSON]
- Firm approach: [FACTUAL, SUPPORTABLE POINTS ABOUT HOW WE WORK]
- Location and accessibility: [REAL PUBLIC ADDRESS OR SERVICE AREA / REMOTE OR IN-PERSON ARRANGEMENTS / ACCESS DETAILS]
- Contact and hours: [PHONE / EMAIL / ACTUAL HOURS / AFTER-HOURS INSTRUCTIONS IF ANY]
- Initial consultation: [REQUEST ONLY / REAL FEE OR NO FEE / FORMAT / DURATION / REAL RESPONSE EXPECTATION]
- Fees and service transparency: [EXACT REVIEWED PRICES OR RANGES AND REQUIRED BASIS, TAX, DISBURSEMENTS, INCLUSIONS, EXCLUSIONS, STAGES AND TIMESCALES / OMIT]
- Proof: [REAL, VERIFIABLE, PERMITTED AND APPROVED TESTIMONIALS, MATTERS, RESULTS, RANKINGS OR AWARDS / NONE]
- Privacy: [LAWYER-REVIEWED NOTICE / RETENTION PERIOD / PRIVACY CONTACT / NOT YET SUPPLIED]
- Brand direction: [ACTUAL COLOURS, WORDMARK AND FEEL / USE THE DEFAULT BELOW]
- Approved real media attached, if any: [LOGO / ATTORNEY PHOTOS / TEAM OR PREMISES PHOTOS WITH PLACEMENTS AND PERMISSION / NONE]

FIRST-BUILD SCOPE
Build Home, Practice Areas, About or Professionals, What to Expect and Contact. Add one protected owner screen for reviewing requests and editing approved public details. Do not add a client portal, document upload, payments, fee calculator, custom calendar, legal chatbot, automated legal answers, blog, newsletter or case-management system in this first version. Do not publish a regulatory, complaints, privacy, terms or legal-notice page without the exact reviewed content it requires. Keep missing launch requirements on a private owner checklist, with no dead public link.

MEDIA AND DESIGN
Use only the approved images I attach. Improving crop, lighting, colour or sharpness of my real photos is fine; do not generate from scratch or invent lawyers, staff, clients, offices, work or results. Do not fetch unrelated stock images and present them as my firm. If I supply no media, make the site look complete with typography, spacing, colour, fine rules and restrained abstract geometry. Render no empty photo frames, generic headshots, testimonial placeholders or oversized blank image cards. Keep optional media fields empty and hidden until I upload approved assets; report where a logo, professional portrait and premises photo could go later.

Use a calm, readable editorial style. If I gave no brand direction, start with warm off-white, near-black and one muted accent, a readable serif for headings and a clean sans-serif for body. Avoid gavels, scales, courthouse columns, handshakes, flags and badges as generic decoration. At 320px, no firm name, heading, notice, navigation or action may clip or create horizontal scrolling.

PUBLIC CONTENT
Home: identify who the firm helps, the actual practice areas, location or service area and a clear “Request an initial consultation” action. Do not imply acceptance, a free consultation, guaranteed availability or response time unless my facts support it.
Practice Areas: explain only the supplied work in plain language. Do not invent legal rules, deadlines, eligibility tests, strategies, likely outcomes or personalised advice.
About or Professionals: use only supplied people and approved bios. Do not infer seniority, specialist status, admissions, memberships, years of experience or credentials. Hide unsupplied portrait fields without layout gaps.
What to Expect: describe the firm's supplied initial process, including human review, any conflict or suitability check by the firm, possible follow-up and written engagement if accepted. A request is not acceptance and does not create a lawyer-client relationship.
Contact: show only supplied location or service area, contact methods, hours and request route. Make click-to-call and directions links only for real, working details. All consultation actions go to /contact#request. Direct loading of that hash and clicking from Home must bring the request heading and first field into view below any header, with sensible keyboard focus.

Keep every public claim factual, sober and supportable. Do not invent testimonials, ratings, case studies, settlements, success rates, client counts, awards or “as seen in” marks. Hide proof sections when no approved proof exists. Do not use fear, urgency or unsupported “best,” “leading,” “expert” or “specialist” language. Publish fee information only from my exact reviewed inputs and with any context my jurisdiction requires. Do not invent universal “Attorney Advertising” or regulator wording.

INITIAL CONSULTATION REQUEST
Use a request form, not a live calendar. Collect only full name; exactly one contact value, email or phone; preferred contact method; a broad practice-area category from my supplied list; and an optional preferred contact window. No matter-description box, opposing-party names, case numbers, deadlines, documents, financial or health information, evidence or file uploads.

Show this draft notice just before submission and flag it for local lawyer review: “Do not send confidential, sensitive or time-critical information through this form. Sending a request does not create a lawyer-client relationship, and the firm has not agreed to act unless it confirms this in writing.” Do not claim this notice alone solves every professional-responsibility question.

If I have not supplied a reviewed privacy notice covering this form's actual data handling, keep public submission inactive and clearly mark the form as a preview until the notice and storage decisions are supplied; do not silently accept real enquiries. Once it is enabled, validate locally and on the server; add basic spam protection and duplicate handling. Save a valid request exactly once as Pending before saying it was received. The success message must not promise that the firm will act. Use a response expectation only if I supplied one. Store requests in the protected owner inbox. Keep saving and notification as separate statuses. Do not send email or text unless a supported provider, sender, destination and required plan or domain are actually configured. A failed or missing notification must not discard a saved request or falsely claim delivery.

OWNER ACCESS
Use supported authentication and server-side authorisation. Only approved owner/admin accounts may read or change requests or public details. Register and test the login route actually used by this builder: signed-out /owner must reach a working sign-in screen and return to /owner after sign-in; an unrelated signed-in user must be denied. A client-side guard or hidden link is not sufficient. Do not create demo credentials. Show Pending, Reviewed and Closed requests, limited contact details, practice-area category, timestamps and notification status. Do not add free-text case notes or automate conflict, urgency, merit, eligibility or acceptance decisions. Keep the owner interface in English.

LEGAL, PRIVACY, SEO AND ACCESSIBILITY
Use only the exact reviewed regulator, registration, complaints, advertising and privacy details I supply. If missing, put them on the private launch checklist and omit the corresponding public page or claim. Before real submissions go live, require a privacy notice matching actual fields, storage, retention, providers, notifications and analytics. Do not enable marketing enrolment, analytics or ad pixels unless I ask and configure them.

Give each public route a distinct title, description and canonical based on supplied facts; never leave builder-default metadata. Add business structured data only from verified facts. Use one H1 per page, descriptive links, labelled fields, useful errors, visible focus, keyboard access and strong contrast. Do not invent location pages or promise search rankings.

HANDOFF AND TESTS
Before calling this ready, check every route on a 320px phone and desktop; verify there are no clipped headings, empty image gaps, dead links, invented facts or default metadata. If the form is preview-only because privacy details are missing, exercise valid and invalid sample interactions and confirm zero writes or notifications. If real submission is enabled, exercise valid, invalid, bot-like and duplicate requests; confirm one saved Pending record before success and honest notification status. Test signed-out, authorised-owner and unrelated-user access in a browser, including the actual /owner sign-in and return flow. If a check cannot run, mark it UNTESTED rather than inferring a pass from code. Report required professional review, missing business facts, external accounts, plan/domain requirements, likely service costs, and where approved real images can be added later.