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
Developed a fully custom WordPress website for ScrumQueens, transforming the previous website into a modern, structured, and maintainable digital platform.
Key Contributions:
Custom-developed the WordPress website to support the project's specific content and business requirements.
Designed and implemented custom WordPress data structures for organized content management.
Migrated a large volume of content and data from the previous website into the new custom WordPress structure.
Worked with WordPress development capabilities, including PHP, custom post types, and content management functionality.
Focused on maintaining content integrity throughout the migration and making ongoing website management easier.
Tech Stack: WordPress, PHP, MySQL, HTML, CSS, JavaScript.
The project demonstrates hands-on expertise in custom WordPress development, complex content migrations, and building maintainable CMS solutions.
How did you check the older content after migration? Matching article counts is one step, but I'd be curious how you checked images and links inside the articles.
Good question! Since there was a lot of content, I used manual spot-checking rather than checking every article. I tested different articles to make sure images loaded, links worked, and formatting looked right after migration.
Got it, thanks. Did you include the oldest articles in that sample? Older image paths and embeds would be the first things I'd check there.
Yes, I included some of the older articles in the checks as well, especially to make sure images, links, and embedded content were still working properly.
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
🚀 Saasti — Smart Automation for Growing Businesses
A modern SaaS website concept designed to turn complex automation into a simple, intuitive experience. With clean layouts, interactive workflow dashboards, vibrant accents, and clear messaging, every section highlights the power of smarter business operations.
✨ Modern SaaS UI/UX Design
⚡ AI-Powered Automation Experience
📊 Intuitive Workflow Dashboards
🎨 Clean, Conversion-Focused Layout
Designed by OrdainIT to bring innovation and usability together.
#SaaSDesign #UIDesign #UXDesign #AI #WebDesign #DashboardDesign #OrdainIT
Brilliant execution!
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.
Modern Slick hero page design figma+Tailwind+Gemini ;)
