A listing of the theme plugins currently developed and available on a Try ‘n Buy basis. Generous interest free payment options for business start-ups. Click on the Details and Download link for further information and to download product or see this same list pre-popluated with default items and have it built for you.
0001The Plugin Theme:Detects device used. Allows for user to override. Details and Download.
0500Setup:Theme settings. Registers menus, post thumbnails, etc. Details and Download.
1000Body:Important switching functions for the rest of the site. Details and Download.
1100Header Title:Site title, description, logo, search form, menu. Switchable. Details and Download.
1110Announcement Bar:Can be used for announcements. About 35px high. Details and Download.
1120Header Widgets:Three widgets across. Details and Download.
1200Body Middle:The middle of the page. Typically used for pages and posts. Details and Download.
1220Middle Widgets:Two rows and four columns of widgets. Switchable. Details and Download.
1310Footer Links:A flat list of static links. Details and Download.
1320Footer Widgets:Three widgets across. Switchable. Details and Download.
1330Footer Devices:List of device templates available/selected. Details and Download.
1400Body Left:Typically refered to as the left sidebar. Details and Download.
1500Body Right:Typically refered to as the right sidebar. Details and Download.
2100Nav Top Flat:A flat list of menu items. Can include search form. Details and Download.
2300Nav Bottom Flat:A flat list of menu items. Details and Download.
3100Device Mobile:Mobile Theme. Details and Download.
3200Device Tablet:Tablet Theme. Details and Download.
3300Device Desktop:Desktop Theme. Details and Download.
3400Device HD:HD Theme (1920x1080) Details and Download.
3500Author HD:Author Info (Scholar) Details and Download.
4100Search:HTML5 Search Form. Details and Download.
4300Images:Sets image sizes (HD, desktop, tablet, etc.) Details and Download.
4400Not Found:Not Found Template. Make it interesting! Details and Download.
5100Fonts Droid Sans:Droid Sans (headings and all other text) Details and Download.
5210Fonts Slabo 27px:Slabo 27px (headings) and Roboto (everything else) Details and Download.
6000Wireframe:Displays a light dotted outline around major elements Details and Download.
7000Responsive:Very lightweight responsive CSS. Details and Download.
7100Effects:Transitions to "soften" effect changes. Details and Download.
8200RGB Green:Green. Pick a base color you like and work from there. Details and Download.
8300RGB Orange:Orange (ditto). Details and Download.
8500Texture:A texture like grit, etc. Details and Download.
9100Business:A combination of elements geared toward a business look. Details and Download.
At this time, no discount is being applied to bulk orders. This is to encourage innovation for individual plugins, to help keep quality high, and to help differentiate between the functions each plugin supplies. So often I here, “Well, you just have to… do x, y, or z.” Well, true, but in the real world of mufflers, transmissions and performance tires, the buyer instinctively knows that “just” adding another tire will add another $100+ to the total price tag. These plugins are like that.
Again, The benefit of this approach is that the code in each plugin is much more compact, making it much easier to understand, debug and modify. A spark plug or a cylinder in an engine might be a similar comparison. There is a balance between the number of cylinders, raw power, torque and speed. Here you can install just the plugins (not spark plugs!) you need so that you can keep a watchful eye on the balance between functionality and performance. If you “just” need a left sidebar. Just install the left sidebar plugin. The compact size of each plugin means there is not much of a performance impact for each one. Separating them out, means you can keep your site just as lean as it needs to be. (No pun intended!)
In addition, and in keeping with the car mechanic motif being used here, the settings for the plugins are contained almost exclusively in the data.php files. First this makes the plugin easier to create, as code is typically written in a text editor on a desktop computer. Putting the settings in a text file (at least at first) is the natural choice). Second, putting the settings in a text file that can’t be directly accessed from the online admin section (where pages and posts are normally written), means that no one can “mess them up”, either by choice or inadvertently. This keeps them more secure.
I often wonder at the wails of grief in the online community where this, that or the other setting can’t be found, where people are essentially thrown to the wolves. See that pile of two by fours, concrete, asphalt shingles and wires over there. Go build a house. It’s free! We all know the mess that would ensue. Yet this is exactly what happens when people try to build their own site.
With this approach we split the difference. You have here some “flat packed” cabinets. “All” you have to do is pick which ones you want, upload them and configure them. I still think the configuration part should be left to someone who has a working knowledge of WordPress, MySQL databases, HTML, CSS and the like. That way if anything goes wrong (and it often does), you have someone there to help.
A moderate goal I have with this approach is to do all (or most) of my coding in advance, so that when it comes time to actually build out a site, all the tools and pieces are their in neat order. Any actual modifications that need to be done to the underlying code should be minimal, and if I need to create a slightly (or vastly) different footer, sidebar (body left), or any other piece of a site, I can simply copy the plugin over to a different folder, assign it a different name (in keeping with the numbering schema being used here), and I’m off to the races.
To be honest (and to let you know part of my background), this approach is based on a tonne of real world experience, dealing with crops, wagons, pigs, fields and the like. This is the approach that has to be used there. Set yourself up, build the pattern you need. Then carry out the rote work. So, I hope that provides some background and motivation to pay the “full price” for web development, done in advance. It works in the real world, it should work here as well.