
Between 2011 and 2017, I did content migration with HCA Healthcare’s Web and Social Media Product Development team and TriStar division. This has involved moving website content – text, images, widgets, etc. – from old content management systems to new, and then from old web implementations on the system to new hosts, using design guidelines made by the core development team and designers.
Having been directly and indirectly involved with 700+ websites, I’ve learned both the intricacies of dotCMS and gained insight on the process of upgrading websites over several years. New websites that I implement are strictly modern standards compliant, from image file sizes to CSS semantics to the kind of markup used in code.
Examples
Old pages, like the above landing page for a regular health magazine, would undergo dramatic changes in layout in the process of migration. I like to think of this as visual re-interpretation: using the tools provided by the modern framework, I would determine how best to present the old content in an updated way and work with the design or development teams, when necessary, to produce a desirable result.
The new version of the page. There are updated images, an updated form, and overall new structure that relies on Twitter Bootstrap content components rather than images and tables.
Consumer-facing healthcare IT is very concerned with user experience. Having clean, accessible, easily-navigable websites contributes to the ultimately goal of wholly facilitating the needs any patient — both existing and potential.