Spending three days with some of the best minds working in the web today at Confab Minneapolis reinforced the fact that story is at the center of all we do, and it takes a coordinated effort to tell that story successfully in today’s complex world.

As content strategists we’re the ones who put the pieces together. We’re the storytellers in our organizations, and we need to make sure everyone involved in any chunk, piece or project knows where their role fits into the narrative.

Today’s publishing systems are extremely complex. Gone are the days of linear workflows and the control allowed by print. We need to make sure that we can speak the language of everyone who makes up our storytelling teams, from those who build the systems that put it on the web, the bots that help our users find it, all the way through to the analytics teams who measure our success.

Photo courtesy ConfabEvents.

The People

Jeff Eaton helped remind us that dev teams and content teams need not devolve into the Hatfields and McCoys. Scope always changes, features always change. The needs of both teams are valid. Take the time to understand how their team functions, what their main concerns are, and why they respond in a way you may find unexpected.

Also take the time to share why you’re coming to them, what you’re trying to accomplish and what you may need in the future. Once you see each other as humans with needs, you can help each other get the best result.

The Bots

So you’ve smoothed the path to get the story into the publishing machine. Will machines be able to understand and parse it? We all know that automation and aggregation are playing an increasingly important – and complex – role in today’s publishing systems. But getting our content through that system is someone else’s job, right?

Wrong. Sara Wachter Boettcher reminds us to make sure everyone working in the web should have a working knowledge of how all the web properties that work with our content or outside content that is pertinent to our message map out and how people use it. As content experts we can ensure that our content is structured and tagged as well as relatable and relevant. Now our story will reach our users.

The Numbers

Now that your content is churning through the machine and getting to your audience, how can you be sure it’s working? Our good friend, analytics. True, this is something else that feels like it’s not really “yours” to deal with. While you may not own it for your organization, it is a core competency you should have to improve the world for your users.

 Jonathon Colman reminds us that if you want to make a business case for what you do, you’ll need numbers. Want to show those controlling the budget that your work is worth a bigger piece of the pie? Prove it. Want to show how well your content aligns with core values and vision? Ensure that’s part of the success metrics. Want to know what to do when someone comes to you worried about bounce rate? Understand the context and what that metric is telling you. Understanding the story the numbers are telling will enable you to tell yours more effectively.

For many content strategists, thinking about analytics is a bit outside their realm of expertise – rather than thinking of eloquent phrasing, you’re thinking about APIs and analytics. Luckily, Michael King bridged the gap in his session on the poetry of SEO.

Social and search channels provide us with some of the best opportunities to hear what our users want. It’s up to us to make sure we’re listening. The tools that are being developed provide us with additional ways to spread out message. Meta data is really about making a good first impression. So we need to make it count.

The Reason

So, you may be asking yourself when you can just hole up and write again, and free yourself of all these constraints. That’s totally understandable. But you can’t have creativity without constraints. Paul Ford closed Confab MN by outlining this point, and showing us how artists live within the resistance of the materials. That’s why we have to care about all these puzzle pieces that make up our content strategy.

But remember, constraints can also create territories. Declaring that analytics isn’t in your job description will simply draw a line between you and the rest of the team. Not being a part of requirements gathering for the CMS update pulls you further from your team, and will ultimately impede your success. So reach across those boundaries, learn about your team and what they do.

Now, you can sit alone and write.

The end of Confab brings an interesting mix of emotions – somewhere between how you’d feel after completing a marathon or leaving summer camp: exhilarating, enlightening, inspiring, and exhausting all at once. It’s exactly this unique kind of high that keeps the repeat Confab-ers coming back year after year, and the newbies itching to experience the unparalleled Content Strategy Conference for themselves.

After three intensive days of learning, networking, and eating (lots and lots of eating…) at Confab 2013 in Minnesota, it’s easy to head back to the Real World and succumb to playing catch up and addressing day to day minutia. And yet, the empowering feeling of returning from Confab lingers and (hopefully) inspires us to make meaningful change within our work, our teams, and our organizations.

If this sounds a little emotional for a conference, that’s because it was. If you don’t believe me, just take a quick peek at the #ConfabFeelings backchannel. If one thing became apparent this week, it’s that content strategy is emotional business, and delightful content requires empathy.

