Reference: Repository Layout and Key Files – Key Configuration and Entry Points
This section outlines the core configuration and entry-point files in the Nexora Web Agency static site repository. Each file plays a crucial role in project setup, build and deployment, hosting configuration, form logic, and the main page templates. You’ll edit these files when updating project metadata, modifying build or hosting behavior, adjusting security headers or redirects, refining the quote-request flow, or changing page content and SEO metadata.
README.md
Location: README.md
The README provides a high-level overview of the project, including its purpose, tech stack, feature set, and usage instructions. It also documents environment requirements, available npm scripts, and security considerations.
- Project Information: Describes the business value of a high-performance, SEO-optimized static website powered by Netlify Forms and IntersectionObserver animations.
- Tech Stack & Features: Lists HTML/CSS/JS, Netlify hosting, serverless form handling, and interactive UI elements .
- Available Scripts:
npm run build: Builds the/distdirectory by copyingsrc/pages/,src/assets/, andpublic/.npm run dev: Runs the build script then servesdistlocally.
- Environment Variables: Notes
NODE_VERSION="20"reserved innetlify.toml. - Security Notes: Summarizes strict security headers (Clickjacking, XSS, MIME sniffing, Referrer Policy).
Edit the README when you need to update:
- Project overview or feature summaries
- Build/development instructions or prerequisite versions
- Security or deployment guidance
package.json
Location: package.json
Defines project metadata and npm scripts that orchestrate the build and local development workflow.
{
"name": "nexora-agency",
"version": "1.0.0",
"private": true,
"description": "Nexora Web Agency",
"scripts": {
"build": "rm -rf dist && mkdir -p dist && cp -R src/pages/* dist/ 2>/dev/null || true && cp -R src/assets dist/assets 2>/dev/null || true && cp -R public/* dist/ 2>/dev/null || true",
"dev": "npm run build && npx serve dist"
},
"dependencies": {},
"devDependencies": {}
}
- build: Clears and recreates
dist/, then copies page, asset, and public files. - dev: Runs
buildand servesdist/for local preview.
Edit package.json when:
- Adding or modifying build/development scripts
- Introducing new dependencies or tooling
netlify.toml
Location: netlify.toml
Configures Netlify build settings, environment variables, routing rules, and HTTP headers for security and performance.
[build]
publish = "dist"
command = "npm run build"
[context.production.environment]
NODE_VERSION = "20"
[[redirects]]
from = "/*"
to = "/index.html"
status = 200
[[redirects]]
from = "/*"
to = "/404.html"
status = 404
[[headers]]
for = "/*"
[headers.values]
X-Frame-Options = "DENY"
X-Content-Type-Options = "nosniff"
X-XSS-Protection = "1; mode=block"
Referrer-Policy = "strict-origin-when-cross-origin"
[[headers]]
for = "/images/*"
[headers.values]
Cache-Control = "public, max-age=31536000, immutable"
[[headers]]
for = "/assets/*"
[headers.values]
Cache-Control = "public, max-age=31536000, immutable"
- [build]: Points Netlify at
dist/and runsnpm run build. - Environment: Locks Node version for the production context.
- Redirects:
- SPA fallback to
index.html(remove if not needed). - 404 catch-all to
404.html.
- SPA fallback to
- Headers:
- Global security headers.
- Aggressive caching for images/icons.
- Immutable caching for CSS/JS assets.
Edit netlify.toml when:
- Changing publish directory or build command
- Adding/removing redirects or custom 404 behavior
- Tuning security or cache headers
forms.js
Location: src/assets/js/forms.js
Implements the client-side logic for the 3-step quote-request form, managing step navigation, validation, and UI state without page reloads.
- Initialization: Binds to
#quote-formand exits on other pages. - State Tracking: Maintains
currentStepand toggles.activeand.completedclasses on.form-stepand.progress-step. - Next/Back Buttons:
- Validates budget selection at step 2.
- Smoothly scrolls to top of the form container on step change.
- Update Function:
- Shows only the current step.
- Updates progress indicators accordingly.
Edit forms.js when:
- Adding or removing form steps
- Changing validation rules or button behavior
- Adjusting scroll offsets or animation timing
Main Route Pages
Locations: src/pages/*.html and public/*.html
These HTML files serve as the entry points for each site route. They share a common header, footer, and asset references, and include page-specific content and meta tags for SEO.
- index.html: Home page with hero, metrics, service cards, founder snippet, and CTA .
- services.html: Lists core capabilities with category toggles.
- quote.html: Houses the multi-step quote-request form wired to Netlify Forms.
- contact.html: Static contact form for general inquiries.
Edit these pages when:
- Updating page content, headings, or calls to action
- Modifying SEO metadata (
<meta name="description">,<title>) - Adjusting which CSS/JS assets are loaded or changing component markup
Each page imports:
<link rel="stylesheet" href="/assets/css/global.css">
<link rel="stylesheet" href="/assets/css/utilities.css">
<link rel="stylesheet" href="/assets/css/main.css">
<script src="/assets/js/forms.js"></script> <!-- on quote.html only -->
This reference highlights the files you’ll most often interact with when configuring the build pipeline, hosting behavior, form logic, and top-level page templates. Understanding these entry points ensures efficient updates to project setup, deployment, and core user flows.