The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
ExamShield AI is a full-stack online exam platform where admins create MCQ exams and students take them under live webcam proctoring. MediaPipe face detection runs in the browser to flag missing or multiple faces, looking away and tab switches, so no video leaves the student’s device. Each session gets a suspicion score and an approve, review or reject recommendation, and answers are graded on the server. Built with React, TypeScript, Tailwind, FastAPI and MongoDB Atlas, and deployed on Vercel and Render.
I love this very much
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Landing page for an AI-native terminal platform
AI & Automation Academy Website Design
Designed a modern Kajabi, responsive website for an AI & Automation Academy focused on helping engineers, founders, and professionals develop practical AI skills. The goal was to create a structured learning experience that makes it easy for visitors to explore courses, understand learning pathways, and find the right training programs.
The website features a bold hero section, clear calls to action, featured course cards, structured learning tracks, and dedicated sections highlighting hands on projects, certifications, quizzes, and learning resources. A dark interface, vibrant purple and cyan accents, and AI-inspired visuals establish a technology-focused identity while maintaining readability and visual consistency.
The layout prioritizes intuitive navigation, clear content hierarchy, and responsive design to help users move from discovering the academy to exploring courses and considering enrollment.
Key features:
AI and automation education website design
Course catalog and featured course sections
Beginner, Builder, and Advanced learning pathways
Student dashboard and certification feature presentation
Resource library, quizzes, and project-based learning sections
Strategic CTAs for course exploration and enrollment
Responsive layout and modern UI/UX design
Dark theme with purple and cyan visual accents
Check the Live Sitemap Before Signing Off the Release
A sitemap can export correctly while the live website still serves an older URL list. The task needs a check at the public sitemap address after deployment.
That check should compare the published file with the pages the team agreed to include.
Imagine an export containing 200 URLs. The public sitemap also contains 200, but it still lists a retired service page and omits the new replacement. The totals match. The contents do not.
Before closing the task, check:
• The production sitemap address returns the expected XML.
• Its complete URL list matches the agreed inventory.
• Each intended page type is represented, including a newly published page.
• Deliberately excluded pages remain absent.
• Someone owns the process that keeps the file current.
Start with the sitemap already on the site. It may be an index pointing to several smaller files. Include those files in the comparison so a working index does not hide an outdated section underneath it.
Keep the inventory decision explicit: which service pages, locations, articles or products belong in this release? A crawler's export tells you what it discovered. Compare that list with the pages the site was supposed to publish.
Open a sample of the listed URLs as well. Check that they reach the intended production pages and use the preferred addresses. If the sitemap includes modification dates, those dates should reflect significant page updates; exporting the file again does not make every page newly updated.
For a site that publishes regularly, document how new pages enter the sitemap and how retired pages leave it. An automated generator still needs clear inclusion rules and a check when those rules change.
Keep the public address, inventory comparison and update owner in the release notes. Make the sitemap discoverable through Search Console or robots.txt, and check for retrieval or processing errors. Submission does not guarantee that every listed page will be crawled or indexed.
I put together the generation, export and publishing steps in the full guide on Technical SEO Notes:
https://technicalseonotes.org/how-to-generate-and-export-an-xml-sitemap/
Projects and client work: NikoCodes
https://nikocodes.com/
Solid checklist. I'd add lastmod: if every release stamps today's date on every URL, Google learns to ignore it. It should only change when the page content changes. Also worth confirming every sitemap URL returns a direct 200, not a redirect.