Skip to main content

​
Landing Site Lab Overhaul — Business Learnings

​
Context

The “Lab” section on devarno.cloud is the primary showcase of all Devarno ecosystem tools. It was functional but had no visitor tracking, no search engine optimisation, and no way to measure which projects attract attention.

​
What changed

  1. Visitor attribution tracking — Every outbound link (card clicks, GitHub, Calendly, social profiles) now carries UTM parameters identifying devarno.cloud as the source. This means when someone clicks through to SO1 or Skyflow, we can see in those products’ analytics that the visit originated from the portfolio site.
  2. Five analytics events — We now track: which org cards people click, what they search for, which filters they use, which footer CTAs convert, and which social platforms they visit. All privacy-friendly via Plausible (no cookies, GDPR-compliant).
  3. Search engine visibility — The Lab now has its own dedicated URL (/lab) with proper page titles, descriptions, and structured data that Google can index. Previously it was only an anchor section on the homepage with no independent SEO value. A sitemap and robots.txt were also added — the site had neither.
  4. Visual polish — Cards now animate in with a stagger effect, hover states show a glow and lift, and interactive elements have consistent feedback. This matches the quality bar of the rest of the site.

​
Impact

  • Measurable funnel: Can now answer “how many visitors explore the Lab?” and “which projects get the most clicks?” for the first time.
  • SEO surface area: /lab is now independently indexable. The JSON-LD structured data lists each public project as a SoftwareApplication, which can appear as rich results.
  • Domain alignment: All references updated from devarno.com to devarno.cloud. Plausible analytics was pointing at the old domain — visitor data was being lost.

​
Operational Takeaways

  1. Domain migration has a long tail: Even after the primary rebrand, four files still referenced devarno.com in metadata, analytics config, and content links. Automated grep sweeps should be part of any domain change checklist.
  2. Analytics without a sitemap is half-blind: The site had Plausible and Vercel Analytics but no robots.txt or sitemap. Search engines couldn’t efficiently crawl the site. These are table-stakes files that should exist from day one.
  3. Build pipeline gap: The landing site cannot currently npm run build due to a missing workspace dependency (@v01t/client). This blocks standard CI verification. Resolving this dependency should be prioritised so future changes can be build-tested.

​
Action Items

  • Fix @v01t/client@workspace:* dependency so the landing site can build
  • Update GitHub org URLs to owner/repo format to activate live metrics on cards
  • Set up Google Search Console and uncomment verification code in meta.ts
  • Monitor Plausible for first Lab analytics data after deploy