Content is the people in a house.
Content is the artist in a venue.
Content is the team in a stadium.
Sure, you can have an structurally sound house or a state of the art venue. But, unless you're an architect or historian you're likely not there to see the building.
Likewise, unless you’re a developer or designer you’re not necessarily visiting a site to see how it was built, you’re there for the content.
As Drupal 8 nears release, we want to shift the conversation to explore how the content modeling experience can be more core to how the Drupal community is oriented.
Drupal may be a robust and expansive Content Management System, and we want to ensure that we as a community do not neglect the first most elementary reason for developing a CMS: content.
This panel has collectively worked for 15+ years within the sphere of Drupal ‘end user’ experience for Fortune 500 companies specializing in globally localized sites. Wearing many hats from Content Managers, Project Managers, Editors, Producers to Quality Assurance Analysts we will be bringing in examples from the frontlines of Drupal content management realities in order to improve our feedback loop pertaining to content between: the people who are developing Drupal core, the people who are building the sites, and the people who are using them.
As the web trends favor content APIs as architectural staples of decoupled, interoperable, integrated web systems that feed a multi-device future, good content practices at the ‘core’ are more valuable now than ever before to our cms.
- Log in to post comments