More and more writers are becoming published authors. Some start with blogs, writers’ groups, and lifelong dreams. Traditional publishing can be difficult to break into, especially if you’re not already an established author. So how are new authors getting their books into the competitive market without an agent or a supportive publishing house?
Nearly a decade ago, ebooks were on the rise, and it was believed that this would lead to the imminent death of the print book. Some experts went as far as stating that the market for print books would plunge into oblivion. These prophecies turned out to be both true and false to some extent. While the market for ebooks soared at an unprecedented rate, the print book still holds its place with its head held high.
During my time at Ooligan, I have been told by multiple people that XML coding is the portion of the Ooligan workflow that they are most unfamiliar with and therefore most anxious about volunteering for. It’s not hard to see why XML seems daunting or confusing: the work is done by the editorial department, but it requires coding tags one would expect to see in the digital department, and the product is used exclusively by the design department. It’s easy to get lost in all of that. If the work requires coding, why isn’t it done in the digital department? If the product is only used by the design department, why don’t they do the work? To help clarify, here’s a crash course in XML.
While the first webcomics began popping up in the mid 1980s, the medium exploded in popularity starting in the mid-to-late 1990s. Numerous long-running series got their start around this time, many of which are still going strong over twenty years later.
I’ve known for a long time that I learn best through listening and through verbally discussing a topic. My favorite classes have always been the ones where the professor was a great orator, because it meant I could just sit back and absorb what they were lecturing on. All I ever needed to do was jot down some key words or phrases in my notes, and when I studied later the entire lesson would come flooding back. People thought I was crazy, but it worked for me.
Once upon a time, maintaining your portfolio meant taking hard copies to an interview or attaching them with your application. However, today most publishing employers prefer portfolio websites so they don’t have to worry about hanging on to (or worse, losing) the multitudes of work they receive from each candidate. But those of you who haven’t spent much time coding or building websites are likely wondering: Where do I begin? Well, look no further. Here are some tips to get you started.