FRONK OIL WEBSITE CONCEPT — JESSE BY DESIGN

This is an interactive reference site, not a native Bitrix24 template export.

Pages: Home, service overview, four service details, industry overview,
five industry details, About, Customer Resources, Contact/Quote, presentation guide, and four online applications.

BITRIX24 ADAPTATION
1. Verify cloud/on-premise version, subscription, and website editor permissions.
2. Build native menu, cover, text, card-grid, FAQ, contact, and footer blocks.
3. Copy approved copy and images, keeping existing URLs or setting redirects.
4. Apply colors and font settings; adapt site CSS to actual block IDs/classes.
   Do not paste this global stylesheet unchanged over the existing site.
5. Replace the local demonstration form with a native Bitrix24 CRM form.
6. Verify actual customer portal, document links, CRM routing, consents, mobile
   layout, keyboard access, and quote submission end to end before launch.
7. Confirm image reuse rights, service information, contact details, and coverage.

HTML sections and CSS are references, not guaranteed native-editable blocks.
Custom HTML/JS, fonts, and CSS availability must be checked in the real account.
This prototype requires no framework, backend, database, or custom API.
The four application forms fill original PDFs in the browser, preview and download
unsigned demo copies, and demonstrate proposed department routing. No details
are sent to Bitrix24, stored, or emailed. Sensitive fields are fixed placeholders.
The /resources/ hub includes the customer portal, four applications, original
PDFs, tax references, the tank calculator, and FAQs. /forms/ redirects there;
/forms/<type>/ applications retain their addresses. One Customer Resources
button appears in the fixed header. Its measured height reserves page space;
the mobile menu scrolls within the viewport and anchor jumps clear the header.
See forms-assets/sources.json for original document provenance and
forms-assets/applications.json for editable field-to-PDF mappings.
PAPER APPLICATION IMPORT
Each Original Document panel accepts a completed sample/redacted PDF or up to
three page photos (JPG/PNG/WebP), 15 MB total. PDF.js 5.6.205 and Tesseract.js 7.0.0
are vendored locally with workers, English data, and licenses. Scans stay in
browser memory, never reach a server, and clear when the import window closes.
Selected reviewed answers remain in the open web form until leaving or editing.
Known-template regions isolate editable answer fields; source titles are checked.
The customer reviews/edits every selected answer and confirms accuracy before
applying it to the web form. Existing unselected values and locked sensitive
fields remain unchanged. Checkbox choices require manual customer confirmation.
Printed entries work best; handwriting needs correction. Production must evaluate
a handwriting-capable recognizer with protected uploads and source-record retention.
See forms-assets/import-regions.json for top-left Letter-page OCR regions.

Production requires native CRM forms or a secure integration, document generation,
approved signatures, protected attachments, verified recipients and department
rules, payment-provider tokenization, and end-to-end delivery testing.
Do not collect or email live card numbers or CVV through ordinary CRM fields.
External links open existing Fronk customer tools. These are not rebuilt.
The original Fronk Oil logo is retained. All photos are original Pexels stock
photographs. See photo-sources.json for photographer, source, and license records.
No AI-generated media is permitted in this project.
Fonts use Google Fonts with system fallbacks.

Official references:
https://helpdesk.bitrix24.com/open/8745423/
https://helpdesk.bitrix24.com/open/21883080/

Form workflow references:
https://helpdesk.bitrix24.com/open/25885167/
https://helpdesk.bitrix24.com/open/24369266/

COMPATIBILITY AUDIT — OCTOBER 7, 2026
Confirmed reusable asset formats: six industry JPEGs, original JPEG logo,
four original PDF downloads, and the added PNG favicon. Font/layout/header
code must be adapted and scoped to native blocks; current CSS is global.
Native CRM form design uses supported Design controls; arbitrary CSS/JS
form styling is not supported. Reviewed values can use the documented
CRM form setValues API after field mapping. Native file upload does not
establish OCR. Scan extraction/customer review and exact original-PDF
overlay generation remain custom integrations requiring resource-hosting,
worker/module/WebAssembly/security-policy and account-plan validation.
Native document templates must be DOCX, <=2 MB, with CRM field codes.
The importer supports matching Fronk PDF/JPG/PNG/WebP applications, not
DOC/DOCX or arbitrary resume/document extraction. Live department routing,
email/document delivery, secure payment capture and signatures are not
connected in this demonstration. Fronk’s account has not been tested.
See /implementation/#bitrix-compatibility for source-backed audit details.
