ForgeLocalLive preview

ForgeLocal documentation · v1.2.0

Deployment

Open locally or deploy to Netlify, GitHub Pages and ordinary hosting without a build command.

1. Test locally

Double-click index.html for basic review. Some browser security rules can affect local SVG references, so a local static server is preferable for final testing. No build command is required.

2. Netlify

  1. Zip or select the ForgeLocal folder.
  2. Drag the folder into the Netlify deployment area or connect a repository.
  3. Use the project root as the publish directory.
  4. No build command is required.
  5. After deployment, verify HTTPS, every page, forms and redirects.

3. GitHub Pages

  1. Create a repository and upload the folder contents.
  2. Enable Pages from the chosen branch and root folder.
  3. Use relative links exactly as provided.
  4. Remember that GitHub Pages has no built-in form backend.
  5. Set the real canonical domain after publishing.

4. Ordinary shared hosting

  1. Open the hosting file manager or FTP/SFTP client.
  2. Upload the contents so the chosen index.html is in the public web root.
  3. Preserve the assets, pages and documentation folders.
  4. Enable HTTPS and test both www and non-www routing.

5. Choosing a homepage

The root index.html is a marketplace preview. To launch a sector demo as the real homepage, copy its body and metadata into a root-level file, then change asset paths from ../assets/ to assets/ and page links from same-folder names to pages/name.html. Test every link afterward.

6. 404 and 500 pages

Hosting providers configure custom error-page paths differently. Point the platform to pages/404.html and pages/500.html according to its current settings.

7. Troubleshooting

  • Missing styles: confirm the relative assets path.
  • Broken icons: keep assets/icons/icons.svg on the same origin.
  • Forms do not send: expected until an endpoint is configured.
  • Menu does not open: confirm all JavaScript files uploaded and no browser extension blocked them.
  • Wrong social preview: replace absolute example.test metadata and clear platform cache.

8. Browser support

Current Chrome, Edge, Firefox, Safari, Mobile Safari and Chrome for Android. Progressive enhancement preserves core content and phone links.

Version 1.2.0

Preview screenshots and caching

Deploy assets/screenshots and marketing/preview-assets with the package. Enable Brotli or gzip for text files and long-lived caching for versioned WebP assets. Re-run Lighthouse on the deployed domain.