I am planning on releasing WordPress-themes here on TF again, after being off the market for a few years. As I am employed full-time, and don’t have the luxury of working 100% TF, I am looking for someone to team up with. Someone who can write great theme documentation, set up beautiful demo-websites with my themes and offer excellent support to buyers.
This person needs the following set of skills:
- English as native language, or at least fluent in English.
- Good writing-skills
- Plenty of experience with publishing on the WordPress platform.
- Good knowledge about themes and plugins
- Worked with WordPress for at least a couple of years.
No coding skills are needed, but having decent understanding of the principles of php, html, jquery and css would be a huge plus.
- Writing theme documentation.
- Creating documentation screencasts
- Setting up demo-website for the theme
- Offer support for buyers through our support forum. ( Heavy technical support excluded )
- Update demo-sites when needed (For new theme features etc.)
I am offering a good deal for the right person(s), with a generous commission of our earnings
My part in this will be designing and developing new themes. Hopefully I will be able to create a theme every month or so, depending on the workload at my regular job.
If this sounds interesting, and you think you are the right person for this, please send me an email via my profile page, and tell me a little about yourself.
I never said you should store builder layout data into post_content. I said you need to tie everything back into post_content. I never went as far as explaining any method you’d take to get there. Your post just took the idea I noted and expanded on it with more details of one method on how to accomplish that end goal.
If I understand you correctly, you want the content to be editable in the editor, even it you swich off the page builder, or change themes?
Page Builder by Site Origin does this, although it lacks some finesse in other areas. I also find it better to use native wp functionality like widgets instead of shortcodes. It is also much easier to understand for not so tech-savvy users.
cooledition saidThere is no rule that says you can not zoom in on a responsive website. If some developers do this, it seems like a very bad practice to me.
one of the things i hate on must responsive websites is that you can not zoom in photos. Also many times there are things in the desktop version that don’t appear in the responsive version and that piss me of lol
Show me just one author that doesn’t include shortcodes in his theme, doesn’t include a drag & drop builder directly in the theme, but gives everything via plugins.
I will be able to very soon
For our next release:
All CPTs in separate plugins
This means that users can activate only the CPTs they need, and have access to the data if they change themes.
Front end pagebuilder – plugin
Will not have much front end styling if theme is replaced, but users will still have access to the components and functionality. Also, it makes maintenance easier for me, so it is a win-win situation.
Analytics tracking – plugin
Why should the users have to re-enter their analytics code when changing themes?
Shortcodes – plugin
And where have you dug up this old thread anyway. Close the damn thing before we get another pointless discussion
This is absolutely not a pointless discussion. This is one of the reasons I advice our clients to not use TF themes. You can argue about best practices and all, but the fact is that it is a major issue when changing from one theme to another.
I really can’t see a single argument for having CPTs registered in the theme. For me it is just logic to have as much of the functionality as possible in plugins, and let the theme handle the presentation.
Might it be that a logo (image) is inserted? Probably via a theme options page…
I would guess it was set up to only show site title if no logo is inserted.
Just a bit of friendly advice, focus on one problem before tackling another… e.g. focus on your DMCA tool before you start another project to `fix` support.
Well, that was probably very helpful. You know, some people can actually have more than one thought at once….
johnleebkk: I am sure that would be much appreciated by buyers. I would think the closest thing we will see is an improvement in the item-discussion area. Perhaps some search-functionality will come one day?
Pirenko saidYou could not select which formats to enable in 3.6 beta. I am aware that you can in older versions.
Like many others, I found the UI pretty confusing. Also, I think there are far to many post formats. I would also like to have the ability to turn off some of the formats. Why would I need “Aside-format” for my portfolio-posts anyway?Actually you can already decide what post formats you want to add support. So you can turn on/off whatever you formats you want. More info here: http://codex.wordpress.org/Post_Formats
Anyway, once again, the big problem is that they look incomplete and this leads to a non standardization of treatment and implementation across different themes.