Deployment, SEO and troubleshooting

Publish Nexora without a build process and replace all project-specific metadata.

Deploy to Netlify

Keep index.html at the package root.
Drag the complete nexora folder into Netlify Drop or connect a repository.
Use the root as the publish directory. No build command is required.
Open several nested pages and confirm relative assets load.
Configure a custom domain and HTTPS in the hosting dashboard.

Deploy to GitHub Pages

Create a repository and upload the contents of the nexora folder.
Enable Pages for the chosen branch and root folder.
Use relative links as supplied. For a project-site subpath, do not replace them with root-relative paths.
Wait for deployment, then test homepage, nested page, CSS, JavaScript and SVG requests.

Deploy to ordinary hosting

Upload the complete folder with FTP/SFTP or the hosting file manager. Preserve lowercase filenames and folder structure. Set the domain’s document root to the folder containing index.html. The server should serve .html, .css, .js and .svg files with normal MIME types.

SEO customization

Every public page includes a unique title, description, canonical placeholder, Open Graph data, social-card data, favicon, theme color and robots directive. Replace https://example.com/ everywhere. Export the included social-preview SVG to a broadly supported 1200×630 PNG or JPG and update the metadata path.

Structured data

JSON-LD examples include Organization and SoftwareApplication, with Article, Product or JobPosting on relevant examples. Replace fictional values, remove types that do not apply, and validate the final markup. No review aggregate, real certification or binding offer is included.

Security and compliance placeholders

Security and compliance pages describe a structure, not verified controls. Replace all statements after review by the responsible organization. Placeholder badges and phrases such as “designed to support” must not be converted into certification claims without evidence.

Browser support

Nexora targets current Chrome, Edge, Firefox, Safari, Mobile Safari and Chrome for Android. Core content remains readable without optional Intersection Observer animation. Native <dialog> receives a simple open-attribute fallback.

Common troubleshooting

Symptom	Check
Unstyled nested page	Confirm `../assets/` paths and preserve folders.
Theme does not persist locally	Some strict private modes block local storage; the default theme still works.
Forms do not send	This is expected until a real endpoint and submit method are configured.
Open Graph image is missing	Many platforms require an absolute URL and raster image.
Page gives 404 on host	Verify exact filename, letter case and uploaded folder depth.

Pre-launch release checklist

Replace the brand, URLs, contact information, fictional claims, prices, customer names, legal copy and structured data. Test navigation, forms, keyboard focus, reduced motion, both themes, responsive layouts, metadata, console output and all relative links on the final host.