Archive for the ‘Core Concepts’ Category

Template Data – Part 3: The Newspaper Drop

Thursday, October 29th, 2009

Of all the data you’ll use to build Hot Ink templates, probably the most important is the data associated with your newspaper itself. The “newspaper drop” is available and contains the same data on all templates and no matter what the context.

To learn more about Liquid, the templating language used by Hot Ink, read the Liquid wiki at http://wiki.github.com/tobi/liquid

Your newspaper’s drop is the main piece of data used for building your template’s structure. If you’re interested in fleshing out your template with a little more data, be sure to take a good look at what’s inside this drop. We’re still adding new features to the site, so look forward to this drop expanding significantly over the next few month.
(more…)

Template Data – Part 1: The Article Drop

Thursday, October 29th, 2009

When working with Liquid, the Hot Ink templating system, each type of object (like an article, a mediafile, an issue or even your newspaper itself) has data associated with it that’s available for use in your templates. Which piece of data is available depends on which template your working in, but perhaps the simplest case is a Hot Ink article page template. On each article template there’s a variable called “article” representing the article requested by the user.

(more…)

Introduction to Website Design with Hot Ink

Thursday, October 29th, 2009

**This post is a basic introduction to using the Hot Ink templating system. You may recognize it as the introduction to the Hot Ink Publisher google doc some users have had access to. Others have contributed to this document (thank to all of you), I’m posting it here to give it a wider audience and to help answer some questions forusers new to Hot Ink.**

Publishing with Hot Ink is different from publishing with any other content management system. Hot Ink strives to make it possible for you to exercise the same kind of careful control over the structure, appearance and composition of your website as you do over the print edition of your publication. Because it’s so flexible, the templating system can be a little overwhelming at first. To help make it a little easier to understand by defining some key terms.

In order to be visible to the public, your website must have a design and it must be set to be your website’s current design.

A design is a collection of layouts, templates, stylesheets, javascript files and images that together define the complete visual
presentation of your website. You can have as many designs as you like, but only one of them may be current at any one time. The design
designated as current is the one shown to readers when they visit your website.

Designs control the appearance of your site using templates. Templates are dynamic HTML files written using a templating language called Liquid. Liquid is a simple, easy-to-learn addition to standard HTML that makes it possible to build complex templates that accommodate a variety of individual types and forms of content gracefully. For example, a well written Liquid template for your article page will display the article differently depending on whether the content is
horizontal or vertical, an image or an audiofile, has a subhead or no subhead. (more…)

The open source approach

Friday, April 24th, 2009
hotink_github_screenshot

Hot Ink's project page at github.com, a social open source development site

The first decision we made when starting Hot Ink was to keep the project “open source.” We mention it everywhere, so that’s probably no surprise. Maybe you’ve even heard of it before. So, you’re entitled to ask: what specifically does “open source” mean, and why should I care?

If you’re anything like me, the first place you’ll look is the wikipedia page.  That’s interesting, sure, but it’s also a little bit long and both too general and technical for our purposes. Instead, let’s keep it simple. To us “open source” will mean software development where the both final code and ongoing development are transparent (i.e. viewable and trackable online.) This is the opposite of traditional “closed-source” development, where only the final product is available and the code running it is completely hidden.

Open-source reporting?

A good way to understand the differences, from a software developer’s point of view, is to consider what it would be like to write a news article in an open-source environment. Currently, most campus newspaper articles are “closed source.” Reporters gather some primary and secondary sources, write up an article, then pass it off to their editor as a more-or-less complete package. That editor may have access to the primary sources but readers generally don’t. Readers get the final product, read it and live with it.

In an open-source reporting environment, the early stages would be very similar. A reporter would collect information from sources, write up an article, and then submit it to an editor for publication. However, readers would be given access to the reporter’s copy, notes and source materials. If a reader was confused by a clause in the article they could refer to the sources (or the notes) and determine the author’s true intent. Then, if the reader is motivated enough, he or she can update the story to read a little clearer. Expand this on a massive scale and what do you get? Wikipedia, more or less.

(more…)

Hot Ink - A vault to store your valuables

Wednesday, April 22nd, 2009

Campus papers spend a lot of time creating content. Your paper’s content includes all the articles and media created, edited and polished by staff for each issue and the design you dressed them up in for publication.

Try tracking how much content your paper produces for each issue. After a few issues, that pile will start to add up. After a few years, you’ve got a serious database representing the combined efforts of hundreds or maybe thousands of contributors. While this archive may be of little immediate value to newpaper volunteers, to editors it should represent a publishing tradition, a historical record and, who knows, maybe even a future revenue stream.

Maintaning that publishing tradition and historical record falls on the current management of your paper, typically its editors. That means a lot of former (and future) contributors are relying on your editors’ wits to protect a legacy they helped create. That editor might even be you.

Are you doing a good job? Try really thinking about it.
(more…)