jagster

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • in reply to: Moving navbar menu to be flush with top of page #4068

    jagster
    Participant

    @huskerliz: Just anywhere in the file, but try grouping your code logically.

    in reply to: Firefox CSS Quick Query #3997

    jagster
    Participant

    You need to add

    clear: left

    to #slidercontainer for it to go below the logo and nav bar…even then there is a white gap on the top in FF. Not sure why.

    in reply to: page on custom menu – display none #3981

    jagster
    Participant

    Can you link to your site?

    in reply to: page on custom menu – display none #3971

    jagster
    Participant

    Do you have a live link?

    in reply to: thematicsnippets.com #3563

    jagster
    Participant

    Just a quick update: I will be moving this behind a paid registration. It will cost $19 to access tested snippets, resources and other cool things. It will be more professional this way so I can concentrate on making it better over time. Free sites like this usually tend to fall by the wayside so please bear with me while things get going.

    in reply to: Is anyone using thematic for new websites? #3494

    jagster
    Participant

    Hi, yes Thematic is still being developed. I still use it and know a lot of people that do. The latest development version is gearing thematic up for HTML5 support among other things, like keeping it up to date with the WordPress releases. Things move slow here however, so you have to be patient.

    The latest dev branch can be seen here https://github.com/ThematicTheme/Thematic/tree/develop

    in reply to: Least useful child theme ever. #3479

    jagster
    Participant

    Nice, I will check it out some…@drec you should use compass.app (http://compass.handlino.com/), I like it alot.

    in reply to: Development Ideas #3365

    jagster
    Participant

    Thanks for the response ­čÖé

    I think we should avoid the headache of adding styles from the parent theme the way I suggested a la Hybrid Core and just add them directly to the child theme (e.g. just include a well commented style.css in the child theme?). I use and love SASS, but we can’t include that in a child theme out of the box – beginners and newcomers would get really really really freaked out (Scott might argue otherwise, but he is more experienced than me and might not be able to relate to the noobs as much). Adding the layout classes might bloat the stylesheet but I nevertheless like it. It is easier to style. Plus, selecting your layout from a dropdown is cool, right? ­čśŤ

    On another note, should we depreciate all of the current styles (the styles folder) and the superfish/dropdown scripts? All the menu stuff can now be handled with CSS. Superfish adds markup to the structure too, which is annoying. Maybe we can just create a minor headache now and begin depreciating this stuff (which we will eventually flush, maybe by WordPress 3.8 – 2 versions worth of time). I know Thematic is also a parent theme and has added┬áresponsibility, but if any users freak out after the update that flushes this stuff we can just have a sticky topic here that links to a sample child theme with all of the old styles (the whole folder). I have been seriously considering forking Thematic because of the fact that we might have to see all this depreciated stuff forever, but I really do not feel like doing that because I love it and also because my php skills are weak so I would probably fail.

    in reply to: Development Ideas #3359

    jagster
    Participant

    P.S. I will open up some issues on GitHub so others who look there can see what we are trying to do. Is that okay?

    in reply to: Development Ideas #3358

    jagster
    Participant

    I am pretty decent with CSS and best practices so I can definitely help a lot. There are a lot of headaches with the styles and it will be a pretty hard task, especially since we want to streamline the framework as much as possible. A few things:

    1. My biggest worry is that we will have all these legacy styles and the framework will be a little bloated – just knowing the files are sitting there will bother me a little ;). I think we should at least┬ádepreciate and/or remove the 18px, 21px and menu.css files because I have never seen them being used. Ever.
    2. Using @import was cool when Thematic first dropped, but is now frowned upon. That is why we should make it so the user has to add the styles in their functions.php file a la Hybrid Core. See https://github.com/justintadlock/hybrid-core/blob/master/functions/styles.php
    3. As for the layouts, that will be a mess. We should do it a la Hybrid Core as well IMO, but I have to think about that one more. We need to not only trim down each layout stylesheet, but make sure it won’t interfere with responsive/mobile-friendly design. Any ideas?
    4. Should we add basic ARIA support like role=”banner”?
    5. The siteinfo should be wrapped in a <p> tag </p>

    I have off of work tomorrow so I will submit some pull requests on github for other things. The readme file needs to be updated among other things.

    – James

    in reply to: Thematic html5 plugin version 0.4 released #3182

    jagster
    Participant

    Haven’t posted here in forever, but it would be awesome if Thematic was converted to HTML5 via the way Gene described. Just wanted to voice my support (I would even consider using Thematic again :)).

    in reply to: Fabric – A new responsive Thematic child theme #638

    jagster
    Participant

    Oh ok, I wasn’t sure if the variant stuff was outdated or not – even though it still works, I’ll try and update that soon.

    in reply to: Fabric – A new responsive Thematic child theme #572

    jagster
    Participant

    I’d love to just include the theme options with my theme via the thematic options (I think it is filterable now?) Kind of a pain to install a plugin for a few options.

    in reply to: Fabric – A new responsive Thematic child theme #557

    jagster
    Participant

    The menu currently doesn’t handle multi-level dropdowns – there were some issues with it. I figured for this theme no multi-level dropdowns were okay since it is a minimal theme, but for my next one I’ll try to figure it out.

    in reply to: Menu bar moved w/ upgrade #271

    jagster
    Participant

    Yep I see it. Add this to your style.css and it will go away ­čÖé

    #blog-title {
    border-bottom: 0;
    }

Viewing 15 posts - 1 through 15 (of 19 total)