Whether you attended Confab or not, there are almost certainly a few levels of #ConfabFeelings you must consider as a content strategist – below are a few of the overarching ones discussed at the event.

Ego & Prejudice

One of the core beliefs we are constantly emphasizing on the CMS Myth is that technology is nothing without the people behind it. Corey Vilhauer’s session, “Empathy: Content Strategy’s Hidden Deliverable”, drove home the notion that we need to shift our thinking from Content Strategy to People Strategy for our strategy to stick. As Corey explained, writing can be very personal and involves ego, and we must consider the needs, goals, and biases of the people creating our content, on top of the business and audience goals. He shared 5 considerations to make this happen:

1. Ask questions – even the tough ones. Get to know and understand the goals of stakeholders, contributor needs and skills, aspirations of the business and opportunities to connect with the audience further.
2. Be clear and concise – speak their language. Beyond the content we produce, we also need to think about making our processes understandable and relatable to the people that will follow them so they feel truly empowered to succeed.
3. Be deliberate. The inclination may be to FIX ALL OF THE THINGS – but pace yourself. Consider the relevance and necessity of your organization’s processes and methodologies before asking your team to follow, and look out for “vestigial legs”. Stop holding onto outdated or redundant methodologies and instead focus on providing the right tools for exactly what you need content creators to do.
4. Be sneaky – reframe the conversation. Kristina Halvorson and Jonathan Kahn emphasized this point in their talks as well – as content strategists, we are also salespeople. You have to be ready to direct the conversation to speak to the personal goals and needs of the people you’re selling to – your team. Speak to the resistors, play to the team’s strengths, and adapt roles to work with your people.
5. Enable process and growth. In addition to salespeople, we are teachers – we have to empower our teams to sustain the strategy we put in place.

Confusion & Helplessness

We spend a lot of time developing our personas and creating journey maps to guide our content structure and strategy, but often we forget that the systems we create for are a major factor. Sara Wachter-Boettcher’s talk, “Write Like a Human, Think Like a Robot”, reminded us that the systems we use aren’t perfect, and the ‘bots need our help deciphering and filtering content. In a handy “Robot Logic Style Guide”, Sara noted a few considerations for showing a bit of robot empathy.

Structure: The structure should match the mental model of your users, and make sense to them inherently.

Metadata: Metadata is not just useful extra info for the ‘bots, it’s relevant for users, too. Consider the descriptive, structural, administrative, or helpful instances where metadata might come up – but be careful not to overdo it!

Rules: Prioritize and structure content to develop “If this, then that” guidelines for your system, enabling flexible decisions across screens and channels. Every time you break your content into smaller pieces, you create a new opportunity for new rules – and new decisions for how that content should be used.

Transportation: Take your content and turn it into a product. Learn and leverage APIs to help your content “chunks” move and shape what you need your content to achieve (i.e. Yelp’s unique combination of user-generated, Google map, and proprietary content).

Context: Remember that data isn’t useful without context. It takes UI design, labeling, and explaining to bring meaning and new possibilities to the content you’re creating.

Patience & Enjoyment

“How can this be faster?” is often our default goal to make experiences better, but Margot Bloomstein’s session “Content Strategy for Slow Experiences” urged us to pump the brakes for a minute to reconsider the usefulness of a less urgent pace.

As Margot explained, frustration typically drives the perception of slowness, but creating purposeful slowness in experience can actually be enjoyable, if designed the right way (look at Disney World, with constant opportunities to learn and engage at every turn of the queue).

From Disney World to the digital world, creating a pleasant pace can help drive discovery, engagement and learning. Just as IKEA approximates the in-store experience of exploration on their website or REI encourages product comparison to enable smart customer choices, using content to set the pace in customer experience can be delightful and helpful.

Delight

While balancing the needs of content creators, audience, and systems can make the job of a content strategist feel more like a juggler (in addition to salesperson and teacher), the core foundation of content should focus on the user. As Jared Spool put it, “Content is whatever the user needs or wants right now – whatever that may be”, and content is at the center of great experiences.

While great design always looks simple (and should be invisible, as Jared noted), the work required to create great content experiences forces focus on interaction design, visual design, information architecture, and content strategy. The balance of all pieces should help tie customer experiences to business goals, such as the Zappos return policy, which delights customers and stakeholders alike.

We need to change our mantra from “creating useful content” to “creating delightful content”. Not only does bad content hurt the business, but it hurts users. Delightful content creates real value.

Years ago we worked with an individual who was promoted into a senior role overseeing digital at a very large global company.

He was a dynamic leader with big ideas about how the web could change the organization, increase sales and improve customer experience.

However, soon after taking the reins of the existing operations he found himself saddled with legacy websites and platforms that had spiraled out of control over many years.

By his count the organization had 10,000+ different websites.

Not 10. Not 100.  Not 1,000.

10,000.

Web teams get maxed out running a single site, let alone 10,000. So, what’s a newly minted global web leader to do? Establish a new governance structure? Implement a unified CMS? Run for the hills?

He had a different idea.

“I’m going to shut down all the servers and only turn the sites back on if someone notices,” he announced.

The idea was bold, brilliant, and perhaps necessary.

While this may be considered the nuclear option, digital sprawl is a huge problem. Content strategists call the process of fixing it eliminating the ROT (redundant, outdated or trivial content). It’s a problem in all organizations, but in large decentralized global companies the rot can be so widespread it can’t easily be tamed on a page-by-page or site-by-site basis.

Content audits can uncover a tangled mess of ad hoc microsites, landing pages, department sites, forms, vanity URLs, and content strewn across the Interwebs. And those are the ones you can find. Some haven’t been used for years, but worse, some are alive and well (and ranking well in Google).

There’s nothing inherently wrong for a large company to have many websites, so long as they have a purpose, are actively managed, and support a larger content and customer experience strategy.

Unfortunately that’s not usually the case.

Sometimes the best option may be to pull the plug on the servers.

This post is part of of an ongoing series on managing large web platforms. Join us on Thursday June 6 for a webinar on Wrangling Global Content Strategy 

Image Source:  Benesh & Associates

Managing a global web platform isn’t for the faint of heart. Dozens (or hundreds) of sites, localized and translated content, and a network of globally dispersed web editors are enough to make even the most seasoned digital professional sweat.

Join us for an upcoming webinar June 6, 2013 on Wrangling Global Content Strategy with Seth Gottlieb (Lionbridge) and Brian Payne (ISITE Design).

Seth and Brian will share their experiences working with large complex global web platforms and share insight on how brands are unifying their content, technology and localization strategies to deliver digital experiences at scale.

Key takeaways include:

• How to create and govern a global content strategy
• Understanding CMS in large-scale global environments
• How to navigate unified and decentralized models
• Keys to avoiding “site sprawl” as platform grow over time
• How to deliver more personalized global experiences

The webinar is being produced in partnership with Sitecore, ISITE Design, Lionbridge and Clay Tablet.

Register today to attend (and we’ll send you a recording of it after as well).

Hope to see you there.

Facts are simple and facts are straight
Facts are lazy and facts are late
Facts all come with points of view
Facts don’t do what I want them to
- Cross-eyed and Painless, The Talking Heads

What’s the difference between data and content?

If content, in the digital age, includes all the text and associated assets plus metadata, does that mean that all content is also data?

Is all data also content, or are there forms of structured data that we would not include in a content strategy?

I can think of a few distinctions people traditionally have made between content and data:

• Content is for humans to consume (across devices); Data is for machines to consume
• Content is loosely structured and creative; Data is very tightly structured and modeled
• Content belongs to the CMO; Data belongs to the CIO

Applications have highly structured data systems – specified down to the field level with high degrees of precision. (Such data is often exchanged or exchangeable via APIs or structured feeds of XML/JSON/etc. – it has to be readable by machines not humans).

Content, on the other hand, needs to resonate with end users. Content resists structure. Like people, it’s highly variable and resists being forced into templates. (Note how easy it is to personify / anthropomorphize content, which you can’t easily do with data).

Arguably, content management systems are essentially interfaces wrapped around databases, to make it easier for humans to manage data.

Does this ultimately mean that data is from Mars and content is from Venus?

I want to tread carefully here. I was a graduate student in literary theory in the 90s as John Gray’s work was becoming popular. I found it horribly essentializing - glossing over the complex social construction of gender with simple platitudes and metaphors.

But there is a real historical gendered context here – data has been the realm of IT, content has been the realm of marketing. It should not be surprising then that we see way more women as visible leaders of the content strategy community – and that the developer community behind CMS’s has been more broadly male. (Of course there are great exceptions in both cases).

What difference does it make?

Perhaps the most important challenge in 2013 is the goal of structured content, future-friendly content, adaptive content, and content everywhere.

Does this mean ultimately learning to treat content more like data?

In Karen McGrane‘s keynote at Drupalcon, she argued  that our job is to create new tools and interfaces that reflect new mental models.   We need to make CMS platforms that create a different tradeoff. Rather than providing perceived short-term ease-of-use via things like WYSIWYG editors and editing-in-place, which reinforce the assumptions of content creators carried over from earlier platforms, we need to create interfaces which highlight the structured, data-like nature of content.

The web is not print; digital creates the possibility of content separate from its manifestation in a specific format. Content can finally become data in the fullest sense.

The real challenge, I believe, is how do we avoid losing what made it content in the first place – the human, narrative, contextualized, lumpy, unstructured part of what makes content not data.

Or is the very existence of something about content that isn’t data itself a residual, essentialist concept we need to abandon?

For Mythbuster May, a bad pun about one of the key challenges for content managers, and one of the main themes of all the various CMS related conferences: mobile, or more accurately, multi-channel multi-device content publishing.

How often have you clicked (touched?) a link, only to be either: a) sent to the mobile version despite being on a desktop, b) sent to the “full site” version despite being on a mobile device and finding no mobile-friendly experience, c) sent to a “please download our mobile app” interrupt, sometimes with no way of getting around it to the page you requested, or d) sent to a “content not available in requested format” style page.

Our platform assumptions are getting in the way of our experiences, a feeling Bob sums up well:

Bob Dylan – Stuck Inside Of Mobile With The Memphis Blues Again from kovacsmaff on Vimeo.

The song is full of references to content that for one reason or another just can’t get its point across:

Oh, the ragman draws circles
Up and down the block
I’d ask him what the matter was
But I know that he don’t talk

And:

Well Shakespeare he’s in the alley
With his pointed shoes and his bells
Speaking to some French girl
Who says she knows me well
And I would send a message
To find out if she’s talked
But the post office has been stolen
And the mailbox is locked

And my favorite:

Now the preacher looked so baffled
When I asked him why he dressed
With twenty pounds of headlines
Stapled to his chest

How many sites have you run across which seem to have 20lbs of headlines stapled to their chests?

The refrain reminds us all that we’ve been here before – we’re stuck in a single platform:

Oh, Mama, can this really be the end
To be stuck inside of Mobile
With the Memphis blues again.

OK, so he doesn’t actually say “with the CMS blues again” but it is what I sing every time I hear it. Now, hopefully, next time this happens to you you’ll find yourself saying (sometimes out loud) “Oh, Mama, can this really be the end . . . ”

Last week, hundreds of content management system users, developers, designers, administrators, and strategists gathered in Evanston for CMS Expo 2013. CMSX has its roots in the local user group community, which makes it feel more like a multi-platform user group meeting than a vendor-driven sales conference. It’s like a DrupalCamp, WordCamp, and Joomla Camp all ended up at the same hotel, which makes for some interesting cross-platform discussions. John and Linda have also really made big strides in shifting the conversation to include not just the platforms but also business strategy and content strategy. This directional change was even more in play this year, with fewer small track sessions in the am and more large sessions attended by the whole audience.

The major theme this year was the arrival of mobile, and how the impact of mobile goes well beyond just responsive design: structured content, content strategy, adaptive content, reactive technology were all discussions stemming from this root.

Many of the highlights were those I had expected:

• Margot Bloomstein (Cart, Meet Horse)
• Jeff Eaton (Prepare for the Mobilacalypse)
• Sarah Beckley (How to Future Proof your Business Content)
• David Aponovich (Five Secret Weaknesses of your WCM)

There were also way more sessions I wanted to go to but couldn’t, including: David Hobbs, Avery Cohen, David Skarjune, Scott Liewehr & Robert Rose, and many others.

One unexpected highlight for me was Kevin Drew Davis‘s keynote, which was a model of clarity and vision without getting bogged down in technical details. He touched on the importance of Star Wars (the first one, now retroactively known as Episode IV) as the first presentation of a “used future” in which the world wasn’t all shiny and new. (Though the Star Wars geek in me was tempted to remind the speaker that Star Wars is technically set in the past not the future). We tend to keep thinking that when the next new thing comes all the old things stop being valuable, or that at some point we’ll stop inventing more new platforms and formats, but instead these new things just accrete. We add more devices but we’re reluctant to give up old ones. We need to stop thinking of our users as using “a” platform and recognize all users use multiple platforms in multiple contexts.

