Thursday, April 17th 2025, 11:37 am
Today is exactly two weeks into building this site. A complete, enterprise-scale product demonstration. It has all the elements of a full scale production site, it could be a TV station, a radio station, financial news, sports news. I've been thinking lately about all the types of products it could be used for, now that we are ready to expand and bring on new large customers.
A year ago I traveled to Australia and took a particular interest in Aboriginal art, and had a wonderful conversation with an art gallery owner. They had a big problem because of how prolific their artists are, and their CMS just couldn't keep up with the data entry required, or the complexity in the structure of how the artworks relate to each other. It needed an arbitrary data association. We can do that! I'd encourage you to check out Mbantua Gallery if you have time. These artists are paid by the square foot they make so much.
Anyways, I digress. I'd like to show you how fast a big site like this can be created. I'm one guy. Yep, this whole product that currently serves 2 Million requests per hour for current large customers, is operated by one guy. Just to give you an idea of how efficient this stack is, here is a graph of the traffic we are serving for just ONE of those sites, measured in 5min intervals. It just spiked to 50k requests/5 min, and I'm not even alarmed. New servers will be created to soak up that demand while I write this article.
Once again, I've digressed. Here is my status today on "building this site". I haven't made any changes that require deployments. I'm setting it up straight from the box, and I've already got many pages and site structures in place:
I've written a bunch of stories, and I've had ChatGPT write some stories as well. It's a content site, of course, I've got to have content:
The point of this story is to show you, and to make a record of, the screenshots at this point in time. You can see I've only been writing stories and making pages since 4/3/2025 and today is 4/17/2025. Exactly two weeks. I'd like to see another CMS provider match that, especially considering how fancy the pages are.
We've created many user-interactive features without needing to deploy a thing, and you can too. On this site, I'm using ChatGPT to create those experiences, just as your designers would. I could have done it myself, but I wanted to prove that a front-end isn't necessary. Viking CMS can easily digest the output of any AI code assistant in a way that nobody else can, and without a single email or phone call.
I'm Don Drury, and I created Viking CMS. I built a whole enterprise-scale CMS based on a need I saw working as a front-end developer within the largest media conglomerate in Oklahoma. They had spent 20 years trying to work around their CMS. They had hired a back-end developer, a front-end developer, 4 designers and still weren't able to do the basic things they wanted to do. I built Viking CMS and changed everything for them.