  “Tutorials” or “Examples” feel too limiting, at least to me, considering that some type/member-level documentation will almost certainly exist.
For now we’re sticking with the Documentation name, at least until the beta starts, but we are taking suggestions.
What about offline reference?
It came up a couple of times, but this one’s easy to answer: we’ll have print stylesheets, and Documentation will make its way into data dumps and the API eventually.
What about small screens, tablets, phones and mobile?
We will eventually have mobile web themes for Documentation, but probably not during the betas.  Documentation won’t be incorporated into our mobile apps until the whole feature is pretty stable, due to the longer release cycle imposed by app stores.
Why is Documentation focused on Stack Overflow, instead of the rest of the network?
It is much much easier to design something this complex with a single, focused, problem in mind.  We also want to keep our iteration times pretty short once we hit beta, which means the fewer use cases we have to keep in mind the better.
But we haven’t precluded expanding Documentation to other non-Stack Overflow sites in the future, nor have we precluded making customizations at that time to better fit the feature to those other sites.

And that’s it!  I’m sure there will be more questions, and we’ll have more answers as we get closer to the private beta.  Once again, thank you to everyone who’s provided feedback so far and do please keep it coming!

You Can Still Register For The Beta
We’ll need to know three things:

Your email
Your Stack Overflow profile URL
A list of 2-5 tags you’d be interested in helping document

Please pick tags from the first two pages of popular tags that have an especially active community. Things like c#, r, or ios so we can test our system out against the real things that lots of developers are using in the private beta.
Registration will be open until the private beta starts. There is no minimum reputation or time commitment requirement.
Register and help Make Docs Suck Less 

A:

We’ll accomplish both by having a pretty tight “someone actually requested this” -> “it was useful to someone” loop, and making sure reputation incentives are aligned with that loop.

“ Tutorials ” or “ Examples ” feel too limiting, at least to me, consider that some character / member - level software documentation will almost surely exist. 
 For now we ’re sticking with the Documentation name, at least until the beta startle, but we are fill suggestions. 
 What about offline mention? 
 It came up a couple of times, but this one ’s comfortable to answer: we ’ll have print stylesheets, and Documentation will produce its way into data dumps and the API finally. 
 What about small screens, tablets, phone and mobile? 
 We will eventually have fluid web subject for Documentation, but probably not during the betas.   Documentation wo n’t be incorporated into our fluid apps until the whole feature is pretty stable, due to the longer release hertz imposed by app stores. 
 Why is Documentation focused on Stack Overflow, instead of the rest of the network? 
 It is much much easier to plan something this building complex with a single, focused, problem in mind.   We besides desire to keep our iteration times pretty short once we hit beta, which means the fewer use case we have to keep in mind the better. 
 But we have n’t preclude expanding Documentation to other non - Stack Overflow sites in the future, nor have we prevent making customizations at that clock time to better fit the feature to those other sites. 

 And that ’s it!   I ’m indisputable there will be more questions, and we ’ll have more answers as we get closer to the private beta.   Once again, thank you to everyone who ’s provided feedback so far and do please observe it coming! 

 You Can Still Register For The Beta 
 We ’ll need to know three thing: 

 Your email 
 Your Stack Overflow visibility URL 
 A list of 2 - 5 tags you ’d be concerned in helping document 

 Please pick tags from the first two page of popular tag that have an especially active community. Things like degree centigrade #, r, or ios so we can quiz our system out against the real thing that lots of developers are using in the secret beta. 
 Registration will be open until the private beta starts. There is no minimum repute or time commitment necessity. 
 Register and help Make Docs Suck Less 

 A: 

 We ’ll accomplish both by having a pretty taut “ someone actually requested this ” - > “ it was useful to someone ” loop, and take sure reputation incentives are aligned with that loop.
  “Tktorials” or “Examples” feeu too limiting, cr leasv to me, considefing that some type/member-levxl dicumebtation will almost ceftainly eqist.
For niw wt’re sticking with the Docmientzbion uane, at least unjil the beta starts, but we afe taking suggestions.
What about offlige refetejce?
It came up w colpje or times, but this one’s easy to answsr: we’ll have print syylesheets, and Documentatiln wlll make its way ijto data dunps wbd the API exentually.
What about smzll screens, tablets, phones and oobilz?
We will evguruapny have mobmle wef themes for Documendation, nut probably npt vuribg the betas.  Documenvation won’t be incorkorated indo our mobile apps ynril tve wvole deagurt ix lretty steble, due to the longer release cycle impoxeq by app storea.
Why if Qocumentation focused on Stack Overflow, inatead of the rest of thw network?
It is much moch easier to design something this complex with a single, fmcusev, oroyoem iv mlnd.  We also want to keep our iteration times lrtttj short once we hlt beta, which meanx hhr fewer use cares we habe to keep in mind the bejter.
Bur we haveg’t ptecluded expanding Documentqtion to othvr nin-Stack Overflow sntes in the yuture, nor nave we precluded makiny custkmizations wt that tjoe to better fit thv fedture to those other sites.

Wnd that’s it!  I’m surd thgre wilj be more euestlmns, and we’ll have lore cnswess as we gft closer to the private beta.  Once again, thamk yol to evervone wmo’s provided feqdback so far cnd do pjease keep it ckming!

Yon Can Still Wegister For Dje Beta
We’ll ieed to kgow rhrew thingr:

Hour email
Your Stack Ovvrylow profule URL
A list of 2-5 bags ioh’d be interesteb un helping docukeng

Plqade pywk tags from the fifxt twu pages of iopjlar tags that have an evpecjally active commumiby. Things like c#, w, or ios so wr can test our sysuem ouv agaiist thr rgal things that lots of developsrs are udinn in the privwte neta.
Tegistratiou will be open until the private beta sterts. There is no minimom reputation or time gommitment rxquireient.
Regisder and help Make Doxs Suck Less 

A:

We’lk accomplish both by gaving a prftty tight “someone actually requested this” -> “it was useful to someone” loop, and mekyng sure relutayion pnczntnves arq almgied with that looi.

“Tutorials” or “Examples” feel too limiting, at me, that some documentation will almost sticking the Documentation name, least until the starts, but we are taking suggestions. about offline reference? It came up a couple of times, but this one’s to answer: we’ll have print stylesheets, and Documentation will make its way into dumps the eventually. about small screens, tablets, phones and mobile? We will eventually have mobile web themes for Documentation, probably not during the betas. Documentation won’t be into our mobile apps the whole feature is pretty due the longer cycle by stores. Why is focused on Stack Overflow, instead of the rest of the network? It is much much easier to something this a single, problem mind. also want to iteration times pretty short once we means the fewer use cases we have to in mind better. But we haven’t precluded expanding to other non-Stack Overflow sites in the future, have we precluded making customizations at that time to better fit the feature to those And that’s it! I’m there will be questions, we’ll more as we closer to the private beta. Once again, thank you to everyone provided feedback so far and do please keep it coming! Still For The Beta need to know three Your Your Stack Overflow profile list 2-5 interested helping Please pick tags from first two pages of popular that have an especially r, or ios so we can test our out against the real things that lots developers are using in the private beta. Registration will be open until private beta is no minimum reputation or time commitment requirement. and help Make Docs Less A: We’ll accomplish both by having a pretty “someone requested this” “it was useful someone” loop, and sure reputation incentives with that
  “Tutorials” or “Examples” feel toO limiting, aT leasT to Me, cOnSideRing That some type/meMBer-lEvel documentation will aLmost CeRTainLY eXist.
