StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14097244
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-31T03:54:55.237
FavoriteCount
0
LastActivityDate
2012-12-31T04:03:03.010
LastEditDate
2012-12-31T04:03:03.010
LastEditorUserId
143739
OwnerUserId
143739
ParentId
13486960
PostTypeId
2
Score
19
ViewCount
0
LastEditorDisplayName
text
Body
A page can have only one <code>layout</code>, but layouts can be nested. I have three <code>_layouts</code>: <ul> <li>master.html</li> <li>default.html</li> <li>post.html</li> </ul> The <code>master</code> layout has all of the basic structure that any page I want will need. It looks something like this: <pre><code><html> <head> <title>{{ page.title }}</title> </head> <body> {{ content }} </body> </html> </code></pre> I use the <code>default</code> layout for most pages that are not blog posts. I do make extensive use of a few <code>page</code> variables in pages' YAML front matter. The layout looks something like this: <pre><code>--- layout: master --- <h1> {{ page.title }} {% if page.subtitle %}{{ page.subtitle }}{% endif %} </h1> {% if page.description %}{{ page.description }}{% endif %} {{ content }} </code></pre> I use the <code>post</code> layout for <code>_posts</code> pages. It looks like this: <pre><code>--- layout: default --- Posted {{ page.date }} <ul>{% for tag in page.tags %}...{% endfor %}</ul> {{ content }} </code></pre> Every blog post that I make, I use the <code>post</code> layout, and they inherit from all three layouts. If you want to have snippets of reusable markup, then I would recommend using <a href="https://github.com/mojombo/jekyll/wiki/Liquid-Extensions"><code>_includes</code></a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJekyll index.html that uses 3 different _layouts
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USkzh
UserOwnerUserId
1. USkzh
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
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.