So some of you might be horrified or intrigued by this but the speed that we can generate software with AI is always impressing me (and I have been using / programming against AI tools since the first llm / API that OpenAI released).
So for fun I thought I would see how long it might take to create a new viable audio website and fully publish it with 'useful' content. So here is a little timeline.
Note: I have my Pragmatic Audio blog already created and I knew what worked well with that so some of what I will describe below will seem is sort of cheating as I made upfront decisions to most generate what I now works for me.
But I will more highlight the AI tools used and mostly how long I spent with them
1. Domain Names ( 20 minutes - mostly thinking more deeply about what I wanted to build )
Last night, I thought it might be nice to have a second website - less about 'Pragmatic' stuff - but more about well engineered audio products at any price. So, using claude code I more / less asked for a list of possible websites that I could registered with ideally one .com but I did briefly ask for .audio domains. Given this is a bit of fun I didn't want to pay too much for the domain so as well as asking for good relevant domain names I wanted the annual fee to be cheap. I got probably 20 semi usual domain names and in the end I settled for
https://www.informedlistening.com as I felt it had the right concept for what I wanted to publish on the website and $15 a year seems reasonable. Using AWS route 53 !!
2. Architecture ( 10 minutes - I already had an idea of how and what I wanted to use to put everything together )
So, I originally was planning on looking at it over the weekend but when I got up this morning I thought why not use Codex to create a skeleton architectural plan for what to build - this involved me create a detailed 'prompt' describing mostly how I had build PragmaticAudio.com originally as a Hugo 'static CMS' Website hosted on gitlab pages. The advantage of this is you mostly get free worldwide hosting and gitlab pages when setup correctly will manage certiifcates and other 'difficult' aspects of website hosting.
3. Infrastructure setup ( 10 minutes )
This was basically giving codex readonly access to by private gitlab - so it could give instructions both for Gitlab but also AWS route 53 instructions to get the DNS and certificates all setup correctly - this took me most of a day to get fully right when I did it by hand for PragmaticAudio.com.
4. Build And Preview (30 minutes - mostly the back and forth refining what was generated )
So this involved reviewing the high level plan from 2 above, describing the main attributes I wanted this new website to have. Which was 3 things - Reviews ( just come cherry-picked ones I had already written copied over), 'Informed Articles' and News stories. These 2 extra features were subtasks of the overall plan which I will get too below.
So, which this expanded prompt I got codex to generate a complete Hugo website structure. There are lots of Hugo websites already on GitHub so it can easily 'Vibe code' a suitable structure with sample content. After a bit of reviewing ( basic back and forth with codex) I got mostly something locally that looked good and I briefly published it to make sure the gitlab setup from 3. above was all correct.
Note: I probably should have spent more time reviewing as tweaking this with 'real' content later too most of my time.
5. Subtask 1 - News and Editorial 'tool' ( 2 hour )
Since I wanted the 'Informed' name as part of the website - I feel that having up to date audio news might be the most useful aspect but while I don't want to have 'AI' scrap and generate crap new stories, I also am mostly busy with lots of other projects. So I thought of a middle ground - I still like RSS feeds and there are many useful sources of what I feel are 'informed' audio information - obviously AudioScienceReview being one of the most informed - so I got claude this time to generate a scheduled feed monitoring tool in python that would look at a bunch of websites that I would configure to find new news stories and update a small local DB of candidate stories for review - this tool looks something like this:
Because I don't want this to cost me money I have a local LLM Gemma4:12b running locally on my MacBook Pro - and the schedule tasks takes each story and asks this Gemma model to extra the website and summaries the contents so I can preview as per the image above. 'Approve' moves the generated summary (with the link to the stories, article or review) into my 'live' news to publish on the main website content - Hugo content is published by pushing content to gitlab.
I ended up spending probably an extra hour, refining the summarisation prompt used to generate suitable 'news' content from the various sources I picked. I also wanted to 'pin' certain stories e.g. the one against 'Capra Audio' that is now pinned on the website. So it got a little more complex.
6. Some interesting 'Informed Articles' for the website ( 2 Hours ).
So this will be the most controversial thing I feel in this article. So one tool I have been separately playing around with is thread summarisation - basically finding a good way to get LLM's to understand how to properly extract useful information from long threads - and I had written a extraction tool and summarisation tool for threads on ASR and some other websites. So for today I decided to create 'articles' based on those threads - so this is done via a 'Skill' which tries to structure the article into something relevant extracting the main topics from the longer thread into hopefully good paragraphs ( to be honest this is still a work in progress but I thought I would use it this morning ). The initial version of these was too short so I expanded the prompt and then expanded the skill to ask Codex to generate images and some diagrams to include in the content ( automatically without me prompting ) and to flesh out these still fairly short articles a little. Basically 4 of the classic threads from ASR and one from the headphones.com forum were used as examples ). The most fun was seeing the images generated from the topics extracted from the threads !!
7 Final tweaking ( 1 hour )
So, after all this AI fun - I decided to review what I had and change lots of things around - this is where I probably should have spend more time originally but for example, the new suggested layout for reviews didn't match my PragmaticAudio layout so I had to ask Codex (OpenAI) to generate the missing bits etc and the layout of the different sections needed again lots of tweaks. But in the end as a quick experiment in what could be done in a few hours I thought it was pretty good.
I will hopefully be keeping this update to date - that was the idea of the daily news edition tool being developed - the reviews should be shared with ones that I was doing on pragmatic audio and the articles will be updated as I make that thread summarisation better and some up with other articles or topics that would be good for a website called 'Informed Listening' !!
Here is the 'final' website after 6 hours:
Audio reviews, measurements, news, and technical analysis judged by engineering and listening performance.
www.informedlistening.com
For those who won't want to click here is what it looks like:
And I made that banner stories be dismissible - so the reviews and news become more visible: