Forum Replies Created
@ roar - with the new My.StudioPress member portal, you are able to fill out a help ticket and our staff will personally attend to your question. The forums here are only for general questions about WordPress and design, which might make you think that theme support is getting pushed aside.
We don't have any public page or link to send folks to as far as what's on the roadmap, but what I will say is that in Genesis 1.9 we've got new functions written for implementing Google Fonts as well as one for responsive design. (The latter will require support from the child theme, but we do have a new mobile menu option coming.) There are some other cool things coming in 1.9 such as Google Authorship profiles.
Another major thing is the updated design for the Genesis parent theme, which you can see here. This should be available shortly after WordPress 3.5 is released in December.
Genesis 2.0 will primarily include support for HTML5 elements and will most likely be a spring 2013 release. Hope this helps!
Tracy, your original post is still here -- I had tried to split that thread, which didn't really work so I decided to open an entire forum for suggestions and feedback.
As for links, when you create a link in the text editor, you have the option to set it to open in a new window. As for signatures, since that is a manual process for folks to add, they'd have to add the target="_new" to the HTML for that to happen.
If you're using Chrome or Firefox, right right click the link when you go to open it and you'll have the option to open it in a new tab or window.
If you purchased our Magazine theme and are logged into the new My.StudioPress portal, you can view the setup instructions which should help. Also, that theme comes with a file called magazine.xml which is location in the /magazine/xml/ folder, and you can use that to import the demo site content.
@ everyone - can you guys start a new thread here with what you had in this one, so I can delete this one and handle on a per suggestion basis?
I am going to close this so we can address things individually, as it's tough to do that in a single thread.