StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7151268
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-08-22T17:37:53.403
FavoriteCount
0
LastActivityDate
2011-08-22T17:37:53.403
LastEditDate
LastEditorUserId
0
OwnerUserId
623654
ParentId
4893215
PostTypeId
2
Score
31
ViewCount
0
LastEditorDisplayName
text
Body
SUPER SHORT VERSION: Use <code>/*! loud comments */</code> and compile the SCSS just before packaging and distributing. Two part answer, "old part" first: I used Sass/SCSS when developing my "Orin" theme: <a href="https://github.com/founddrama/orin" rel="noreferrer">https://github.com/founddrama/orin</a> Part One: <ul> <li>In my <code>src/scss</code> directory, I keep all of my <code>_include.scss</code> files and the <code>style.scss</code> file that has all of the <code>@import</code> statements.</li> <li>During development, I just run the usual <code>sass --watch</code> (although it's an extra step to remember to save the <code>style.scss</code> file).</li> <li>Once your SCSS source is looking good and committed to version control, you can simply build the <code>style.scss</code> into <code>style.css</code> and check that into version control for the Theme that gets distributed.</li> </ul> In my case, "Orin" is just for me, so I perform the build when I update it on the blog server, but the SCSS compilation can just as easily be done prior to packaging/distribution. The build script I'm using is <a href="https://github.com/founddrama/orin/blob/master/bin/deploy.sh" rel="noreferrer">here</a> (in that Github repo); the gist of it being: <ol> <li><code>touch</code> to create the <code>style.css</code> output file;</li> <li>apply the license text;</li> <li>compile the SCSS and append it to <code>style.css</code>.</li> </ol> Part Two: More recent versions of Sass include support for <code>/*! loud comments */</code>; meaning that I need to get off my lazy butt and update to: <ol> <li>Include the license text and theme description right there in <code>style.scss</code> using the loud comments;</li> <li>update the build/deploy script to simply compile the SCSS.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Sass compressed output while leaving theme comment header for Wordpress
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USfounddrama
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.