After several years of talking about and conceptualizing, and months of development, I’m proud to formally (and finally) announce the release GovPress, a simple, elegant WordPress theme for government.
Since we launched version 1.0 just a few months ago, it has been downloaded more than 30,000 times from WordPress.org by governments, nonprofits and educational institutions around the world.
For those who’ve been following our work on this project, the original iteration was called GovFresh WP, however, we renamed it GovPress for the formal release so that it met WordPress branding guidelines and could be included in the official WordPress theme gallery.
The entire process of bringing GovPress to market has been an amazing experience, getting feedback, questions and, especially, thank you notes from people all over the world. I’ve learned a ton about building a solid civic hacking project and will soon write more about this so that it may help others working through their own ideas.
Finally, I can’t thank Devin Price enough for all his support in making this happen.
GSA announced it has officially opened up its URL shortener Go.USA.gov to anyone with a .mil, .gov, .fed.us or .si.edu email address. The site lets users create trustworthy short .gov URLs on Twitter and other online services with character restrictions and was developed by the team behind USA.gov along with members of the Drupal community.
User activity will be monitored to better understand citizen interests and needs. According to GSA, more than 700 public servants across all levels of government have registered to use the service, and more than 3,000 URLs that have been clicked over 450,000 times.
Too often, dense writing, confusing acronyms and fancy jargon bog down government websites. Hereâ€™s how to use plain language to help your customers find what theyâ€™re looking for, and save your agency time and money.
I’m all for the “clarity in government” objective of PLAIN (Plain Language Action and Information Network), the folks who maintain plainlanguage.gov.
I fully understand and support the need for PLAIN’s lofty goal of “Improving Communication from the Federal Government to the Public,” but don’t quite understand the need to create an entire Website to achieve this.
While I may be simplifying this effort, it seems to me a better approach would be to make Strunk and White’s classic The Elements of Style required reading for all federal government employees.
By October 1, 1998, use plain language in all new documents, other than regulations, that explain how to obtain a benefit or service or how to comply with a requirement you administer or enforce. For example, these documents may include letters, forms, notices, and instructions. By January 1, 2002, all such documents created prior to October 1, 1998, must also be in plain language.
By January 1, 1999, use plain language in all proposed and final rulemaking documents published in the Federal Register, unless you proposed the rule before that date. You should consider rewriting existing regulations in plain language when you have the opportunity and resources to do so.
PLAIN defines plain language as:
Plain language (also called Plain English) is communication your audience can understand the first time they read or hear it. Language that is plain to one set of readers may not be plain to others. Written material is in plain language if your audience can:
* Find what they need;
* Understand what they find; and
* Use what they find to meet their needs.
There are many writing techniques that can help you achieve this goal. Among the most common are:
* Logical organization with the reader in mind
* “You” and other pronouns
* Active voice
* Short sentences
* Common, everyday words
* Easy-to-read design features
No one technique defines plain language. Rather, plain language is defined by resultsâ€”it is easy to read, understand, and use.
Is the federal government living up to the mandate?