CMS Website Guide

Our team specializes in building content management system (CMS) websites — from discovery to wireframing and design to content entry and administration. We build websites to fit your needs, moderate content after they launch, and continue partnering with you as your needs change.

Tell us what you need your site to do and say, and we’ll bring our expertise and experience to bear and make it happen!

Pre-launch responsibilities

Website creation team

  • Help define and/or refine the site’s various calls to action, audience, aesthetic, and markers of success.
  • Call kick-off meeting.
  • Create a schedule and monitor deadlines.
  • Create a RACI responsibility matrix that lists who is Responsible, Accountable/Approving, Consulted, and Informed for various tasks and stages of the website creation process.
  • Design, refine, and build the website architecture.
  • Train partner-clients on content entry and consult on entry progress.
  • Collaborate with partner-clients on editorial and image choices.
  • Collaborate with partner-clients on website testing prior to launch.

Website project partner-client

  • When putting in the project request, think about your goals for the site. Who’s your audience? What isn’t your current site doing, or, if it’s a brand new site, what problem will it solve? The Website Creation team is most effective when it has a comprehensive understanding of the problem(s) that need(s) solving.
  • Meet agreed-upon deadlines for wireframe and design reviews, content entry, and QA testing.
  • Respect the roles and responsibilities laid out on the project RACI, i.e. manage the feedback of those not listed there — no surprise stakeholders!
  • Enter content (editorial and, as needed, images) once content entry training is done.
  • Provide the web developer with the email addresses of people who should have access to enter and moderate content.
  • Create a plan to promote the website and its contents after launch.
  • Keep in mind (and give voice to) how the website might be used in the future so that the website creation team can build in functionality that allows for future expansion without major structural changes.