StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
477541
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-01-25T10:59:23.857
FavoriteCount
0
LastActivityDate
2009-01-25T16:59:26.740
LastEditDate
2009-01-25T16:59:26.740
LastEditorUserId
53881
OwnerUserId
53881
ParentId
477502
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
RunningMonkey
text
Body
Many successful open source projects demonstrate how good online documentation can look like. Some aspects are: <ul> <li>Up to date. If the documentation is not up to date anymore, it may become a show stopper.</li> <li>Many online documentations begin with some short tutorial. They show some key aspects from the software and keep the user aware and interested to dig deeper.</li> <li>Often HowTos or FAQs are very useful. Many users choose not to read documentations and just try it out. At some point the users are very likely to ask the same question over and over again. Be aware what the users may ask for and what they already have asked for.</li> <li>For the interested users, provide some in detailed information in a core documentation.</li> <li>Also consider to think about the audience of the documentation. As an author of documentation, I think it’s very useful to clearly state for which audience the documentation is for and what kind of knowledge they should already have. This forces me to be specific and concise. This way I may end up separating the documentation in different distinct parts, which makes the documentation very structured.</li> </ul> If you already have a “1500-something pages tome like” documentation, you can wrap around some tutorials, HowTos and FAQs and that would spice up the documentation. When the software evolves, you can refactor the core documentation to a more readability. The most hard part is to keep the documentation up to date. Write the documentation with future changes in mind.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is Good Online Documentation?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTheo Lenndorff
UserOwnerUserId
1. USTheo Lenndorff
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat is Good Online Documentation?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.