<font id="3j955"><dl id="3j955"></dl></font><dl id="3j955"></dl>
<dl id="3j955"><i id="3j955"></i></dl><i id="3j955"><i id="3j955"><delect id="3j955"></delect></i></i>
<video id="3j955"></video><dl id="3j955"></dl>
<dl id="3j955"><delect id="3j955"></delect></dl>
<i id="3j955"><font id="3j955"><meter id="3j955"></meter></font></i>
<dl id="3j955"></dl><dl id="3j955"><delect id="3j955"></delect></dl><i id="3j955"><font id="3j955"></font></i><dl id="3j955"></dl>
<dl id="3j955"></dl><video id="3j955"><delect id="3j955"></delect></video><dl id="3j955"></dl>
<dl id="3j955"></dl>
<i id="3j955"><font id="3j955"><nobr id="3j955"></nobr></font></i>
<dl id="3j955"><i id="3j955"></i></dl>
<nobr id="3j955"><video id="3j955"></video></nobr>
<dl id="3j955"></dl><i id="3j955"><font id="3j955"><nobr id="3j955"></nobr></font></i><dl id="3j955"></dl><delect id="3j955"><delect id="3j955"><meter id="3j955"></meter></delect></delect>

Bring your team’s documentation into the digital age

Introducing Articles on Stack Overflow for Teams.
Where long-form knowledge goes to thrive.

Get started
Available on Business Enterprise

Create content from commonly-used formats

Tie the Article to a question or answer

Flag Articles to be updated by the owner

Upvote content that is helpful or solves a problem

Content that thrives in Articles


Today, documentation is typically housed in a Word or Google doc and rarely sees the light of day once a new product or feature has shipped. With Articles, the documentation can be easily updated over time as the technology changes and evolves.


Share quarterly updates, weekly metrics, and project plans with an Article.


How-to’s and onboarding are easier and more visible. Team members can link from a question or answer to the guide for closed loop clarification.

Policies and procedures

Skip the email threads, Slack updates and meetings to discuss processes and procedures. Articles allows organizations to move out of the wiki and into the tool that their teams already rely on for finding and sharing information.

The best proactive and reactive way to find, share, and access knowledge.

Quicker time-to-market

By increasing visibility of mission-critical information to your team members, you're ensuring that no matter who needs to jump into a project or cycle mid-stream that they have what they need to do great work.

Choosing the article content type
Articles with historical context or company-wide policies

Retain key information

When a project or release wraps, context is often locked up in a doc or ticket that requires digging and sifting to find and understand. Take that knowledge and add it to one central location where it can be easily searched for, accessed, and updated over time. That way, when a team member leaves the project, critical knowledge is maintained.

Faster onboarding

Getting a new team member from training to contributing takes time. Increase the velocity of your onboarding program by giving new members access to all types of information when they need it most. They can search and find historical information about a product, project, or team within seconds.

Showing links to questions from articles

Leverage Articles with your current Teams setup

Create content from commonly-used formats
Tie the Article to a question or answer
Flag Articles to be updated by the owner
Upvote content that is helpful or solves a problem