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
Most people see AI tools as shortcuts.
I see Lovable as a speed multiplier.
It doesn’t replace thinking.
It removes friction.
With Lovable, I can go from idea → working product in days, not weeks.
And that changes everything.
Because in today’s market, the advantage isn’t who knows more
It’s who can execute faster.
Paired with tools like Supabase for backend and platforms like Contra to showcase work, it becomes a powerful stack for builders who want to ship, not just plan.
Still exploring. Still learning.
But one thing is clear:
Tools don’t make you valuable.
How you use them does.
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
This is so true! Even in 3D product animation, I always start with rough sketches on paper before jumping into Blender.
It saves hours of rework and the ideas flow more human. AI can't replace that feeling.
Great process Filip!
Is sketching part of your creative workflow or we've forgotten what it feels to be human?
Depending on the projec's scope, I normally like to explore my ideas on paper before I come up with the best solution.
And no, they're not perfect.
They are rough and messy, my goal is so...
Same thing happens in sales copy. A rough outline on paper catches the weak argument before I waste time polishing it.
Landing page for an AI-native terminal platform
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.