(First off I know solutions vary project to project, but I want to know what you guys do the most)
How far to go in optimizing template? Too much optimization (minimization, combining files, etc) = hard to support, hard for end user to customize / hack up. Too little Optimization = Slow non user friendly. => I was thinking a happy medium would be to combine files as much as possible, but not to minimize them so end users can hack, I can support easier, and end user can minify with whatever tool they want. (Obv utilities like jQuery can be minimized).
Second question: How to organize a jQuery application. I’m thinking keeping it simple: 1 – Just import jquery 2 – Group plugins in 1 file each within its self contained function 3 – Initiate plugins, do custom coding, in another file 4 – Lastly provide a config file to be used by other scripts
Of course not included in that order… But does that sound passable in Themeforest terms, or any suggestions on how you would do it differently. I’m thinking YUI, requireJS or LABjs, MVC frameworks are overkill + not Mass Market friendly but IDK.
Thanks in advanced for the feedback.
Yeah, the welcome message does break up the flow that can be created by the block elements.
High. I’m designing a PSD Template to ease into Theme Forest. I’m a coder by default.
Background I’m going for a Microsoft Metro inspired fitness theme. I’m trying to address a specific design problem while still staying within what themeforest reviewers expect while executing an emerging style. I’m trying to avoid skeuomorphism for this particular project.
Any ideas on making an appealing psd product while avoiding skeuomorphism totally, let me know.http://curtisturner.me/mfr2.jpg
I’m aware the bg can be changed and the padding may be a little tight for most tastes.
PS – The placeholder images are ganked from the net for now. Just needed something to slap in there for now.
I’ve sent an email to your gmail.
Let me know.
Just a thought.
I believe the term “WordPress Theme” should be deprecated in favor of “WordPress Application” or “WordPress App”.
With design and coding everything is rooted in concept, so what you call something has a lot to do with how the tool is used. Think design patterns. Each design pattern domain uses the same language + dev tools + devs themselves, but saying the name of a design pattern gives you an instant idea of how the code is organized and what the code is to do.
So when you say “Theme” it’s no wonder why 90% of WP sites are top down header, nav, slider, columns of info, and a footer. I mean that’s what a theme is, same structure and tool box of components with different colors (Simplifying here).
I’m not a seasoned dev, but just going off instinct I bet when WP first came out, theme-ing was used to best describe what was going on. Now I think that term undermines what the platform has evolved into and it traps new devs like me into thinking building a site with a slider and a filterable portfolio is what the platform is meant to do, and doing stuff outside of that is some advanced hackery.
Example: As a beginner going by the “WordPress Theme” standard thinking model, I would read books and blog posts and I wouldn’t come close to thinking the first thing I could build with WP is a cross platform mobile music app accessed through a URL on mobile devices. Instead I would probably spend the following months learning how to build and tie together a big conglomerate of web components like a blog, contact forms, galleries pages, 50 different types of sliders, portfolios etc. when there are already a million apps/themes that do this and I would be learning techniques that are devalued because of the millions of others that have been pushed down this specific training path.
Anyway My 2 Cents.
P.S. I do see the value of following the same structure also, reach a bigger audience through generalization and this would turn into code canyon if to much “uniqueness” came about. But it’s kinda crazy when a restaurant site, a portfolio site, and a gym site all have the exact same structure and components… Then it just loops around to that’s the nature of “theme-ing” which doesn’t really make sense if you design a solution for a specific business domain lol, then that loops around to is that a smart thing to do in a mass oriented marketplace (design for a specific business domain)... so you’re back to the basic structure I guess and it all is how it’s supposed to be.
Alright I’m done rambling, anybody else have an opinion?
I’ve made a post asking if this existed in another forum. Here I am requesting the categories since they don’t exist.
Illustrator and Fireworks are used for Interface Design by many designers. I think it would be a valid category to feature on the site.
Fireworks may especially be a good category seeing how a well constructed Fireworks file can have links simulated, along with allowing drastic changes with a few clicks across the entire site (No going through every single PSD File duplicating changes wasting HOURS possibly).
I think it’s silly to only have a PSD Template section. Many interface designers use Fireworks and Illustrator to make their templates. Fireworks itself being specifically built for the task.
Thanks, I’ll message Envato support.
Where would one go to sell Illustrator Site Templates?
By Illustrator Site Templates I mean a product that would have an equivalent purpose to the products listed in the ‘PSD Templates’ section of this Marketplace Site.
So I’m reading the last chapter of sitepoint’s book: Wicked WordPress Themes and Jeffery Way is talking about the GPL license. Basically at one point it suggest that any PHP that is distributed with WordPress themes is GPL territory because it hooks into WordPress…