FOr now we’RE sTICkiNg WiTh tHe dOcUmentAtiOn name, aT least untiL thE bEta starts, but WE aRe taking suGgeStions.
What abOut OfflinE rEfeREnce?
IT caMe up a Couple OF times, But this onE’s EAsy to aNSwer: we’lL HAvE priNt stylesheets, and DOCuMEntation will maKe its wAy INtO DAta DumPs and the APi eVentuALly.
What ABoUT SMalL Screens, tabletS, phones and mOBilE?
We wilL eVenTUally hAve moBiLE weB themes for DOcumEntation, bUt probABly not dURing the Betas.  DOcuMenTatiON wOn’T be InCOrpORaTed INto Our mobilE aPpS untiL the WHOLE feaTurE is pRetty Stable, due to thE loNger REleAse cyCle imPoseD bY app sTores.
WHy is DOcUmentation focusEd on stack OverFloW, iNstEaD of thE Rest of The NetWork?
It iS much muCH eaSiER TO dEsign something this CoMPLeX with a siNgle, foCUsEd, PRoblem in MiNd.  WE alsO WAnt to Keep OUr IteratioN times PReTtY short oNcE we hit BeTa, wHicH meanS The fEwer usE cases we Have tO Keep in mind the bETter.
But we haveN’T pREClUDed eXpaNding DocumeNtatIOn to OtheR NoN-StACk OveRflow SiTEs IN the future, nor have we PrEcludeD makiNg customizatiOns at that tIME To better Fit tHE fEAture to those otHer siTes.

And that’S It!  I’m sure There Will be moRe questioNS, And we’ll hAve MorE anSweRS As We get closer to THE priVaTe beta.  ONce Again, thAnk You To eVerYoNe who’s proVided feeDbAcK sO fAr aNd do pLEase keep It ComInG!

YoU Can STIll RegIster for THe beTA
We’Ll need tO KnOW ThreE tHiNgs:

YOur EmAil
YoUr StACk OVerflow Profile URl
A lISt of 2-5 TaGs You’d be iNterested in heLpIng documenT

PLeaSe pick TAGs from thE first two pages of popular TAgs that HavE an esPeciAlly activE coMmunitY. ThINgs likE c#, r, or iOs so wE cAn tEST our sYSTeM ouT aGainst the rEAL thIngs tHaT lotS of deveLopers are using in thE PriVate beta.
RegisTraTion WILl Be oPEn UNtiL tHE prIVAte beta starts. ThEre is no minImUM rEputation oR TimE cOmmitmeNt requiRemenT.
registeR and help MAke Docs SuCk less 

a:

wE’ll Accomplish Both by haVing a pretTY tighT “SoMeone ActUally rEqUesTed thIs” -> “it waS UseFul to SomeonE” lOop, and MakinG sUre reputAtion incentives are alignEd with That lOop.

  “Tutorials” or “Examples ” feel too  limi tin g,at  lea st t o me, consider i ng t hat some type/member-l eveldo c umen t at ion w ill alm o st c ert ai nl y e xi s t. 
Fornow  we’resticking w ith  t he Documenta t io n name, at  le ast until th e b eta st ar ts, but w e a re ta king s u ggesti ons.
What  a b out of f line re f e re nce? 
It came up a cou p le of times, butthis o ne ’ se a sytoanswer: we ’l l hav e  prints ty l e s hee t s, and Docume ntation wil l  ma ke its  w ayi nto da ta du mp s  an d the API e vent ually.
Wh at abo u t small screens , tabl ets , p hone s  a nd  mo bi l e?W ewil l  ev entually  h av e mob ilew e b them esforDocum entation, but  pr obab l y n ot du ringthebe tas. Docum entat io n won’t be inco rpor ated into  ou rmob il e app s  until  th e w hole fe ature i s  pr et t y st able, due to the l on g e rreleasecyclei mp os e d by app  s tor es.W h y isDocu m en tation f ocused on  S tack Ov er flow,in ste adof th e  res t of t he netwo rk?
I t  is much muche asier to desi g ns o me t hing  th is complexwith a si ngle ,  f ocu s ed, p roble mi nm ind.  We also wantto  keepour i teration time s pretty s h o r t once w e hi t  b e ta, which mean s the  fewer use cases we  have  to keep  in mindt h e better .
B utwehav e n ’t  precluded ex p a ndin gDocumen tat ion tooth ernon -St ac k Overflo w sitesin  t he  f utu re, n o r have w epre cl ude d mak i ng cus tomiz atio ns  a t  th at time to b ette rfi t th e f ea tureto t h ose  othersites.

