Beegit - Content Production and Collaboration Blog

What is Content UX and Why Does it Need to Be in Your Business Vocabulary?

Wed, 19 Jul 2017 12:00:00 +0000

What is Content UX and Why Does it Need to Be in Your Business Vocabulary?

Is content truly king or is user experience (UX) the way forward? For years, the battle has raged between content strategists and UX designers trying to claim the crown of most important to a business’ success. Well, we’ve got some news, an oligarchy is in order, wrapped neatly into a new package labeled “content UX” that can transform your website’s performance.

What is Content UX?

As alluded, content UX is the merging of two previously separate disciplines — content strategy and user experience design — to create seamless experiences across your website. But let’s start with the definition of both content strategy and UX design.

Content strategy is the creation, publication, and oversight of useful, usable content. For instance, it’s writing the blog post, publishing it at the correct time for your audience, and monitoring its click through rates, engagement, and link profile long after it’s published.

UX, in turn, is the process of enhancing user satisfaction by improving the usability, accessibility, and pleasure provided through interactions with your website. Examples include building helpful dropdown menus, adding a breadcrumb trail to pages, and categorizing or tagging blog posts, plus a whole host of other design elements that make your website easy to navigate, intuitive, and simple to use.

Content UX, therefore, is creating and publishing valuable and engaging content into a design where it can be found, easily digested, and accessed by users. It also means optimizing existing content to ensure that your published articles or landing pages aren’t buried in the sitemap or impossible to find.

These two fields already overlap in many areas, making a transition to content UX less difficult than you might imagine. To help you visualize, take a look at this user experience honeycomb, created by Peter Morville, that shows the key factors to consider in UX, each serving a unique purpose in website design.)

As you can see, at least four elements — useful, usable, findable, and credible — should apply to the type of content you are already creating. It’s then a matter of combining your content strategy with your UX plan at earlier stages to capitalize on the benefits of quality copy mixed with easy-to-use interfaces.

Why Does it Matter?

In today’s online world, simply pumping out blog posts and new landing pages won’t lead to ranking success, nor will a responsive website design or interactive interface garner favor with Google on its own. The two must go hand-in-hand.

Before you can create an easy-to-navigate content hub, you need content worth organizing. On the flip side, you may have some great content, but no simple way for users to find it. Think back to the honeycomb — when information is found (UX), is it useful (content strategy)? Is your article extremely credible (content strategy), but not accessible (UX)?

Knowing where and how your UX design and content intersect and relate is essential to good content UX. For example, if you want to add a “Latest News” reel to your website, but you only post a new blog every three months, UX can create a reel that disappears after 30 days and reappears when a new post is added, instead of having stagnant content sitting on your site.

If you remember one thing in terms of content UX, make it this: everything needs a purpose and a place to exist on your website. This focus on content UX adds value to user experience by positioning relevant and desirable information where readers can find it.

What’s Next?

When it comes to implementing content UX, your first move should be to understand your customer’s journey through your site and to find gaps in content. Whether you have amazing content that simply can’t be found, or have a point in the journey where users seem to be bouncing or leaving your site, it needs to be identified.

In successful content UX, the customer is king. Focus on a good user experience that follows unimpaired pathways and journeys, while adding value to their overall experience with engaging, relevant, and informative content along the way.

Woo Content is an international, multi-lingual copywriting agency based in New York, London, Sydney, and Singapore.

Beegit and Ad-Rank Media

Tue, 21 Feb 2017 12:00:00 +0000

Beegit and Ad-Rank Media

Ad-Rank Media is a content marketing agency based in London and Norwich. Over the years, we’ve built up a solid reputation for the quality of our copy, delivering high profile projects for some of the country’s biggest brands.

As our business has moved forward, our internal processes for managing the flow of content have struggled to keep up with our growth. While we’ve always been extremely confident in the ability of our writing team, around a year ago we decided to adopt Beegit as our content delivery system, and it’s been an absolute game changer.

Taking Stock

Prior to Beegit, we used a combination of Google Docs and Dropbox to manage the editing process. Completed files were uploaded by our writing team, and all edits that were suggested and consequently made were recorded in a corresponding spreadsheet before being sent over to the client for approval.

On the surface, this process was still relatively fast, even if our tree of files was fast growing in complexity. But, errors were hard to pin down. We discovered that a missing document or an incorrectly recorded edit could take hours to resolve, while managing the process of approval was a significant task in it of itself. The writing team also found it complex and distracting from their main focus, which is creating quality copy for our clients.

In total, we estimated that this administrative process was taking around five minutes per edit. Given that each piece was edited at least twice, this came to 10 minutes of admin time per page. At 300 pages per month, this equaled 50 hours — more than the working week of a full-time team member.

Transparency

With Beegit, this figure has been cut to virtually zero. Our clients now have access to the system, and can approve copy when needed. With less files flying around by email, mistakes have been considerably fewer. This has eased the burden on our content delivery managers, and given us more time to focus on work that adds value for our customers.

Reliability and Productivity

There have been other benefits, too. By creating files that mirror the structure of how the content will sit on a website, editing copy for repetition between pages has become easier, as has planning and understanding a customer journey. Meanwhile, the activity reporting tool has meant that we can quickly and accurately provide updates on delivery numbers.

The template option has removed a lot of room for error as well. We have found that this is particularly useful for freelancers or those working out of the office, who may have missed some of the more detailed communications regarding a project.

At the same time, we’ve worked hard to improve efficiency. By holding regular workshops and feedback sessions, our writers tell us what they need to make their tasks easier. Our content delivery managers are also continually refining our processes in order to increase our ability to produce at speed and scale.

Overall, we’ve been extremely happy with Beegit and the effect it has had on our business, even aside from the cost saving. Perhaps the greatest benefit has been the responsiveness of the Beegit team. Our questions have always been answered quickly and thoroughly, and our requests for new features are frequently implemented. Having this relationship is a real advantage, as we feel we have a platform that will grow and adapt with our company in what is an extremely fast-paced and competitive industry.

Customize your team's content workflow — and fonts!

Sun, 15 May 2016 12:00:00 +0000

A few months ago, we released updates to Beegit that helped improve the content production workflow for teams. In that release, we included some basic file statuses (Draft, Pending Approval, Approved) that help keep track of where a particular piece of content stands in its lifecycle. Although that works well for most teams, some teams with more complex requirements need the ability to create custom content workflows that better model their production process. With that in mind, we have further enhanced the file status feature to allow for custom content workflows! Here’s how it works.

Customizing project file statuses

In any of your projects, any project administrator can now go to the project settings tab, and then to the new file statuses tab
Inside the file statuses tab, you can create, rename, remove and drag ‘n drop the file statuses
Changing the file statuses for a project will only be visible to that project

That’s a great and pretty flexible way to represent your custom workflows on different projects; but what if you want all of your projects to fit a specific custom workflow? Enter default file statuses.

Customizing default file statuses

From your team account dashboard, any team administrator can now customize the default file statuses that will be present on any new project created in your team account.

On the team account dashboard, there is a new settings tab visible to team administrators
In the new settings tab, you can now create, rename, remove and drag ‘n drop the default file statuses, similarly to what is available on project file statuses
When a new project is created, it will contain the default file statuses that you’ve specified in your team account settings

Customizing font preferences

One last little thing we added in to help make the writing and editing experience just a little more pleasant is the ability to change the font in the editor. This is now a user preference that anyone with a Beegit account can customize for themselves. From your account preferences, you can set the font, font size, and whether to enable or disable the spell check feature.

That about wraps up or customization feature release – we hope that this added level of personalization will help make your team even more productive! If you haven’t been around for a while, now is a great time to log back in to Beegit and see why it’s the best team-based content production and collaboration tool on the web. If you’ve never signed up for Beegit, it’s the perfect time to start a free trial.

Five quick steps to creating a content plan that kills endless revision loops

Sat, 07 May 2016 12:00:00 +0000

Those of us who live in the world of content planning and production know that nothing slows down a project like the final stage of content revisions and approvals.

After hours of work putting just the right words in just the right order, there’s suddenly feedback from multiple people outside of the core production team. Many don’t even know why they’re reviewing the content, but, gosh darn it, they’re going to make changes and, frankly, they don’t like the way that one thing reads.

The screeching halt of the content production process can be heard across the entire office. The only solution is to get out of the content game, right? Maybe spend a few months on the open seas learning the fun names of the knots used by boaters.

Stop. Don’t jump on that boat just yet. You can put a repeatable content plan in place that helps you cut out the most terrifying loops of the revision cycle. It won’t be easy, but these five steps will make it easier.

Note: This blog was created from our recent presentation on content planning and production at a content strategy event. If you want to see the full presentation, check it out here.

1. Identify and clearly define team roles

You don’t always have complete control over the team involved in a content project, but you can control how the team is put into action. Whenever you are working on a content project, have a kick-off meeting where you convey roles and expectations for everyone involved.

Clarity is key to the entire content planning and production process. It’s your job to create a plan for your content project and define roles that help see that plan through.

Here’s the thing that we in the content planning world often forget: many stakeholders in a new website launch or a big eBook project have never been involved in a large content production before. If you don’t clarify how they should give feedback on content, they’ll just do what they think is best and likely make you sad.

Here are some common roles we use at NgageContent, our growth marketing division. By letting everyone know that other roles are covered, they worry less and can focus on what they need to do. Note that on smaller teams one person can have multiple roles.

Researcher — Finds internal and external facts, figures and materials for the content.
Copywriter — Writes the content and is responsible for consistency, language and tone.
Subject matter expert — Provides industry or organizational expertise.
Copy editor — Holds content accountable to style guide, grammatical and template standards.
Approver — Has the final say on content going “live.”

2. Lean on templates and style guides to avoid endless revisions

The unsung heroes of content projects are those of us doing the planning and writing, am I right? But our most helpful sidekicks are style guides and templates. They can really swoop in and save the production process.

That’s because there is no reason to have an endless revision loop over the use of a word or the styling of your headlines. From the outset of a content project, select what guides and templates you will use and make sure everyone knows that’s the plan.

For example, many companies use AP style on all of their content. Recently, our team of grammar nerds were all buzzing about the AP’s recent decision to finally jump into 2016 and stop capitalizing internet and web. If someone wants those capitalized on a content project, we point back to the style guide and say, “Hey, quit living in the past!” — or something nicer than that. (Ignore the fact that in the presentation above we say to capitalize them both — it’s from five weeks ago. My, how times have changed!).

Similarly, in-house templates and organization-specific style guides can solve issues.

Templates for content projects help everyone do a better job coloring inside the lines. By assuring them that every page on a site gets the same treatment or every blog has the same ending bio, people new to the content production world worry less. Even better, an in-house, organization-specific style guide can be a blueprint to keep everyone consistent. This guide covers things like how and when to use a company’s full legal name or what to call your CEO. To answer a question you might have, yes, these guidelines are extremely taxing to assemble. But go through the pain once and you will never again have an argument about whether you need a comma between a company name and LLC.

3. Centralize the team in an online hub

It’s 2016 and it’s time to demand that your content production process move to an online system that makes it easy for you to write, edit and track content from anywhere.

I don’t care if you use Beegit, Gather Content or, if you have a small team and are looking for something free, Google Docs. (OK, I’d prefer you use Beegit, but that’s not the point). The idea is that your online document flow lets everyone on the team know who last made changes and where the content stands. The old way of someone emailing a document around the office that called ‘ContentProjectFinalVersion8’ is rife with frustrations and slowdowns.

Don’t let your content get lost in a loop where someone says they are looking at something. Are they? With online tools, there is accountability. That’s key, particularly for those that are new to content production. Not only is this likely their first project like this, they probably have another full-time job and it’s easy for content creation and editing to fall off their radar.

Which brings us to the next tip…

Content always takes longer than you think and people are always running late. Give everyone on the content team very clear deadlines — and make their deadline well ahead of the planned completion date.

Make sure that everyone has their deadline in a very visible place, either in your shared content hub or in a tool like Trello or CoSchedule. Making a team plan that includes visible accountability for everyone involved will make life easier throughout the process.

There’s a bonus in doing your content planning this way: By identifying early on those stakeholders that fall behind, you’re not coming in like the Punisher on deadline day. Instead, you can see early on who is off track and have a conversation with them. From that, you might find that the reason they are struggling is that they overwhelmed by being part of the content process. Since you’ll be ahead of schedule, you’ll be able to help them swim to shore.

5. Get approvals on small samples of content

Let’s say the content plan is working and your early efforts to give everyone a role and a clear deadline have gone over well. Now, your team knows what to do and where to write. First, go ahead and wink at yourself in the mirror. You’re amazing.

Next, to avoid the last big revision meltdown, get buy-in from subject matter experts and final approvers early in the game. Don’t put all your wonderful prose together on day one. Tie together your big thoughts into small chunks of content or even just bullet points. Get approval on these core thoughts and then you’re really ready to run.

