📞 Maxima CX Website

🔗 Live GitHub Preview

📸 Screenshots

🖥️ Desktop preview:

📱 Tablet Preview

📱 Mobile Preview

🏅 W3C HTML Validator

🏅 W3C CSS Validator

🌈 Chrome LightHouse Audit

Desktop:

Mobile:

⚡ PageSpeed Insights Results

Desktop:

Mobile:

🛠️ Built with:

🔨 Fully Responsive, Mobile First Approach, Transitions, Animations, Grid & Flex Layout
⛏️ Google Font: Poppins

This is the newly created website for the brand Maxima CX. The design for it was inspired by Converst's Website. It uses the Nuxtship - Nuxt SAAS Starter Website Template as a base.

🚀 Nuxtship - Nuxt SAAS Starter Website Template

Nuxtship is a free starter nuxt website template for saas, startups, marketing websites & landing pages.

The Nuxtship - Nuxt SAAS Starter Website Template is build on top of the Nuxt 3 Minimal Starter.

This Free Template is sponsored by jakob-aichmayr.pages.dev.

Look at the Nuxt 3 documentation to learn more.

🧰 Online resources and tools:

🖼️ Photopea [Online Photo Editor]

🌐 Browser Support:

(Last updated and tested: 07/08/2025)
🌟 Chrome 151.0.7922.109 (64-bit)
🦊 Firefox 153.0.3 (64-bit)
🏴‍☠️ Opera 134.0.5954.46 (64-bit)
🪟 Edge 151.0.4129.72 (64-bit)

🧪 Online Validators:

✔️ W3C HTML Validator
✔️ W3C CSS Validator
💡 LightHouse Audit
⚡ PageSpeed Insights Audit
⭐ WebPageTest

Setup

Make sure to install the dependencies:

# npm
npm install

Development Server

Start the development server on http://localhost:3000:

# npm
npm run dev

Production

Build the static site:

# npm
npm run generate

Locally preview the production build:

# npm
npm run preview

Check out the deployment documentation for more information.

Deployment

This project deploys to GitHub Pages using GitHub Actions. The current configuration in nuxt.config.ts hard-codes the GitHub Pages base path /maxima-cx/, the canonical origin https://ralitsavoronevska.github.io, and the matching Web3Forms access key.

The site is served from the /maxima-cx/ subpath, and the default branch for deployment is master. The gh-pages branch is no longer used; deployments are handled only by GitHub Actions from master.

Push to master:

git push origin master   # → CI builds & publishes to GitHub Pages

This triggers the Deploy to GitHub Pages workflow, which runs npm run generate and publishes .output/public via the official upload-pages-artifact / deploy-pages actions. One-time setup: Settings → Pages → Source must be GitHub Actions.

The package script deploy is only a convenience alias for pushing the branch:

npm run deploy

It does not publish the site directly; the actual Pages publish is handled by the workflow.

Local development

Use the regular Nuxt dev server for local work:

npm run dev

For a static build, run:

npm run generate

The build is configured for the GitHub Pages sub-path, so it is deployed as-is by the Pages workflow.

Contact form — the Web3Forms key

The contact form (app/pages/contact-us.vue) submits to Web3Forms, which needs an access key to deliver submissions. The project uses a single GitHub Pages key in nuxt.config.ts, which is public by design and restricted in the Web3Forms dashboard to the GitHub Pages host.

There is nothing to configure in the repo for this to work; the key is baked into the static build at generation time. For local testing, you can override it with an unrestricted dev key:

echo 'NUXT_PUBLIC_WEB3FORMS_KEY=your-dev-key' > .env

NUXT_PUBLIC_WEB3FORMS_KEY overrides the config value in local development.

Rotating a key

Edit the key in nuxt.config.ts and rebuild/redeploy — there is no repo secret or server env var to keep in sync.

🌟 Inspiration & Credits:

🪄 Claude AI
GitHub Coplit

---

🙌 Thank you for checking out my project! More is coming 🔜.
Stay tuned 🚀 and please don't forget to give the project a star! ⭐
Made with lots of 💗, ☕, and a sprinkle of ✨ by Ralitsa Voronevska!