On filing an issueIssues are essentially bugs, feature requests, or suggestions that you believe should be incorporated into the theme. Anyone (with a Google account) may file an issue and it will be tracked accordingly. It's simple. For our purposes here, a bug is when the theme does something that it explicitly shouldn't, whether intentionally or accidentally. Before filing an issue, however, consider: - Does this keep in the minimalist philosophy behind the theme?
- Could this be done by a plugin instead?
- Is this a request for personalization?
- Could this be something accomplished with CSS alone?
But it's better to suggest something that isn't incorporated instead of keeping it to yourself. And thanks for taking the time to check this out. Your input is both welcome and needed.
|
Sign in to add a comment
I think I understand the distinction between emphasis and presentation, and why the <em> tag shows up as boldface rather than italics. My problem is: with Blogtext 3.0.1 installed in Wordpress, on my writing/editing page, I still have a button with an italic i shown on it (second button from the left.) It actually adds the <em> tag, though.
My questions are: -- Is it possible to make the symbol on the button correspond to what it actually does? -- Is there some way to make the Wordpress editor add italics automatically? (I like italics.)
I think I understand the distinction between emphasis and presentation, and why the <em> tag shows up as boldface rather than italics. My problem is: with Blogtext 3.0.1 installed in Wordpress, on my writing/editing page, I still have a button with an italic i shown on it (second button from the left.) It actually adds the <em> tag, though.
My questions are: -- Is it possible to make the symbol on the button correspond to what it actually does? -- Is there some way to make the Wordpress editor add italics automatically? (I like italics.)
I also understand the idea of semantic markup. However, in a blog that is more literary than not, I need the distinction between italics for titles and bold for emphasis. Otherwise, it is a glorious theme. Thanks! (I go in and change the stylesheet for my purposes, so I'm not asking for a fix, although that would be nice to have the distinction built in.)
Separate issue: on one blog I've used blogtxt as the theme, everything's fine. However, yesterday I had an IT person install it for me on a server here at school, and it seems to be using the print.css file instead of the style.css, i.e., the sidebar items are at the bottom of the page. I don't have direct access to the server here, nor do I have any clue as to what to tell the IT guy. Have you encountered this issue before? I would give you the URL, but it's behind a firewall and you couldn't get to it.
Quick one- I'd love an option for sidebar text alignment. The 'veryplaintext' theme (also by Scott Wallick) has one and I have tried unsuccessfully to import it into blogtxt. When the sidebar for the 2 column layout is set to the left it's text become right-aligned and is not changeable. I'm a typographer rather than a php/css developer I'm afraid!
Also a couple of very quick one possibly not for this wiki: can anyone tell me where the code for the vertical rule on the sidebar are situated? I want rid of it and it's driving me insane trying to find it.
Is there an easy way to move pingbacks below the comment form? Some of my posts have very lengthy pingback lists, requiring commenters to scroll quite a bit to get to the form.
Hi Scott.. not really an issue but it took me awhile to figure out that the sidebars have a css file not listed in the design section. these are 3c-b.css (i needed to edit the "vertical rule" or border color on lines 18 and 19) 2c-r.css 2c-l.css if you can, let me know how to add these to the theme editing sections.
all of the style.css content is editable, but some of the style related content is in the above files.