Again, if you have templates that fill up part of the content, agreement on what you are expecting from others and approval on the core ideas, you’re 80 percent of the way there. Now, go craft your narrative or add sizzle to that content in peace, knowing that you won’t have to start all over again on a new content revision loop.

Deep content search and improved commenting with resolved comments

Fri, 18 Mar 2016 12:00:00 +0000

Native support for inline comments is a critical component of collaborating during a content production cycle. It has been one of the most heavily-used features of Beegit since it was introduced, and we’ve recently released improvements to the commenting system that bring support for viewing the comments you and your team have resolved.

Closing out the comment feedback cycle

For each of your files, you can now view a list of all comments that have been resolved (along with their full replies thread), who resolved them and when, and what selected text the comment was attached to.

We are pretty excited about the improved clarity and accountability that this new feature brings!

Deep content search upgrades

The universal search box that searches across all of your projects and files has been a big hit. Originally, the search only searched across your filenames and not the content inside of your files. To promote content reusability and findability, we’ve updated the search to perform what we’re calling a deep search across all of your content. Now, your search results will report back to you where your search phrases are inside of your content files, with context, and provide you one-click access to open the file.

We hope you enjoy these exciting new features! If you haven’t been around for awhile, now is a great time to log back in to Beegit and see why it’s the best collaborative content production app on the web. If you’ve never signed up for Beegit, it’s the perfect time to start a free trial.

Updated version control system for easier collaborative editing

Sun, 24 Jan 2016 12:00:00 +0000

The version control system in Beegit has always been a core feature in the platform and a prime reason why a lot of our customers love the way we do things. We’re excited to announce big improvements to the version control system that make it easier, more accessible, and enable a whole new range of uses, particularly for collaborative editing.

Version history for files

Prior to this update, all of the version control action was in the “revisions” section and available across the entire project. There were a few issues with this, and after listening to a ton of feedback, we’ve moved all version control features completely into the files section.

Now, you can commit new versions and view the entire version history for a file right from the file itself. By opening a past version, you can quickly see:

What changed in that version compared to the version that came before it.
What the entire document looked like in Markdown.
What the entire document looked like in a rendered HTML preview.

Plus, there’s a 1-click “restore this version” button that will immediately restore the document back to the selected version.

Committing new versions

You can commit new versions of a file any time by using the “commit changes” option in the new “file actions” menu (the three vertical dots next to the filename and due date). Additionally, new versions will be committed for you automatically whenever the file status is changed.

If you’re committing changes manually, enter a note describing your changes the same as before and it will be used as a reference to that version. The “commit changes” screen also has a handy “view changes” tab so that you can see exactly the changes you’re committing.

Restoring past versions

The restore feature works in a “revert” fashion as opposed to a “rollback,” so that means if you restore an old version, you won’t lose any of the more recent versions that came after it. The restored version will be moved to the top of the version history, and everything in between is still there for you.

Collaborative editing using the new version control system is easier than ever. If you haven’t been around for awhile, now is a great time to log back in to Beegit and see why it’s the best collaborative writing app for the web. If you’ve never signed up for Beegit, it’s the perfect time to start a free trial.

Optimize your Markdown writing workflow

Mon, 30 Nov 2015 12:00:00 +0000

One of the biggest benefits to writing in Markdown is also one of its biggest curses when shipping content out for review and approvals: its syntax. Writers love Markdown for its simple, expressive syntax, but it is best suited for writing, not reading. Consuming markdown content is tedious and should never be part of an ongoing workflow. That’s why Markdown editors (like the one in Beegit) come with a built-in preview mode designed for consuming content. Markdown content is written on the left side and rendered for reading on the right side. That’s OK, but it’s still designed for the writing process.

What about an interface optimized for reading?

Today, we’ve rolled out a new feature to level up your team-based Markdown workflow and we’re calling it the Project Portal. Now, each of your Beegit projects can be automatically indexed into a consumable, navigable, and searchable website preview! You can enable/disable this feature from your project settings page. If enabled, just share the link to the Project Portal or file, and anyone can browse the content you’ve written in a rich interface. You can find the link using the share icon next to the file name.

Your stakeholders (clients, bosses, colleagues) can now read your content as intended, as rendered HTML output, without you having to worry about questions regarding Markdown syntax or having to export out a file just so it can be consumed. We’ve also included a project-wide content search in the Portal, so it’s super easy to search across content and easily find related terms while browsing projects.

Taking it a step further with file statuses and approvals

