Another Juiced.GS has been delivered to the printshop, though not without enduring some challenges. I once again had to struggle with a wonderful problem: too much content.
Each print issue of Juiced.GS has to be a number of pages divisible by 4. (That's what you get when you print on both sides of an 11" x 17" piece of paper then fold it in half.) We've decided that the minimum number of pages is 20, and the maximum (which we've achieved only once in our 86 issues) is 28. So most issues are either 20 or 24 pages.
The geography of the magazine is such that many pages are already spoken for: the front and back cover, my editorial, and DumplinGS, for example. That can account for as much as 25% of an issue, with the remainder filled with roughly six articles.
Some of those articles, I pitch to staff writers or freelancers; other articles are pitched to me. Unless it's something we've already covered, I rarely turn down a pitch. Some articles are short one-pagers; others require multiple diagrams that span five or six pages.
And that's what happened this issue: we had so many great pitches of substantial content that, by the time everything was loaded in, the issue was clocking in at 29 pages. I had to delete 1, 5, or 9 pages to get this issue to work.
Making that decision means asking, "What articles must run this issue?" Some topics are time-sensitive, whether they're reviews of new software, coverage of recent events, lead-ups to KansasFest , or series that need to conclude before year's end. Once I answered that question, it became apparent that we had six articles that had to be published in June, and four that could wait until September, resulting in a 24-page issue.
Of course, I could've run some of that "extra" content in June, making for another massive 28-page issue. But there are two downsides to doing so: it bumps the magazine into another postage class, requiring additional stamps; and it leaves less content for us to publish in the fall. By holding content back until September, there's that much less work to do in the short month between when KansasFest ends and when school begins .
There's one other consideration when making content decisions: the writers. How will they feel when their articles, which I gave them deadlines for, are not published when promised? Fortunately, I have never once encountered any tension or pushback. Every Juiced.GS contributor has attached no ego to their publication date, recognizing that these decisions in no way reflect the quality of their submissions. I am grateful for how fully they understand and cooperate.
I don't expect this issue to be the last time I have to make those decisions: with KansasFest 2017 being sold out , our community is growing, and with it, the number of helpers and contributors. I don't see a need to change our format or processes to compensate — to put it in KansasFest terms, we don't need a new venue with a bigger capacity . Instead, we can promise that we'll continue to be curators who work with writers of all experiences and skill levels to deliver the best content we can find.
Enjoy the issue — it hits the USPS on Wednesday!