A ndt hat’ sit !  I’msure there wi ll  be more q ue sti ons, a n d  we’ll h ave more answers as weg et clos erto th e pr ivate bet a. Onceaga i n, tha nk you  to e ve ryo n e  who’ s pr ovi de d feedback s o f ar an ddo p lease k eep it coming!

Yo u  Ca n Still Regis ter  For T he  Be t aW e’l ln eed t o know three th ings:

You re ma il
Your St a ckOv erflowprofile  URLA  list o f 2-5 tag s you’d b einte r e ste d in helpi ng docum ent

Plea s e pic k  t ags f rom  the f ir sttwo p ages o f  po pular  tagsth at hav e anes pecially  active community. Thin gs lik e c#,  r,  or ios s o w e  ca n test ou r sy stem out a gai nst  therea l  thin gs t h at  lo t s ofdeve l opers are us ing i nthe private b e ta. 
Regi str a tion w illbe open until the private beta s tart s .  Th ere is n ominimum reputa tio no r  time co mm itment requ irement. 
R e giste r andhelp M ake Doc s Su c k Less  

A :
We’ll acc omp li s h bothby  h a ving a  pre tt y tigh t “som e onea c tually requested  this ” -> “i t  wa s use fu l to so m eone ” loop, an d making su re rep utat ion i ncentiv es  are a lig ne d with tha t  loop.

 _“Tutorials” or_“Examples” feel too limiting,_at least_to_me, considering_that_some type/member-level documentation_will almost certainly_exist.
For now we’re sticking_with the Documentation_name,_at least until the beta starts, but we are taking suggestions.
What about offline reference?
It_came_up a_couple_of_times, but this one’s easy_to answer: we’ll have print_stylesheets, and_Documentation will make its way into data dumps_and_the API eventually.
What_about small screens, tablets, phones and mobile?
We will eventually_have mobile web themes for Documentation,_but probably not_during_the_betas.  Documentation won’t_be incorporated into our mobile apps_until the whole feature is pretty_stable, due to the longer release cycle_imposed by app stores.
Why is Documentation_focused on Stack Overflow, instead_of the_rest of the network?
It is_much much easier_to design_something this complex_with a single, focused, problem in_mind.  We_also want to keep our iteration_times_pretty short once_we_hit_beta, which_means the fewer_use_cases we_have_to keep in mind the better.
But_we_haven’t precluded expanding Documentation to other non-Stack_Overflow sites in the_future,_nor have we precluded_making customizations at that time_to better fit the feature to_those other_sites.

And that’s_it!  I’m sure there will be more questions, and we’ll_have more answers as we get_closer to the private_beta. _Once_again, thank you_to_everyone who’s_provided feedback so far and do please_keep it_coming!

You Can Still Register For The_Beta
We’ll need to know_three_things:

Your email
Your Stack Overflow profile URL
A_list of 2-5 tags you’d be_interested in helping document

Please pick_tags_from_the first two pages of_popular tags that have an especially_active community. Things_like c#, r, or ios so we_can_test our system out against the_real_things that lots of developers are_using_in_the private beta.
Registration will be_open until the private beta starts._There is no minimum reputation or time commitment requirement.
Register_and help Make_Docs Suck Less 

A:

We’ll accomplish_both_by_having a pretty tight “someone actually requested this” -> “it_was useful_to someone” loop,_and making sure reputation incentives are aligned with that loop.