I also really enjoyed Jen Kramer‘s take on “reactive technology” – her attempt at a buzzword to replace “responsive design” and try to bridge the gap in understand that responsive suffers right now (in that it means something very specific to developers but business owners haven’t yet really understood all their options for mobile). Her mode of presenting the variety of options (from mobile sites to adaptive options to responsive and potentially mixtures of all of these options) helps back out of the “responsive design is the answer to all mobile problems” mentality that can result from a superficial discussion.

WordPress was well represented this year, on the multi-cms “can your CMS do this” and “can your CMS do that” panels as well as through a series of presentations by:

• Aaron Holbrook (WordPress is a CMS)
• Lisa Sabin-Wilson (Exploring Multi-Site, Creating Community)
• Jake Goldman (Publishing Workflows and Tools)
• Me (Beyond Posts and Pages, We’re on a Mission)

Meetup Monday even included an appearance by WordPress lead developer Andrew Nacin talking about what’s upcoming in WordPress 3.6.

While it’s certainly important to recognize that selecting a platform is just one part of the broader content management problem opportunity (see the selection myth), it’s also very valuable to be at a conference like CMS Expo and interact with people beyond the tribe where you spend most of your time. If you work on a specific platform (as a developer, designer, consultant, or client) it’s incredibly valuable to see what solutions other platforms rely on as they face the same challenges.

DrupalCon 2013 in Portland Oregon is right around the corner! I’m so excited for my talk: “So Happy Together (Content Strategists and Project Managers Are)” on Wednesday, May 22^nd at 10:45AM.

During this session we’ll discuss how much we CMS Mythbusters respect and appreciate the rapidly emerging discipline of content strategy. Ironically, after all these years building CMS driven websites, there is one thing we still wish people were more aware of: content matters. Sounds silly right? After all, the ‘C’ in ‘CMS’ stands for…Well, content.

However, project stakeholders are often so wrapped up worrying about technical risks or marveling over new designs that content can nearly be forgotten or worse…Treated as an unimportant ‘detail’ to be figured out later (queue Lorum Ipsum).

Content Strategy Meets Project Management

We’ll take a look at tools of the trade in content planning and strategy, discuss when and how to integrate content strategists and some of the consequences of ignoring this important aspect of designing and building new web properties. We’ll also be handing out *exclusive CMS Myth prizes* so you won’t want to miss this one!

P.S. – If you’re a regular CMS Myth reader and you recognize the title of this session, your eyes are not deceiving you…It’s based on a blog post I wrote last year.

As the folks at CERN recently celebrated, it was twenty years ago that the core technologies and standards of the world wide web (including code for a web server and a line-mode client) were officially placed in the public domain. Tim Berners-Lee’s invention, designed to enable researchers to share research documents across multiple computing platforms and formats, would quickly outgrow these academic beginnings to become a global force for business and social interaction.

It helps to remember this history, though, as we still struggle with one of the fundamental assumptions of early HTML (and its predecessor SGML):

Content has its own internal structure separate from the specific presentations which might be made of it.

This core notion of separation of content from presentation has been a challenge ever since. We just can’t seem to come to grips with the notion that the web is different than print, and that rather than trying to control the output across device types, contexts, and users, we ought to aim for flexibility. (In the 10 years between John Allsop’s The Dao of Web Design and Ethan Marcotte’s Responsive Web Design, the majority of the industry – with some notable exceptions –  largely fell back into a pattern of fixed page designs for the desktop browser).

Enter Content Strategy

While the approaches like progressive enhancement, adaptive web design, and responsive web design have helped the situation significantly, by helping realize the goal of flexible presentations rendering reasonably on various devices, form factors, and contexts, they only account for content presentation.

Content strategists, most notably Karen McGrane (Content Strategy for Mobile) and Sara Wachter-Boettcher (Content Everywhere) have forced us all to recognize that without structured content – without forcing the content management systems and strategies we’re dependent upon to recognize, capture, and make use of structured content – we can’t ever truly be prepared for a world of adaptive content. The apparent flexibility of the WYSIWYG blob in fact prevents us from realizing the best presentation for each context; if we want true flexibility, we need structured content.

