StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3186703
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-06T13:42:52.943
FavoriteCount
0
LastActivityDate
2010-07-06T14:10:18.933
LastEditDate
2010-07-06T14:10:18.933
LastEditorUserId
370940
OwnerUserId
370940
ParentId
3186530
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
You need to learn CSS, not fight it. CSS has been used to create much more complex layouts than what you have described. And it is the only way you should be styling your web pages and implementing a layout design. CSS gives you much more control over the presentation of a webpage and positioning of elements than frames can (frames only give you frames to put load multiple pages in; you still need to style those pages separately). This is a rather broad question, so I'll just say this: <ul> <li>Use HTML to semantically organize/structure your content.</li> <li>Use CSS for your presentation.</li> </ul> In other words, don't use any of the following tags or similar tags: <ul> <li><code></code> (use <code></code> instead)</li> <li><code></code> (use <code></code> instead)</li> <li><code></code></li> <li><code></code></li> </ul> Remember to use structuring tags where appropriate like: <ul> <li><code><h1></code> up to <code><h6></code></li> <li><code></code></li> <li><code><blockquote></code></li> <li><code><pre></code></li> </ul> And use semantically correct tags. So if you have a definition list, use <code><dl></code>, <code><dt></code> and <code><dd></code>. If you have a form, use <code><label for="{input id}"></code>, e.g.: <pre><code><label for="first-name">First Name:</label> <input name="first_name" id="first-name" />  </code></pre> Don't use tables for layouts. Use them only for tabular data. And when you do, make sure you use proper semantic markup <code><thead></code>, <code><th></code>, <code><tbody></code>, etc. Put <code>title</code> attributes in your links and <code>alt</code> attributes in your images for accessibility and usability. And use stylesheets (preferably external ones for DRY) instead of inline styles. Lastly, as Jan_V mentioned, <a href="http://www.w3schools.com/css/" rel="nofollow noreferrer">w3schools.com</a> is a great resource for CSS, JavaScript, HTML, and most web standards. There is a lot for you to learn, but luckily there's a ton of tutorials, references, and other resources on the web to help you along. Learn how to properly use CSS/HTML, and you will produce higher quality webpages as well as save time in maintenance. If you're struggling with the layout you have in mind, start with something simpler and work your way up. E.g. try an evenly drawn 2 column, 2 row layout first. Once you get that working, start changing the proportions and adding more columns/rows.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's current best practices for formatting web page?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USLèse majesté
UserOwnerUserId
1. USLèse majesté
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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.