We’ve also included a simple file status and approval mechanism in this release. From the file menu, you can now manage a status on each file with notifications built right in. The supported file statuses are:

Draft
Pending Approval
Approved

When changing the file status, you can optionally choose which collaborators on the project should be notified of the status change. If the Portal is enabled for that project, then the automated notification message will even direct them right to the Portal for an optimized reading experience. If the file status is “Pending Approval,” the file can be approved directly from the Portal with an optimized approval interface. This helps to simplify an approval workflow by getting a stakeholder’s sign-off on content without having to drag them through the Markdown. Note: To approve a file, the approver will need to have a Beegit account and be logged in – they can also log in from the Portal if they aren’t already logged in.

We hope the new Portal and status features help make your life a little easier while writing and approving content. If you haven’t been around for awhile, now is a great time to log back in to Beegit and see why it’s the best collaborative writing app for the web. If you’ve never signed up for Beegit, it’s the perfect time to start a free trial.

New find and replace feature with expanded file search

Sun, 15 Nov 2015 12:00:00 +0000

People are writing more content than ever in the Beegit editor, so we’ve released a handy new find/replace feature. The project search feature has also been upgraded to support searching for files.

Find and replace

You can use the new find and replace feature in the file editor to search within an open file. Bring up the find/replace panel with CMD+F (Mac) or CTRL+F (PC) whenever your cursor is focused in the editor. From there, you’ll be notified of how many matches are found in your document based on your query. You can then cycle through the matches, or use the replace feature to easily make sweeping changes across the whole file. You can close the panel with the ESC key when you’re done.

Upgraded search capabilities

For a while now, you’ve been able to search across all projects that you have access to by searching for the project name. That search has now been upgraded to search across all files that you have access to as well (given a search query, it’ll try to find both projects and files that match). Now it is easier than ever to use the search feature to jump between files in different projects without having to use the file navigation to open a file. For now, this search will query against all filenames in projects that you can access (stay tuned for more on this later if you want to be able to search file content as well 😉).

Update: As of February 5, 2016, file searches now search actual file content as well as filenames.

Start finding, replacing and searching for files!

If you haven’t been around for a while, now is a great time to log back in to Beegit and see why it’s the best collaborative writing app for the Web. If you’ve never signed up for Beegit, it’s the perfect time to start a free trial.

Writing Tumblr posts with Markdown

Wed, 30 Sep 2015 12:00:00 +0000

If you’ve already established or are thinking about creating a Tumblr blog, you might consider using Markdown to help format your content more productively. While it’s probably not the right tool for image-centric Tumblrs like House of Carbs or Standing Next To Yao Ming, it can help streamline content formatting on text-centric Tumblrs like Great Talks or even help format the captions underneath your manly Spacebeards photos.

What is Tumblr?

Tumblr is a cross between a social networking site and a blog. It is often described as a “microblog” – a social media site where a user makes short, frequent posts. According to the site’s About page, “Tumblr lets you effortlessly share anything. Post text, photos, quotes, links, music and videos from your browser, phone, desktop, email or wherever you happen to be.” Tumblr is great because you can use it for a variety of content types and you can get a blog set up and running in a few minutes, without having to purchase or configure a domain name and hosting.

What is Markdown?

You might think of Markdown as a simplified and far more human readable way to create content that’s destined for the Web. It can be cleanly and easily translated into valid HTML for pain-free Web publishing. According to John Gruber of Daring Fireball, creator of Markdown, “The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions.” And because it plays nice with HTML, you can mix in HTML attributes and styles if you want to achieve specialized formatting that’s not supported in Markdown. If you’re writing words that are destined for the Web, you really should consider formatting it with Markdown.

Why write Markdown in Tumblr?

Purely from a productivity standpoint, Markdown is useful because it gets to the core of what matters: your writing. Once you learn how to use it, you can quickly and instantly format entire texts without ever needing to touch your mouse. And it’s continuing to grow in popularity – it’s supported in tons of new and established online applications, including Reddit, Trello and more.

Enabling Markdown in Tumblr

Below is a step-by-step guide to enabling Markdown in your Tumblr blog (including screenshots).

2. In the right-side column, there’re four options. Click on “Dashboard”.

That’s it! Your Tumblr blog is now configured for Markdown.

If you need some help with Markdown formatting, check out this handy Markdown cheat sheet. If you’re a bit of a writing procrastinator (like myself), check out Reference for Writers for advice, tips and inspiration.

Happy writing!

