We take a content-first approach to building websites. That means that one of the first things we'll do in a project is ask you for all the content you plan on publishing to the web. Here are a few reasons why.
Posts in Code
We took a few minutes to reflect on what was 2008, and what is 2009. Among the upcoming events are DrupalCon 2009 and a barrage of new work for the portfolio.
The Aten Design Group website has a new look, new copy, and new technical platform.
Earlier this week I was able to release the first supported version of the YouTube API module I've been working on for the last couple months.
A few weeks ago I wrote a short how-to on allowing various roles to view unpublished content without having the 'administer nodes' permission in Drupal 5...
A couple weeks ago we received a call from a client who was having problems giving content editors access to nodes which were in the unpublished state.
Website owners and managers need a simple way to edit the text within their websites. They need to add headings, make bold text, bulleted lists, and so forth. It's a fundamental need in Content Management implementations, and perhaps the most used feature of any CMS.
In spite of this, the solutions widely available today are horrible.
Two years ago we began working with Drupal. Before then, our content management implementations were dominated by our own PHP/MySQL-based CMS, which itself was the result of several years of development, revision, and rewriting. Since we began working with Drupal two years ago, we haven't launched a single project using our own CMS. And we never will again.
Aten Design Group seeks a talented Flash developer to assist in creating rich online experiences. Projects will include online games, product configurators, interactive mapping applications, and more. Our clients include some of the world's best known non-profit and cultural heritage institutions.