Welcome to the new tictag.io
We rebuilt tictag.io from the ground up — faster, cleaner, and ready for the next chapter of AI + data work across Southeast Asia.
This is the first post on the rebuilt tictag.io. If you're a long-time reader, welcome back — and if you're new, this is a good place to start.
Why rebuild?
The old site served us for years on HubSpot CMS, but the ceiling on Core Web Vitals, build-time content pipelines, and developer velocity was too low.
Full migration notes are coming in a follow-up post for the engineering crowd.
We now run on Next.js 16, Tailwind v4, and a Velite MDX pipeline so the team can ship posts through pull requests instead of wrestling with a block editor.
The numbers behind the rebuild
Alongside the rewrite we audited every page on the old site. Here's one stat that captured why this project was worth the effort:
That single metric alone justified the rebuild — and it compounds across every page on the site.
What our team is saying
The new pipeline means a two-week content idea ships in a morning — which is exactly the speed we need as the Startup Suite story evolves.
A look at the new blog detail layout
Code blocks, first-class
Velite + rehype-pretty-code gives us Shiki-highlighted blocks with zero client JavaScript — they're pre-rendered to HTML at build time:
import { getAllPosts } from "@/lib/content";
export default function BlogIndex() {
const posts = getAllPosts();
return posts.map((p) => <BlogCard key={p.slug} post={p} />);
}The supported languages are ts, tsx, js, bash, and json — we cap the
Shiki bundle to keep the blog route's First Load JS under budget.
What's next
Over the next few months we'll be migrating the remaining archive from the old site — the case studies are already on their way — and launching the Tictag Startup Suite preview.