Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/juanmatz/inspection-form-euroautos/llms.txt

Use this file to discover all available pages before exploring further.

This guide gets the Euroautos Inspection Form running on your local machine and walks you through creating and completing your first digital vehicle inspection. By the end you will have a working development environment and a clear picture of the full inspection workflow — from entering vehicle details all the way to generating a PDF report.
1

Clone the repository

Clone the project from GitHub and move into the project directory:
git clone https://github.com/juanmatz/inspection-form-euroautos.git && cd inspection-form-euroautos
This creates an inspection-form-euroautos/ folder containing all application source files, configuration, and an .env.example template you will use in the next steps.
2

Install dependencies

Install the project’s Node.js dependencies using your preferred package manager:
npm install
Dependency installation typically takes under a minute on a standard connection. A node_modules/ directory will be created once installation is complete.
3

Configure environment

Copy the provided example environment file to create your local .env:
cp .env.example .env
Open .env in your editor and set at minimum the required variable:
.env
# Required — displayed in the header of every generated inspection report
VITE_WORKSHOP_NAME="Euroautos Workshop"

# Optional — backend API endpoint for cross-device sync
# Leave blank to run in fully offline/local mode
VITE_API_URL=
All variables prefixed with VITE_ are embedded into the application at build time by Vite. If you change a value in .env while the dev server is already running, restart the server for the change to take effect.
See the Installation page for the full list of supported environment variables.
4

Start the development server

Start the Vite development server:
npm run dev
You should see output similar to:
  VITE v5.x.x  ready in 312 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help
Open http://localhost:5173 in your browser. The Euroautos Inspection Form dashboard will load, showing an empty list of inspections and a Nueva Inspección button.
The application works fully offline once the page has loaded. You can disconnect from the internet and continue creating and completing inspections — all data is saved in your browser’s local storage and will sync to the configured backend when you reconnect.
5

Create your first inspection

With the app open in your browser, follow these steps to complete a sample inspection:
  1. Click “Nueva Inspección” on the dashboard. A blank inspection form opens immediately and is auto-saved to local storage.
  2. Enter vehicle details in the first section:
    FieldExample value
    Matrícula (Plate)1234 ABC
    Marca (Make)Volkswagen
    Modelo (Model)Golf
    Año (Year)2019
    Kilometraje (Mileage)87,450 km
    Propietario (Owner)Ana García
  3. Proceed through inspection sections — use the section tabs or the Siguiente button to move through each checklist (Engine, Brakes, Tyres, Bodywork, Interior, Lights). For each item, select OK, Requiere Atención, or Urgente. Add a note to any item by clicking the notepad icon beside it.
  4. Attach a photo — on any item marked Requiere Atención or Urgente, click the camera icon and either take a photo or select an image from your file system. The thumbnail will appear inline in the checklist.
  5. Sign off — once all sections are complete, scroll to the bottom of the form and provide your digital signature in the signature pad. Click Confirmar y Firmar to lock the inspection.
  6. Generate the PDF report — click Generar Informe. A PDF will be prepared client-side and downloaded automatically to your default downloads folder.
To inspect exactly what the application is storing, open Chrome DevTools → Application → Storage → IndexedDB and expand the euroautos-inspections database. You will see each inspection record as a structured JSON object, including all checklist answers, notes, and base64-encoded photo data.

​
What’s Next

Now that you have the app running and have completed a sample inspection, explore the rest of the documentation:
  • Installation — full system requirements, all environment variables, and deployment options
  • Inspection Sections — how to customise the checklist sections and individual items
  • Photo Capture — configuring photo compression limits and storage behaviour
  • Report Generation — branding the PDF report with workshop logos and custom footers

Build docs developers (and LLMs) love

Get started for freeTalk to us