![]() ![]() ![]() As a result, the effort to contribute isn’t as engaging. You start out expounding on a general topic, not answering an actual question a user asked and needs help with. “You aren’t documenting a specific problem you’re facing, you’re helping others deal with an entire class of problems by documenting” ( Welcome to Stack Overflow Documentation. Documentation, on the other hand, is more general. With a forum post, you’re directly helping someone. The interaction model for writing documentation isn’t as compelling as answering forum posts.Additionally, in a forum you’re contributing your perspective amid a variety of other potential answers, not providing a single authoritative answer. It takes more of a sense of expertise and authoritativeness to write documentation than to answer a forum question. Contributing authors felt less confident writing docs than they did forum posts.Forum responses are much easier to crowdsource than entire documentation topics. If the effort for contributors is too high, fewer people participate. It’s a lot of work to write documentation. Documentation doesn’t granularize into little chunks that can be easily crowdsourced.The model of foregrounding examples before textual explanations was supposed to be the differentiating characteristic in Stack Overflow’s Documentation, but it didn’t seem important enough to users to persuade them against the original sources. For example, when creating a new project in Android Studio, would you go to Stack Overflow or Android’s docs? Turns out more people went to the latter. There’s not a compelling reason to go to Stack Overflow instead of the more authoritative source. Documentation was largely redundant from the original sites, so the Documentation pages didn’t receive the anticipated traffic.Here are a few reasons why Stack Overflow’s Documentation effort failed: Why Stack Overflow’s Documentation failed ![]() For their sunset announcement, see Sunsetting Documentation. You can download the MP3 file, subscribe in iTunes, Google Podcasts, or other podcast platforms.įor an introduction and tour of Stack Overflow’s documentation, see Welcome to Stack Overflow Documentation. Author in DITA and Publish with WordPress.Reflecting seven years later about why we were laid off.A hypothesis about influence on the web and the workplace.See the newest Aptos releases in the Latest Releases list and its subpages. If you have checked out another branch to use a specific network, the code may not yet have all of the features described here. Please note, this site is built from the main upstream branch of GitHub and so therefore reflects the latest changes to Aptos. Here you will find concepts, how-to guides, quickstarts, tutorials, API references, code examples, release notes, and more. ![]() This documentation covers both basic and advanced topics. This documentation will help you develop applications for the Aptos blockchain, run nodes, and be a part of the blossoming Aptos community. In the Ohlone language, "Aptos" means "The People." This site is here to help you grow a web3 ecosystem project that benefits the entire world through easier development, more reliable services, faster transactions, and a supportive, decentralized family. Welcome! Aptos is a Layer 1 for everyone. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |