Question about widget areas / unlimited sidebar implementation...

[128]

Hey Jason. I know this isn't exactly the best place to ask you this, but I would be super grateful for any insight you could bestow...

I've been working on developing my own framework and came across one of your posts on TF about Sidebar Generator plugin. It was from 2 years ago, and I was curious if you ever switched to a different method or just kept developing/updating that code?

With newer more feature-rich options available, I was wondering if you would still recommend the SG plugin or suggest a completely different route? Any guidance possible would be much appreciated! (though I totally understand if you rather keep that info to yourself)

Thanks

[themeblvd]

I think what I used to do is simply refer to people to use that plugin because it would just work with most themes. And then I had a video I'd link people to on how to use it. I don't think I ever actually directly implemented it or anything. I've never really liked copying people's plugin code into my themes.

I don't think the authors of that plugin are actually keeping it up anymore. I haven't personally tested it with the latest version of WordPress, so I can't say if that is a good option or not. Have you looked around for another? I have to imagine there is something out there that you can simply refer buyers to use.

A year or two ago, I basically threw out everything and built this new framework from scratch (aside from little jQuery plugins, Bootstrap, etc). This new system for implementing custom widget areas is so complicated and nested within the framework, I wouldn't even know where to being in explaining, to be honest.

http://dev.themeblvd.com/tutorial_category/chapter-08/

This plugin sets up the admin panel to manage the widget areas: https://github.com/themeblvd/Theme-Blvd-Widget-Areas

And then in the framework, when it's displaying the website, it goes through a process of checking for this plugin being installed and checking for any custom widget areas that might exist before figuring out what to display in each "widget area location" as I call them - the default widget area or a custom one if it exists and is assigned to the current location and current page.

[128]

I figured that was probably the case. No need to explain the overly complicated stuff. The only PHP I know is from designing/coding around WP front-ends for the past 6 years. Learning that the Wordpress template system consisted of more than just template tags has already opened up a whole new world of brain hurt. Half-way through this lynda.com php tutorial and I'm still grasping at straws.

Fortunately for myself, at least at this stage, I'm willing to piece together certain code (metaboxes, etc) from different sources, as long as I'm understanding the concepts and learning in the process (though never copying.) I figure once I go through the code to implement WP standards and research everything thoroughly enough, I'll end up wanting to start over from scratch with what I've learned.

As for requiring other plugins, I do eventually intend to try and sell the themes, and while even though I'm a complete PHP newbie, I don't want to send that vibe to users. (which requiring woosidebars would probably do lol) I should probably download your plugin and see if I'm able to understand how you're accomplishing it. I've only glanced at the code in the framework; the parts I could comprehend anyway. Pretty obfuscated to my virgin eyes.

Another thing I wanted to ask you is: If I'm understanding your code correctly, are you ultimately using your heavily modified version of options as a base for the admin modules? I've experimented a lot with OT, but I'm really wondering why everyone seems to still use the older version? Is it more versatile or do people just not want to have to rebuild their framework to support it?

Thanks again for the help. I certainly appreciate it.

[128]

Oh, and I've been meaning to ask: are you going to release a theme to wordpress.org in order to drum up consumer interest in jumpstart?

[Larceniii]

I dont see how a jumpstart childtheme could be released on wordpress.org

[128]

Nah. It wouldn't be anything even close to jumpstart. Though if you design a really good free theme that a lot of people download and use (and keep it updated) it becomes a huge source of traffic, publicity, and a huge revenue stream if converted properly.

For example, pagelines, crazy drag and drop premium Wordpress theme amazingness. Wordpress repository theme version == super duper lite version with just enough to get people interested: http://www.pagelines.com/ http://wordpress.org/extend/themes/pagelines

Most themeshops have done it, but Wordpress doesn't allow blatant advertising so it really comes down to how much you value the traffic and your conversion rate.

100 visitors per week isn't a lot to some people, but if your LP converts at .05%, you'll average $3.25 per visit. People are paying $1 per click on adwords for extremely lower quality traffic. Judging by the current landing page and call to action, I would assume it's a lot closer to .01% or lower depending on the quality of traffic.

[Larceniii]

That's a good point.

I wonder how it could be limited in such a way though?

[themeblvd]

@128 I'm not sure I'm quite clear on what you're asking about the options. I actually originally used Options Framework plugin by Devin Price and since have adapted it quite a bit and extended it to work with a API system I've created. -- http://dev.themeblvd.com/tutorial_category/chapter-05/

I definitely want to create something for wordpress.org eventually, but right now I am just too far behind on everything I'm doing. Some day I'd like to create a more simple theme framework and make themes for wordpress.org.

[128]

Larceniii, it's because they're hand reviewing each theme for malpractices to withstand the integrity of the repository.

I guess what I meant was, I've only seen probably one premium theme (that I could tell) that was using optiontree, yet I notice that you and many others just never upgraded which seemed kind of odd to me.

I see your plugins are getting publicity being out in the wild. I wouldn't look at it so much as redeveloping something magnificent, but instead as just getting more eyes on what you're working on. Anything with a good design stands out in the repository, but if you were able to also quickly demonstrate what you're trying to accomplish with WPJS I think a lot of people would find value in what you've done so far. (just in the docs alone) That's one thing your project definitely has going for it, you're giving the newbies a jump start while everyone else seems to be closely guarding their "trade secrets." It's either that or the WP dev guys sitting on the sidelines heavily criticizing it's users for using their product the best they know how.

Since asking the other day, what I've put together so far is bootstrap 2.3, Fontawesome 3.0.2, halfway configured the shortcode route I'm going to take, decided on sliders and where I'm going to implement them, and got at least a little bit of my options panel worked out.. (Can't decided if I'm going to go all out with the customization) Now I was thinking about integrating all this into underscores theme, but I'm really torn between going the canvas route. It just doesn't seem like a clean base to start out with even though I'm really used to it. Would love some advice.

Are you still developing TF themes in the future? I'm so ready to be done with the backend stuff and start on the beautification, but I know I'm going to have to end up developing a layout builder just to compete with other listings. Been thinking about just rolling the dice and see what happens instead of perfecting anything.