It’s November 2017 and Interlitq: The International Literary Quarterly is 10 years old. Now, we’re not only redesigning the site but reworking the technical architecture from the ground up. One key question: do we migrate all the content from the last 10 years into the new design and architecture, or do we just start fresh with new issues going forward? The latter is the easy choice but there’s so much value in the first decade of Interlitq that it all deserves to be in the new design and technical architecture. We know that’s the right thing to do, so we’re doing it even though it’s not the easiest approach.
Before we go further, a few words about how we got to this point. I first heard about Interlitq in mid-2017 while having lunch with Peter Robertson in a restaurant in downtown Buenos Aires. I had known Peter, a Scotsman, for about a year. We both lived as expats in Argentina and found a connection through our mutual interest in literature. He mentioned that he was starting a literary review, but I didn’t really get involved until issue 2.
The site was developed and designed by an Argentine that Peter knew. The site was not done in any type of content management system (CMS) but as custom PHP code. That worked fine for a few issues but scalability has become a major problem for Interlitq. The graphic design looked good for 2007. (Really, it did.)