> ## Content Index
> Fetch the complete content index at: https://onemanandhisblog.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Building Ampp3d - technically
- URL: https://onemanandhisblog.com/2014/06/ampp3d-development-wordpress/
- Published: 2014-06-16T23:17:16.000Z
- Updated: 2015-04-08T16:17:10.000Z
- Author: Adam Tinworth
- Tags: Ampp3d, developers, Reach, WordPress

![the source code for Ampp3d](https://i1.wp.com/www.onemanandhisblog.com/content/images/2014/06/usvrsvenn.png?resize=960%2C342)

If you’re interested in the technical detail of how sites come to be – and if you’re serious about publishing, you should be – William Turrell’s account of how he [built Ampp3d](http://wturrell.co.uk/ampp3d/?ref=onemanandhisblog.com) makes for fascinating reading:

> I find it helps to put something imperfect into the wild but make a private commitment to yourself to come back and deal with it properly later; my record on that is far from 100% but there’s a definite sense of achievement when resolving a long standing bug or paying off your technical debt.

And that honesty is on show throughout the piece.

However, buried down near the end are words that sent a chill through me:

> Now that the site has proven itself editorially, The Mirror want to bring it within [their own CMS](http://www.escenic.com/?ref=onemanandhisblog.com), but my intention is to archive the present version (and it’s URLs) for posterity.

That’s a decision I have *literally never* seen end well.

Good luck Ampp3d team…