If you’re a program manager or a federal web developer you’ve probably been given a seemingly simple task: Create a basic website as part of a new initiative at your agency. The hardest part is often not crafting the content or designing the prototype, but getting the security and privacy compliance in order to launch and maintain the actual website’s compliance status. For that work, you might have to hire a contractor or put extra strain on your agency’s web team.
Content Management System
Related Event: Create Once, Publish Everywhere Applied—HHS Content Models and Portability, Tuesday, April 18, 2017; register here. Create Once, Publish Everywhere (COPE) The U.S. Department of Health & Human Services (HHS) is sharing its content models and their related Drupal features for you to use on your sites. A content model is a representation of types of content and their inter-relationships. Content modeling takes content items and breaks them down into smaller structures, called content types.
We’re excited to launch a complete redesign of USDA.gov featuring stronger visual storytelling components, a more modern user-experience with easy to find services and resources, and to top it off, a completely mobile-friendly design. Through careful planning, thoughtful design, and a primary focus on user experience and usability, we’ve taken the best of government and industry expertise and put it into creating our new website. This has been a year-long project, but to do this right, we wanted to make sure we tapped into every possible resource.
Here at DigitalGov, we generally focus on federal governmental digital efforts within the U.S. It is where we live and operate, so it makes sense, but many governments across the world struggle with the same issues and leverage technology as a common solution. When I came across an article where Australia announced its “government as an API” platform was available, it seemed like a great opportunity to see how another country is tackling structured and open content.
Recently, I shared some suggestions and personal lessons learned for agencies either shopping for a new CMS or preparing to revamp their content strategy and workflow. Let’s take things one step further and focus on arguably the most important parts of your CMS: the content creator or user. Arguments can be made that content is the most important, but the user creates that content, so either way we have a tight first and second most important ranking.
These days you couldn’t be faulted for thinking your content management system (CMS) choices are limited to two open source systems and maybe an enterprise-level offering that no one uses anymore. And while it’s true that for the public sector the popular open source options are extremely attractive from a cost standpoint, if nothing else, the CMS marketplace is as full of options as it ever has been. So whether you are shopping around for a new system or looking to revamp your current one, there are a variety of items that need to be considered as you examine your CMS options.
Smartphones make up 75% of the mobile market—which makes mobile-friendliness a must for government agencies. With the recent update to Google’s search algorithm, or what some are calling Mobilegeddon, the case for building a mobile-friendly site becomes even stronger. For many government organizations, responsive Web design (RWD) has been the answer to their mobile question. While RWD is by no means a panacea, it can provide agencies with a way to reach their customers on many devices with one site.
Park websites on NPS.gov from A (Acadia) to Z (Zion) are now mobile-friendly. Visitors using phones and tablets to visit national park websites now have a user-friendly experience to enhance their virtual visits. Previously, visitors using mobile devices saw a smaller version of the website scaled to fit the size of their screen. Now, the content will adjust to fit small screens while providing the same functionality available to those visiting the site using a desktop or laptop.
Metadata for website content is usually managed as part of the editorial process when documents are created and published with content management systems. There may be another source for this metadata, especially in regulatory agencies: internal databases that reference Web content in support of record keeping processes. These databases may contain public and non-public information that were never meant to be published for public consumption. “Metadata” is not typically how the content is described.
Imagine a world without Web pages, only intelligent, self-assembling chunks of content waiting to respond to your needs. The page is irrelevant, there may be no context beyond what is included in your content. The content has to survive on its own, perform its goals on its own. Originally when creating content, you would take into account the things that surround it on that page; they give it additional context and relevance.
DigitalGov University has hosted some great events over the last year in partnership with Data.gov, the MobileGov Community and 18F to bring you information on opening data and building APIs. This month we’ve rounded up the events over the past year so that you can see what’s been offered. Use the comments below to offer up suggestions on what else you’d like to see on the schedule.
Rome wasn’t built in a day. Neither are website redesigns. In line with the piecemeal responsive Web design implementation trend we recently highlighted, the new Ed.gov website redesign happened in three phases. In this case, budget limitations and existing content management systems (CMSs) influenced the decision-making process. “We use three different CMSs,” said Jill James, Web director at the Department of Education. “We timed the phases of our redesigns with technical upgrades that we needed to do anyway.
When websites were first created back in the 1990s, developers perfected their skills designing sites that presented content in an attractive and eye-catching manner. Content was completely contained within the four corners of the site. With the rise of Web 2.0, content creation became easier through blogs, wikis, and microblogging. Even so, content was still attached to that particular content creation tool. Content management systems (CMS) freed content from presentation.
Most of us in the DigitalGov community recognize that responsive Web design is one approach to mobile first and most of us have a pretty clear picture of what it means—a responsive website will adjust to different devices, and the content will neatly change its layout from one screen size to another. But do you know how it happens? Would you know how to implement responsive Web design in your agency?
As traffic to desktop .gov websites declines, how we publish our content increasingly matters. We need to meet people where they are as they seek information on the Internet. To do so, we need to adjust to the new world of mobile applications, social media, and instant answers provided by search engines. Freeing Content from Our Websites In this content sharing era, it is important to separate the content from how it appears on your site.
Why Invest in a Content Management System? Does it take too long to update and post digital content? Do you lack consistent branding across your website(s)? Is outdated, redundant content leading to a poor customer experience? Does your agency website show up too far down in search results? Are you re-creating the same content for different platforms such as Web or mobile? A content management system (CMS) can address these issues and significantly improve how your agency delivers and manages digital information—positively impacting your bottom line.
Improving the federal government’s ability to deliver digital information anytime, anywhere, on any device—via open content—is a key goal of the Digital Government Strategy. A content management system (CMS) can help your agency move to an open content model, making it easier for people to find, share, use, and re-use your information. The key steps in getting ready to move to a CMS include: Prepare Your Content Choose a CMS Migrate Your Content to a CMS Prepare Your Content Develop a Content Strategy A content strategy defines such things as topics, themes and purpose, and can also play a part in website governance, customer experience, metadata and search engine optimization (SEO).
Wikipedia says that structured content refers to information that’s been broken down and classified using metadata. It can also refer to information that’s been classified using XML or other standard or proprietary forms of metadata. The National Institutes of Health’s National Cancer Institute (NIH/NCI) move to structured content has allowed them to easily deliver their content anywhere, anytime, and on any device. The Challenge The National Cancer Institute (NCI) has a huge base of information on cancer treatments that is continually updated.
A case study on how the Department of Education used the Drupal content management system (CMS) to publish press releases as structured content to automatically generate listing pages and reduce errors and posting time. The Challenge The Department of Education was posting press releases using a system that posted them as static HTML files. The site design required press releases to be linked from several different pages, but the system was not designed to create those links automatically.
A case study on how NASA is choosing a new enterprise content management system (CMS). The Challenge NASA.gov needs a new enterprise CMS. They’re facing issues such as software obsolescence, inconsistent website governance, and a large amount of unstructured content stored in flat HTML files. Their current system is almost a decade old, and the vendor no longer provides technical support. They need an enterprise solution that will enable offices throughout NASA to collaborate on content creation, instead of having each component create content in isolation.