Static website and Plesk publishing

Public site: esri-arcgis-customdatafeeds.techmaven.net. The domain is hosted in Plesk and is not connected to GitLab. A Git push does not publish the website.

The current homepage describes the delivered P1 capabilities, distinguishes local evidence from production qualification, and explains CloudFS activation limits. marketing-landing-page.html is a matching compatibility page with the same canonical URL. docs/index.html links to public HTML guides generated from the approved Markdown documents. Repository access requires GitLab sign-in; visitors can read the published guides without an account. All pages include Home, Portfolio and Esri ArcGIS Solutions in their navigation and footer.

Build the upload bundle

From the repository checkout, use Node.js 22 or 24:

npm ci
npm run website:check
npm run website:build

This renders approved Markdown with pinned Marked, validates every local link and anchor, then writes only approved public files to dist/website/. Raw Markdown HTML is escaped and unsupported URL schemes cannot create links. Unknown files or symbolic links already present in the output directory stop the build. The deployed website needs no JavaScript runtime, third-party fonts, CDN assets or application server. It uses HTML, CSS and an SVG favicon. It does not serve the diagnostic API or run a query service.

On Windows, create a ZIP with the files directly at the archive root:

Compress-Archive -Path dist/website/* -DestinationPath dist/website-plesk.zip -Force

The bundle contains the two landing pages, documentation hub, generated HTML guides, two credential-free example configurations rendered as guides, fixture evidence, the Grafana dashboard, CSS, favicon and version.json. Its public-file manifest is recorded in version.json. Fixture evidence omits local absolute paths. No provider source code, operational configurations, credentials or research archives belong in this upload. The build job also archives dist/website/ in GitLab CI.

Upload with Plesk File Manager

Open the domain's document root in Plesk. Use the configured root; it may be httpdocs or a domain-specific directory.
Download a backup of the current homepage, marketing page and any existing docs/index.html and website/ assets. Preserve the server configuration and unrelated site files.
Upload website-plesk.zip, select Extract Files, and extract its contents directly into the document root with Replace existing files selected. Do not extract into a new website-plesk/ subfolder. Use the domain's normal static-file permissions.
Remove the uploaded ZIP after extraction. If the host has a CDN or page cache, purge the affected URLs through its normal controls.
Hard-refresh the homepage, /marketing-landing-page.html and /docs/. Check the P1 heading, all three company links, a public guide such as /docs/p1-capabilities.html, and the stylesheet. Verify the source revision at /version.json. A changed version.json with an old homepage usually indicates page caching or an incorrect document root.

See Plesk's File Manager upload and extraction procedure for the panel controls.

The CSS uses responsive layouts and visible keyboard focus, with a reduced-motion option. The HTML sets a restrictive meta content security policy for this static content. Server headers can impose stricter rules; validate them in the actual Plesk environment.

For rollback, restore the backed-up page and asset files and purge the affected cache. This website deployment does not change the provider's ArcGIS certification status or deploy its API.

Maintain the content

Update index.html and copy it to marketing-landing-page.html so both entry points stay consistent. Update the documentation hub when adding or retiring a guide. Keep evidence claims tied to the production review and roadmap; do not advertise research modules as delivered capabilities.