APEX / THE KITOpen the website ↗

FROM BRIEF TO HANDOFF

Make the plan.
Make it theirs.

The Apex kit is for builders comfortable with HTML and CSS. No framework installation is required. This local prototype is for private evaluation. Commercial use, paid checkout and a distribution channel are not active.

1. Start with the real business

Use the detailing content workbook to gather services, actual prices, coverage, vehicle condition, materials, utilities, access and cancellation terms. The included Apex business is fictional. Do not invent customer reviews, insurance claims or professional certifications.

First time? Try the sample customization exercise.

2. Prepare the website settings

Open the setup form. Update the business details, three service scopes, preparation notes, FAQs and image information. Leave starting prices empty for estimate-only work. Download site-config.js and replace that file in a copy of the kit’s website folder.

Continue later: use “Reopen your saved settings” in the setup form. Choose a settings file previously downloaded from that form, review the business name and choose “Use these settings.” This replaces the form entries only after you choose to apply it. Download unsaved work first. The file stays on your device and preview mode remains enabled. Handwritten JavaScript is not supported by the importer.

Entries are not sent or saved automatically. Download before leaving the form. The settings file is public: do not include customer records, passwords, alarm codes or entry instructions.

Install the file you just saved

After requesting a settings download, check that the file was saved, then choose I saved these settings in setup. A canceled download keeps the unsaved-work warning. In the handoff builder, save the editable JSON draft and choose I saved this editable draft; a client document or copied message cannot reopen your editing session. Confirmation records your choice; reopen each file to verify it.

  1. Keep the original extracted kit and work in a copy. Locate the newest settings download and reopen it in this kit’s setup form to check the business name before applying it.
  2. A browser may save another copy as site-config (1).js. In the working website/ folder, replace the original file and name the replacement exactly site-config.js, beside index.html and services.html. Do not leave an added number or .txt extension.
  3. Open the homepage and services page from that same working folder. Refresh each page and confirm the business name, one changed service and its price or estimate label. Opening the store’s demo will still show the example business.
  4. If the old details remain, check the folder and filename first, then reopen the saved settings to confirm you chose the latest file. Keep contact actions disabled during evaluation. Reopening a file in setup does not install it in the website.

3. Review the design and content

Open both website/index.html and website/services.html. The shared settings fill in business details, packages, preparation information and FAQs. Each service has an editable “Service navigation label” label in the setup form. Give it wording that matches the service; the label and service stay linked when you export and reopen settings. Other fixed copy remains in the HTML and should be reviewed for the actual business.

Edit colors in the opening variables of website/style.css. Replace remaining fictional details, page metadata and fixed homepage statements with accurate client content. Search the website folder for Apex and Denver before a real launch.

The original generated example image is not a client vehicle or detailing result. Retain its disclosure during evaluation. For a real portfolio, obtain authorized photography, place it in website/assets, then set the image path, alternative text and caption in the setup form.

4. Choose the inquiry destination

In a configured website with demo mode off, service links open the chosen public inquiry page or call the valid business number when no online destination is available. Texting appears only when enabled. Online links show the destination’s domain so customers can see where they will continue. Confirm the exact business and number before launch; these labels do not verify the destination or complete a booking.

Use the client’s existing public HTTPS inquiry or booking page, their public Korvo intake form, or calls and texts. Korvo requires a separate workspace. The kit does not provide a booking system, payment processing, CRM synchronization or automatic follow-up.

Leave demo mode enabled for evaluation. After commercial-use approval and actual client checks, set demoMode to false in the installed settings. Verify the destination belongs to the correct business and that an authorized test request reaches its intended recipient. A request is not a confirmed appointment.

5. Check and hand over

Check both pages on a phone and a larger screen, with enlarged text and keyboard navigation. Confirm service selection opens the correct service section, prices and exclusions are accurate, and contact actions behave correctly for the agreed destination.

Use the client handoff builder to record account ownership, inquiry delivery proof, support terms and outstanding work. Its checkboxes record your own assessment; they do not run tests. Download the handoff document before closing.

