Hi There, I have a theme framework which makes wordpress into a more dynamic system entirely, it’s been used on some big and pretty groundbreaking sites (.. sorry for the brag just trying to avoid any ‘we dont like experimental engines’ type assumptions). The big question is that it substantially changes the default wordpress template hierarchy.
It still resides in the themes folder and is fully compliant with WP and plays nice with plugins.
Question: Would this be a black mark against it’s acceptance?
Thanks very much!!
Excellent! Thanks Mushin.
Hi There, If my theme were to have a load of extra functionality to add into WP. Would it be better to bundle this into the theme or branch it out into wordpress plugins?
Thanks very much
It’s more of a webapp style framework for making single-page apps. makes use of localstorage, pushstate etc and is REST based. I’ve used it from everything from boring stockbroking applications to 3d particle data explorers. I got bored with my custom build CMS recently and managed to port it to wordpress so… here goes
I’m thinking of making something fun… havent thought of it yet.. From reading the WP API … I’ll just feel a bit limited without my trusty steed beside me.
Most likely noone will want to buy any of my weird stuff lol.
yeah, I know wordpress does, however mines better
Hmm perhaps I should ask this another way:
Its all standard PHP no server additions.
Hi there, This is my first question here so if I’ve missed anything please go easy
I have my own framework which I use to rollout front end sites it’s very stable and has been in development & production on some pretty big well known sites for over 5 years.
The problem is that it uses dynamic bootstrapping tools like SASS (php port), on-the-fly minifiers within it’s core and has it’s own ‘enqueue’ features that have quite a few more features.
If I make templates for theme forest do I HAVE to use wordpress’ enqueuing or is this more of a guideline?
Thanks very much