SWIFT is now XHTML valid

I fixed all the HTML validation errors, SWIFT is now a 100% XHTML valid theme. Wondering why valid code is important?
Here are few reasons

  • Validation is a sign of professionalism.
  • Many engines cannot properly catalog or index a site that has serious HTML errors. This can greatly reduce the amount of traffic your web site receives from search engines. With SWIFT you don’t have that problem.
  • Properly written HTML will render better, render on more browsers, and render faster than HTML with errors. It’s also more easily adapted to print and alternative browsing devices like mobile phones and handheld computers.
  • Properly written HTML is more likely to be “future-proof” (backward compatible with future standards and future web browsers).
  • Problems such as “ugly” pages caused by poor HTML constantly drive visitors away from web sites.
  • Error-free HTML is the best way to help make sure that pages render optimally in as many browsers as possible. This includes older browsers and browsers that are yet to be developed.

[download id=”1″]

XHTML valid
SWIFT is XHTML valid

Changes to the Support Forum

Earlier Swift support forum was powered by BBPress. Though it is simple and light weight it lacked many important functions and wasn’t very user friendly.

SWIFT support forum from today will be powered by vBulletin4.0. I included some new boards on the forum so that you can collaborate with like-minded Swiftler’s. Hope you all like the new forum.

If you want me to include any new sections on the forum or have any suggestions for the forum, please post them in comments.

[download id=”1″]

PS: If you face problems logging into the forum, reset your password.

25 Replies to “SWIFT is now XHTML valid”

    1. I was trying to figure that out!!!!
      Thanks a ton Amber! I didn’t put two and two together…
      It’s been a long night, thanks a bunch! I was trying to set permissions and all kinds of goofey stuff trying to figure out why the file was 404… I need Sleeeeeeeeeeeeeeep!!!
       

      1. whats going on here??

        Is this specific to green.cx or swift in general?

        The actual custom-styles.css css files used by the theme is located at wp-content/uploads/swift_custom

        the one at swift/includes/ is copied to wp-content/uploads/swift_custom when the theme is activated and it’s story ends there.

        1. Hmm, I’m not sure, but I reinstall the theme new each time, re-uploading from downloads from this site, and each time the custom css file is never found, and the site is only half styled. (I can see the mag styles, but not the structure) I quite trying after a few updates and moved all my mods into a single CSS file, which reduces 1 http request as a bonus.
           

          1. It’ will show you a warning message if it’s unable to copy the file to uploads directory unless you are rewriting the files without treating each update as a new theme.

      1. The ads at top of page is solved. but how about search form?
        its pushed down when i add google search code at swift option.
        any custom css?

  1. There seems to be a small problem with the blog name. It’s class seem to be set to 100% width, what causes the ad block to its right to be pushed down and the whole header area to be twice as higher. See my test blog for an example (tested on Firefox 3.6).

    1. As I understand it, it’s for people/businesses to pay to display ads to blog-0wners (not readers) who use the theme when they open Swift’s admin pages. Unless you want to show ads to Swift-powered-blogs’ owners, there’s no point in registering there.
       
      By the way: Satish, are you going to offer alternatives such as paying to not have those ads shown? It’d be good for people offering Swift professionally to their own 3rd party customers (not my case, but I can imagine how that being the case for others).

      1. I haven’t thought of it till now, may be I will release a premium version without ads.
        Will that be a good idea?

        Thanks for answering the other question for me 🙂

        1. I guess you’ll have customers if you release an ad-less premium version, yes. 🙂
           
          You’re probably going to have 3 kinds of users: cheap ones like myself going for the ad-powered version; those wanting to purchase it for a few blogs, so you’d be able to charge them a per-blog fee; and those wanting to install the theme all over the Net, so you’d be able to charge them a one-time big fee to allow them doing so.
           
          I also imagine premium customers would like an option to optionally remove the “Swift by Satish Gandham a product of SwiftThemes.Com” footer text.

Leave a Reply

Your email address will not be published. Required fields are marked *