I’m looking to add a support guru for my themes. I love creating themes, it’s my hobby, but currently my job requires more time from me, and support for my themes is suffering.
Please send me your application via my Themeforest profile page. Please include your name, preferred hourly rate, and demonstrations of your support work.
Looking to fill this position within the next 2 days so please be quick!!!
I believe it only occurs on business days, so it should be processed on Monday.
Nice! How is the performance of the site though? I would imagine there would be a small performance hit on desktops because of the double loading?
I wrote a plugin for wordpress called Responsage. It’s all server side so it runs pretty awesome. You can check it out an example on the plugin site http://responsagewordpressplugin.com/demo/
Be sure to send your link when you share the code!
I don’t see how this affects user privacy? Ebay’s feedback system is entirely open and I’m sure a company worth billions would be privvy to these privacy issues..
I would really like to know who rated poorly so I can rectify the problems if they ever existed.
The WordPress marketplace is flooded with responsive themes, but I was wondering if any devs include responsive images in their theme? For example, the featured image on a blog post is actually smaller in file size and resolution on a mobile than the desktop?
Hello Themeforest community!
I have created Respons(ive) (Im)ages, or Responsage, a little WordPress theme plugin that allows your responsive layouts to load mobile versions of images. I figured since responsive themes are growing exponentially, it would be great to optimize the loading performance for mobile devices.
Of course it is free, so if you are interested in including it in your current or next responsive theme, give it a go!
Looking forward to your feedback!
It is also worth noting the changes in the way certain tags are allowed to function in HTML5 . For example, the anchor tag can now contain block type elements where in HTML4 this would be invalid. So advertising the template as HTML5 would be fine as it is actually HTML5 even though no HTML5 specific tags are used.
I guess this argument would become redundant once HTML5 is solidified and everyone forgets HTML4 existed