Every January, New Year’s pledges empower hoards of resolutionists to buy gym memberships. Machines and weight rooms are always crowded in January, but attendance tapers off once tired gym-goers lose their zeal for resolutions and dumbbells.
This week, Acquia’s digital marketing team is tackling content migration, which means we have entered the “New Year’s gym membership” stage of website redesign. Content migration is the first time a majority of our team is using the Drupal 8 user interface. Our processes are sharp, and we are making pledges not to use and abuse the new site.
However, will this mentality survive once the new Acquia.com starts to feel less new? After spending a week in the trenches, here are three takeaways (we hope) will prevent site burnout down the road.
1. Become a Jack of all Trades
Our content migration assignment involves moving six years of content to a new site. This requires all hands on deck. Every member of the digital marketing team, from our vice president to content authors, analytics managers and front-end developers, is lending a hand. The obvious benefit is that many hands make light work.
It also means content creators have direct access to teammates who know how to navigate Drupal 8’s UI. This is important because when content authors feel confident about entering and publishing content on site, they are able to craft better resources for site visitors.
On our current site, Acquia’s content team uses Drupal every day. Publishing blogs is a self-sufficient process. However, we let our web counterparts push case studies, eBooks, or product datasheets live. Content migration has changed this.
Having to migrate a large volume of content has required every digital marketing team member to learn how to work with new content types in the Drupal 8 UI. Our front-end developers kicked off the process with an onboarding session, and taught us how to use Drupal 8 to create eBooks, case studies and data sheets. They also shared an 89-page, step-by-step guide.
Takeaway: As we continue to grow with the site, it will be easier for non-technical teammates to publish content without extensive front-end help.
2. Start with a Clean Slate
To prepare for content migration, we have cataloged content by asset types, including:
- Case Studies
- Product Pages
- White papers
As we started to migrate eBooks and white papers, the team noticed that there is little differentiation between the two asset types. Collateral uploaded under either classification is pretty much interchangeable. We chose to consolidate these two asset types to increase content authoring efficiency and remove complexity for site visitors.
Takeaway: Consolidating these asset types will change the way execute our content strategy. By decreasing the number of content types on our site, we decrease the amount of technical debt.