Live: https://ridimit-exchange.vercel.app/
Repo: https://github.com/malvisanochie1/Ridimit-Exchange

To start website locally, simply open the index.html file in your web browser:

1. Navigate to the project folder.
2. Double-click index.html (or right-click and choose "Open with" → your browser).

• index.html, about.html, rates.html — main pages
• assets/ — CSS, fonts, vendor CSS/plugins
• imgs/ — images
• js/ — site scripts

Fork, create a branch, make small commits, and open a PR against main. Include a short description and screenshots if you change visuals.

No license file is included. Add a LICENSE (MIT/Apache-2.0) if you want permissive reuse.

Run with VS Code Live Server extension:

1. Install the Live Server extension.
2. Right click index.html -> "Open with Live Server" or click the Live Server button.

Tips

• When testing, clear browser cache or use an incognito window to ensure asset changes load.
• Use your browser devtools (Lighthouse) to check performance and accessibility while developing.

• Branch from main for features: git checkout -b feat/your-feature.
• Make small, focused commits with descriptive messages.
• Run visual/manual checks across desktop and mobile widths. If you add JS, ensure graceful degradation when JS is disabled.
• When ready, open a pull request with a short description, screenshots, and verification steps.

This site is already deployed to Vercel. Typical setup steps for Vercel follow:

1. Sign in to Vercel and import the repository malvisanochie1/Ridimit-Exchange.
2. Set the root to the repository root (no build command required for static HTML).
3. Set the Output Directory to / (or leave blank) — Vercel will serve static files from the repo root.
4. Deploy. Vercel will create a production URL and auto-deploy on new commits to the connected branch (e.g., main).

Recommended Vercel settings

• Framework Preset: None (Static)
• Build Command: (leave empty)
• Output Directory: (leave empty or /)
• Environment variables: none required for static site

If you use a custom domain, add it in the Vercel dashboard and follow DNS verification steps.

• Images: Prefer WebP/AVIF for production and provide width/height attributes to reduce layout shift.
• Fonts: Use font loading strategies (font-display: swap) and host only the required font subsets.
• CSS: Minify and remove unused CSS for production. Consider critical CSS for above-the-fold content.
• JS: Keep vendor/plugin usage minimal. Defer non-critical scripts and use async when appropriate.
• SEO: Use semantic HTML, meta description, Open Graph tags and canonical URLs on pages to improve discoverability.
• Accessibility: Ensure keyboard focus order and visible focus outlines, provide alt attributes, and test with screen readers.

Run Lighthouse audits (Performance, Accessibility, Best Practices, SEO) and iterate on the results.

• Add server-side or client-side analytics (e.g., Google Analytics 4, Plausible, or a privacy-friendly alternative).
• For uptime and performance monitoring, integrate Vercel Analytics or external services like Sentry (for JS errors) and Upptime for uptime checks.

• No server-side code here, so the attack surface is small. Still:
  • Keep third-party scripts to a minimum.
  • Serve resources over HTTPS (Vercel handles this by default).
  • Review any vendor scripts for privacy and CSP compatibility.

Thanks for considering contributing! Small contributions — bug fixes, typo corrections, improved accessibility or small UI fixes — are very welcome.

Preferred contribution steps

1. Fork the repo and create a branch for your change.
2. Make small commits with clear messages.
3. Open a PR against main with a description, and include screenshots or steps to reproduce.

Notes for PRs

• If your change affects visuals, add before/after screenshots.
• If adding JS, follow the existing pattern in js/main.js and keep dependencies to a minimum.

• Code builds and pages load locally
• Cross-browser smoke test (Chrome, Edge, Mobile)
• No regressions to accessibility or performance (run Lighthouse)

This project currently does not include an explicit license file in this repository. If you'd like to publish this project with a permissive license, add a LICENSE file (for example, MIT). Example MIT header to add to files:

MIT License

Copyright (c) 2025 Your Name

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction...

Production static site (HTML/CSS/JS)

Live: https://ridimit-exchange.vercel.app/ · Repo: https://github.com/malvisanochie1/Ridimit-Exchange

Ridimit-Exchange — production-ready static landing site (HTML/CSS/JS).

This repository contains the production build for the company landing site. It is not open for public changes or contributions. Any updates to content, assets or deployment are controlled by the project owners.

View locally

• Double-click index.html in the project root to open in a browser, or run a local static server:

Deployment

• Deployed on Vercel: https://ridimit-exchange.vercel.app/
• No build step required — static files served from the repository root.

Important files

• index.html, about.html, rates.html
• assets/, imgs/, js/

Support / changes

Changes are managed internally. For support or deployment questions contact the repository owner at https://github.com/malvisanochie1.

All rights reserved.