Arcframe Docs
Live preview · Version 1.0.0

Deployment

Publish Arcframe to Netlify, GitHub Pages or ordinary static hosting and resolve common setup issues.

1. Before deployment

  • Replace fictional identity, contact information, projects, people, awards and metrics.
  • Update every title, meta description, canonical URL and structured-data URL.
  • Connect forms or clearly disable submission.
  • Compress replacement media and verify licences.
  • Test all pages at mobile and desktop widths.

2. Deploy to Netlify

  1. Sign in to Netlify and choose the option to deploy a site manually.
  2. Drag the arcframe folder contents into the deployment area. The uploaded root must contain index.html .
  3. No build command or publish-directory configuration is required.
  4. Open the generated URL and check page transitions, links and forms.
  5. Connect a custom domain only after the temporary preview works.

For a Git-based deployment, use the repository root as the publish directory and leave the build command empty.

3. Deploy to GitHub Pages

  1. Create a repository and upload the contents of the arcframe folder.
  2. Open repository Settings → Pages.
  3. Select deployment from a branch, choose the main branch and root folder.
  4. Wait for the Pages URL, then test relative paths.

The package uses relative links, so it works from a project subdirectory. Canonical and social-image URLs are placeholders and must be changed to the final public URL.

4. Deploy to ordinary hosting

  1. Open the hosting file manager or connect by SFTP.
  2. Upload the contents of the arcframe folder to the web root, often named public_html , www or htdocs .
  3. Confirm that index.html is directly inside that web root.
  4. Preserve the folder names and letter case exactly.
  5. Enable HTTPS in the hosting control panel and test the public domain.

5. Local preview

You can open index.html directly. For behaviour closest to hosting, run any basic static server. One example for a computer with Python installed: 

cd arcframe
python3 -m http.server 8080

Then open http://localhost:8080 . No project installation or build step is involved.

6. Common troubleshooting

Problem Likely cause Check
Page shows a directory listing index.html is one folder too deep Move the package contents into the host’s web root
Styles are missing Folder names or relative paths changed Restore assets/css and exact filename case
Artwork is missing Only HTML files were uploaded Upload the complete assets folder
Forms do not deliver No endpoint is configured Follow the forms guide
Transitions do not run locally File-protocol protection is active Use a local server; navigation itself still works
Wrong theme flashes Early theme script was removed Restore the inline head script and theme.js
Mobile menu cannot open Script path is broken Check browser console and assets/js/navigation.js

7. Reduced-motion and browser testing

Enable “Reduce motion” in the operating system, reload the site and confirm that content remains visible without movement. Test current Chrome, Firefox, Safari and Edge, plus a real iOS or Android device where available. Keyboard-test menus, filters, dialog, comparison slider and forms.

8. Asset credits

All included project visuals, portraits, marks and map graphics are original abstract SVG/CSS compositions created for Arcframe. The package uses system font stacks and does not bundle third-party photography, company logos or paid plugins.