File templates help optimize your content production

Mon, 28 Sep 2015 12:00:00 +0000

Today we’ve rolled out one of our most requested features: file templates. You can now create reusable file templates for your content files that are automatically applied whenever you create a new file. Just create a template and pick it from the list of available templates when creating a file.

Creating templates

Anyone on the team with Editor access or above can create and manage the list of templates from the account dashboard. Here, you can create and edit templates that will be available across the account.

Any content you put in the template will be dropped in as the default text on new files created from that template. In addition to file templates supporting static content, they are also very flexible and support the Liquid templating language created by Shopify. With Liquid and Beegit, you can do some really cool stuff, like automatically drop in the current date, or drop in the name and Twitter handle of the user who is creating a new file. When a new file is created against a template, Beegit will merge in any variables you have defined in the template. Here is an example of what you can do (we use this template for our Jekyll blog posts):

---
layout: post
title: Post title - 7 words or less
teaser: Post teaser - 18 words or less
date: {{'now' | date: "%Y-%m-%d 12:00:00"}}
author: {{user.name.first}}_{{user.name.last}}
twitter: [{{user.twitter}}](https://twitter.com/{{user.twitter}})
comments: true
---

Which becomes this file when its template is chosen:

---
layout: post
title: Post title - 7 words or less
teaser: Post teaser - 18 words or less
date: 2015-09-28 12:00:00
author: kris_ciccarello
twitter: [kmctown](https://twitter.com/kmctown)
comments: true
---

Available template variables

Here is the full list of variables that you can specify in a file template:

Template Variable	Description
`{{'now' \| date: "format"}}`	The current date/time in the specified format
`{{ file.name }}`	The name of the current file being created
`{{project.name}}`	The name of the current project
`{{user.name.full}}`	The `Name` of the user creating the file
`{{user.name.first}}`	The `FirstName` of the user creating the file
`{{user.name.last}}`	The `LastName` of the user creating the file
`{{user.twitter}}`	The `Twitter` handle of the user creating the file
`{{user.company}}`	The `company` of the user creating the file
`{{owner.name.full}}`	The `Name` of the user who owns the project
`{{owner.name.first}}`	The `FirstName` of the user who owns the project
`{{owner.name.last}}`	The `LastName` of the user who owns the project
`{{owner.twitter}}`	The `Twitter` handle of the user who owns the project
`{{owner.company}}`	The `company` of the user who own the project

Make some templates!

We’re really excited about the new file templates feature and can’t wait to see what you do with them. If you haven’t been around for a while, now is a great time to log back in to Beegit and see why it’s the best collaborative writing app for the Web. If you’ve never signed up for Beegit, it’s the perfect time to start a free trial.

Beegit - Content Production and Collaboration Blog

What is Content UX and Why Does it Need to Be in Your Business Vocabulary?

What is Content UX and Why Does it Need to Be in Your Business Vocabulary?

What is Content UX?

Why Does it Matter?

What’s Next?

Beegit and Ad-Rank Media

Beegit and Ad-Rank Media

Taking Stock

Transparency

Reliability and Productivity

Customize your team's content workflow — and fonts!

Customizing project file statuses

Customizing default file statuses

Customizing font preferences

Five quick steps to creating a content plan that kills endless revision loops

1. Identify and clearly define team roles

2. Lean on templates and style guides to avoid endless revisions

3. Centralize the team in an online hub

4. Set and share clear (early) deadlines

5. Get approvals on small samples of content

Deep content search and improved commenting with resolved comments

Closing out the comment feedback cycle

Deep content search upgrades

Updated version control system for easier collaborative editing

Version history for files

Committing new versions

Restoring past versions

Optimize your Markdown writing workflow

What about an interface optimized for reading?

Taking it a step further with file statuses and approvals

New find and replace feature with expanded file search

Find and replace

Upgraded search capabilities

Start finding, replacing and searching for files!

Writing Tumblr posts with Markdown

What is Tumblr?

What is Markdown?

Why write Markdown in Tumblr?

Enabling Markdown in Tumblr

1. Click the user icon in top right corner, then click “Settings” in the dropdown menu.

2. In the right-side column, there’re four options. Click on “Dashboard”.

3. Under the text editor section you’ll see a dropdown menu that will read “Rich text editor” by default. Click it and select “Markdown”. A “saved” badge will appear to the right of the dropdown.

File templates help optimize your content production

Creating templates

Available template variables

Make some templates!