StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5777946
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-25T11:36:48.460
FavoriteCount
0
LastActivityDate
2011-04-25T11:36:48.460
LastEditDate
LastEditorUserId
0
OwnerUserId
706866
ParentId
5697474
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
For me the key considerations would be: <ol> <li>Fully automated: Can it be set up in such a way so that pretty much no outside work is required to create or edit the documentation.</li> <li>Fully styled: Can the documentation be fully styled so that it looks great in a wiki or pdf after it’s generated. I should be able to change colors, font sizes, layouts, etc.</li> <li>Good Filtering: Can I select only the items I want to be generated. I should be able to filter the namespaces, file types, classes, etc.</li> <li>Customization: Can I include headers, footers, custom elements, etc.</li> </ol> I found Doxygen could do all of this. Our workflow is as follows: <ol> <li>Developer makes a change to the code</li> <li>They update the documentation tags right above the code they just changed </li> <li>We click a generate button</li> </ol> Doxygen will then extract all the XML documentation from the code, filter it to only include the classes and methods we want, and apply the CSS styling we’ve pre-made for it. Our end result is an internal wiki that looks the way we want, and doesn’t require editing. Extra: We have all our projects in various git repositories. We pull all these down to one root folder and generate the docs form this root folder.. Would be interested to know how others are automating even further..?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODocumentation Generation - What boxes should I aim to tick?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDave Sumter
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODocumentation Generation - What boxes should I aim to tick?
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
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.