We run our own resource hub on the CMS we built for CrawlTheory
The tables and admin behind this hub were ported from the CMS we built for CrawlTheory. What it does, what it lacks, and why we use our own tools.
- We use the tool we sell: the hub runs on the CMS we built for CrawlTheory.
- The tables live in their own database schema, apart from the main site.
- Roles, case-study blocks, industry tags, FAQs and a last-verified field are built.
- Known gaps: last-verified date and reviewer are not yet shown, and FAQ schema markup is not yet output for hub posts.
- No traffic or AI-citation result has been recorded.
Quick answer
The resource hub you are reading runs on a CMS ported from the one we built for CrawlTheory, an SEO publication Aadarsh co-founded. It has three roles, a case-study editor with blocks, industry tagging, FAQs per post, and a last-verified date and reviewer field per post. Some of these are stored but not yet shown on the page. We list the gaps below.
Disclosure: Aadarsh Mishra co-founded CrawlTheory. We built its CMS and ported the design to this hub.
What we did
We built an admin CMS for CrawlTheory, a publication built on Next.js and Supabase. When we needed a resource hub for GarunaCDX, we ported its tables and admin instead of starting again. The hub’s tables live in their own hub database schema, apart from the main site’s data.
What it does
- Three roles: super admin, editor, viewer.
- A case-study editor with blocks such as charts, before-and-after views and diagrams.
- Industry tagging, so posts and case studies can sit under an industry.
- FAQs attached to each post, stored as data.
- A last-verified date and a peer-reviewer field per post.
What it doesn’t do yet
The last-verified date and the reviewer are stored, but the page doesn’t show them yet. FAQs are stored per post, but FAQ structured data isn’t output for hub posts yet. The hub also has no built-in badge for how strong a piece of proof is. We label proof in the text for now. All three are on our list.
Why we use our own tools
Because it is the fastest way to find what is wrong with them. Running our own content through the CMS is how we found the three gaps above. It also means that when we say a marketing team can publish without a developer, we have done it ourselves.
What we haven’t shown. We have no traffic number and no record of being cited by an AI search tool for CrawlTheory or for this hub. Using our own CMS doesn’t prove it works for your business.
The description comes from our own repository, migration notes and project notes, and is tracked in our claim ledger. Aadarsh co-founded CrawlTheory. No figure comes from a third party.
More by GarunaCDX
Get GarunaCDX news in your inbox.
Launches, new case studies and the industry shifts we are watching — once a month.