6. Publish the website files when ready

Hosting and domains are separate. Publish only the contents of the website folder to the client’s chosen static hosting service, preserving paths. The guide and handoff tools are not the client’s public website. Configure final metadata, policies and agreed support details before publication.

Keep an editable handoff draft

In the client handoff builder, choose Save editable draft to keep a .json file of your project notes and recorded checks. Return to the same kit’s handoff builder, choose that file, review its project name and choose Use this draft. Nothing replaces your entries until you apply it. Save current work before applying another draft.

The editable draft is separate from Download handoff document, which prepares the readable client document. Neither file sends a message, runs a check or establishes client approval. Saved checkboxes are previous notes to review, not fresh verification. Keep passwords, access codes and private client records out of both files.

Keep your current edits

If setup cannot prepare a download, the summary at the top of the form lists the details to fix. Choose a link to focus the matching field. Correct its value and try the download again; your other entries stay in place. Optional prices can remain blank for estimate-only work. Zero is a real price, not a placeholder.

Setup and handoff show when changes have not been included in a new download. Download your settings or editable handoff draft before leaving. A download request cannot confirm that your device saved the file; check your downloads before closing.

Reopening a saved file sets the starting point for new edits. If you change the form while another file is being read or waiting to apply, choose that file again to replace the newer entries. This prevents an older pending import from overwriting work unexpectedly.

These tools open as standalone pages. Your browser may warn before leaving a page with unsaved edits; its wording and availability depend on the browser. Stay on the page until your current settings or editable draft are saved and reopened. Do not rely on a warning on every device. Nothing is saved automatically.

The readable client handoff document does not contain a reopenable draft. Use Save editable draft to keep editing later.

Review your content in the design

After installing your downloaded settings, review the actual client version of both pages. A beautiful demo is only the starting point.

Keep a copy of your last working settings before revising. Review fixed page copy separately: changing a service name in settings does not rewrite every mention in descriptions, inclusions or the surrounding page text.

Review, save and verify your settings

At the end of setup, choose Review all settings to read the business details, full service scopes, inquiry destination, FAQs and image information together. Use an Edit button to return to the matching part of the form. Changing or reopening settings clears the old review so you do not mistake it for the latest version.

The summary is a content check, not a live website preview or confirmation that the business facts are correct. Contact actions remain disabled during evaluation. Your image file is separate from the settings.

Choose Download my settings, then check your downloads for site-config.js. Keep a backup of your working file and replace that exact file inside the kit’s website folder. Open both website pages to verify the new business name, service scope and intended image. A download request does not install the settings or publish the website.

If a download cannot start: your entries stay on the page and remain marked as unsaved. Try again, or choose Show settings text. Copy all the text into a plain-text editor and save as site-config.js, without an added .txt extension. Do not use a rich-text document. Reopen that file in the matching setup form to confirm it can be read before replacing your working copy. Showing or copying text does not confirm it was saved.

When you change any field after preparing a text backup, prepare fresh text before saving again. Keep the page open until you have checked the saved file.

Keep the handoff files distinct

The client handoff now identifies blank project details and links back to their fields. Unticked checks remain manual work to complete; filling a field does not verify a business fact or approve publication.

If a download cannot start, keep the page open and retry. Select document text provides the readable document; Show editable draft text provides the complete JSON draft. Save all the selected text in a plain-text editor with the displayed filename and no extra .txt extension. Reopen a saved draft to verify it. Showing or copying text never confirms a successful save. Editing or importing another draft clears old backup text.

If the settings file cannot load

The website and setup page show recovery instructions when site-config.js is missing, broken, from another kit or has unreadable required data. Keep your edited file before replacing anything. Restore site-config.js from the original copy of this same kit into the working website folder, then reload. This restores the example; it does not recover unsaved edits. Reopen your latest valid settings export in setup and review it before installing it. If your edited file is your only copy, preserve it and repair it in a text editor.

The recovery screen does not modify or upload files. Its retry button only reloads the page. If the browser reports an unsaved-work warning elsewhere, keep that page open until you have saved your work.