Content Blobs

WordPress has often been the poster child for – or represented the anti-pattern of –  unstructured content. McGrane wites:

If your organization is using a blogging platform like WordPress as its CMS, you know what this looks like. Content creators get one big field for the body of their content, and it’s like their own personal playground.

WordPress’ focus on a WYSIWYG authoring experience and the legacy of posts/pages has been loved by authors and content creators, because it allows a great degree of flexibility, or what authors see as flexibility. In fact, one of Matt Mullenweg’s favorite features in WordPress is “distraction free writing mode” in which everything but that “one big field” disappears into the background.

That apparent flexibility, however, comes at a longer term cost because the content it captures is not structured. What WordPress stores in the database is a messy melange of plain text, html markup, references to images and other assets like files, headings, sub-headings, paragraphs, and “shortcodes” which are specific snippets of text designed to be understood by plugins and transformed on display into consumable html.

WordPress plugins, themes, and templates can and will impact the presentation layer, adding styling onto that markup and processing shortcodes, but their ability to have structured, regularized, programmatic access to specific parts of the content (in order to execute rules) is very limited, because of the flexibility allowed to the person inputting the content.

Making WordPress Chunky

It doesn’t, however, have to be this way. If you have a content model, WordPress can be made to respect that model and provide interfaces for content creators which encourage require structured content and rich metadata.

Some basic structure and metadata are already built in, of course: title, body, excerpt, author, categories, tags, featured image, and (depending on what plugins you’ve elected) SEO-related metadata. Setting a featured image, for example, stores a specific relationship between the post or page and the media asset that can be presented different ways in different contexts: often, the featured image is included with the excerpt on list style pages in a smaller size, and becomes a hero image on “single article” type pages.

WordPress has also for a long time also allowed the notion of custom meta data, which requires some content modeling and some development, but enables users to add specific fields to content entries representing specific parts of the structure. For example, it’s a trivial exercise to add a subhead in addition to headlines, or to add a “pull quote” field to be treated visually in different presentation contexts. (Although it’s called custom meta data, and stored in a post-meta table, such information doesn’t have to be “metadata” in the purist sense; it can also be part of the content itself).

For $100 off a three-day conference registration use code CMSX54417

Beyond Posts and Pages

This is where one of the talks I’m giving next week at CMS Expo in Chicago comes in: Beyond Posts & Pages – Structured Content and Content Types in WordPress.

Since version WordPress 2.9 (which is to say since late 2009), WordPress can not only be made to think about posts and pages in a chunkier fashion, and to gather richer metadata about the content it is being used to manage, but to create and manage other types of content. Developers have the capability to create custom content types (which WordPress refers to as custom post types, often abbreviated CPT). Sites managed in WordPress can leverage a fairly rich content model, including multiple custom content types, different custom taxonomies for each of those content types, specific meta data or content chunks for those content types, and even (via plugins) relationships between those content types.

In the talk I will walk through a specific example – a site built during New England GiveCamp a few weekends back by a small team for a non-profit focused on encouraging youth understanding of and participation in civic action. We’ll cover:

• Registering (which means “creating”) a custom post type via theme or plugin
• Template hierarchy and styling custom post types
• Custom taxonomies and permissions
• Custom fields and meta boxes for adding/editing them – controlled vocabulary or free form
• Secondary HTML content areas

I will also discuss some of the limitations and challenges of doing complex content types in WordPress: search, alternative outputs, and relationships. It’s definitely a WordPress specific talk but many of the core concepts we’ll be discussing will be helpful for those modeling content in other platforms as well.

This month is a busy one for the CMS Myth team — from Philadelphia to Chicago to Portland, the Mythbusters will be out in force! The CMS Myth will be represented at J. Boye, CMS Expo, Drupalcon, and WebVisions, as John mentioned last month.

I took a minute (forty, actually) to pick the brains of some of our favorite Mythbusters on where they’ll be, what they’ll be talking about, and what they’re looking forward to at the conferences they’re heading off to.  Check it out in the G+ Hangout below:

True, I won’t be out and about this month, but I’m eagerly awaiting my turn to get to Confab Minneapolis, which is just a month away! In the meantime, I’ll be brushing up on some new reading and continuing to head up the Team Content charge back in Beantown.