WordPress Ideas » Tag: easy - Recent Posts

Jack Tummers on "Better content blocks for CMS capabilities."

Jack Tummers — Wed, 08 Aug 2012 08:30:41 +0000

I agree on all of this. Now I'm working on a large project with several content parts and using the secondary content block plugin. Works fine, but I fear the day the plugin is not working anymore... I really think this functionality has to be part of WP core.

Justin Tadlock on "Easier Theme Options"

Justin Tadlock — Mon, 09 Jul 2012 03:43:05 +0000

WordPress already has the Settings API. I'm not sure what more you need. It's simple and fits right into the WordPress UI.

Ipstenu (Mika Epstein) on "Easier Theme Options"

Ipstenu (Mika Epstein) — Sun, 01 Jul 2012 05:51:39 +0000

I'm not sure what you're asking for... Obvioulsy if the theme frameworks can do it, the APIs and hooks are there. Theme options are the venue of the themes.

brightweb1 on "Easier Theme Options"

brightweb1 — Sun, 01 Jul 2012 02:41:51 +0000

Currently, we need to develop a theme options from the beginning and the API Settings are limited. Googling I found a lot of frameworks* that turns the work easy. Why not implement an simple way to customize our theme like this?

Framework for Theme Options:
Options Tree, WordPress AdminPage Class, Options Framework Plugin, NHP Theme Options Framework, ProPanel WordPress Theme Options Panel, CheezCap – Cheezburger Custom Administration Panel, The UpThemes Framework.

scaup452 on "Make Themes easier to locate"

scaup452 — Thu, 31 May 2012 22:09:27 +0000

If the themes were arranged in category format, they would much easier to locate.

mogito on "Better content blocks for CMS capabilities."

mogito — Mon, 29 Aug 2011 21:35:09 +0000

what?
1. You should have the screen option to turn any number of content blocks on.

2. These content blocks are EXACT replica's of the main content block including media buttons and formatting. You should be able to interact with these content blocks in the same way as the main content block.

2. There should be radio button options and template tags so technical and non technical users can specify where they would like to use these in the theme ( pages AND posts ).

3. The content blocks MUST be completely readable by RSS feeds. This is where current plugins fail most urgently. For example - if you have text in one content block and images in another content block - both should be picked up by your feed.

Why? because fafing around with "more" tags is tedious and NOT USER FRIENDLY. There are plugins, but these do not do the job. WordPress has come on leaps and bounds with regards to becoming a fully functioning CMS. Changes like this would help it along even further.

converting2wp on "Payment System to download Plugins and Themes (Extends) right in WordPress.org"

converting2wp — Mon, 25 Jul 2011 14:12:41 +0000

Added your link to an idea I just posted:
http://wordpress.org/extend/ideas/topic/need-a-curated-cross-ref-between-ideas-and-plugin-repository

Papawaya on "Payment System to download Plugins and Themes (Extends) right in WordPress.org"

Papawaya — Sun, 24 Jul 2011 11:31:22 +0000

I think the plugin system needs a thorough review, from top to bottom ( in order to meet the needs of the hugely growing community) ---there are a huge number issues with it both from the developer point of view and from the user .... .. and your idea too draws up a large number of questions too.....

Maybe WordPress core needs to try and set up some working parties of users and developers to spend 2-3 months discussing the issues and the way ahead and to then bring forward those recommendations and suggestions in order to forge a design/process for 2012/2013 ..... the web tools and communication systems mean that the group members can be anywhere really and contribute ...

Once we have a few draft proposals which propose a step by step change for the better we can then look at maybe an i-tunes like system as one of the options ... which could be ideal for accessing them and rating and being able to sort and find them easier

the problem with a $1 fee etc is that you could for example have 3000 people all making say a Google+ plugin all fighting for a slice of the revenue .. is that really what we want?? Would just 10? FREE GooglePlus plugins with variouss options, well made and thought through be better for users ..than the rushed out first out the box for the dollar share ..( imagine with 50 million potential users you have a potential money spinner ) with quality falling ??

Alot to think about
Just my thoughts ....

Clifford Paulick on "Payment System to download Plugins and Themes (Extends) right in WordPress.org"

Clifford Paulick — Sat, 23 Jul 2011 12:29:12 +0000

If there's already a similar idea in here, please link to this or link to that.

Clifford Paulick on "Payment System to download Plugins and Themes (Extends) right in WordPress.org"

Clifford Paulick — Sat, 23 Jul 2011 12:27:52 +0000

Summary: Like turning the Repository into the iTunes store. Devs can release plugins and themes for free or for $1 or for $10.

Current:
1) Developer makes a plugin
2) Developer (kindly) releases into WP repository for free
3) Developer includes a "Donate" button inside the plugin's administration
4) No/Few donations - apparently not enough to keep up with development or support
5) Plugin abandoned, but current and potential users don't really figure that out until after a year of no one ever hearing back from the developer or after realizing it is no longer compatible.
6) Repository is littered with plugins that aren't compatible with the latest WordPress (I know, some people don't upgrade - maybe for the reason that they just HAVE TO HAVE that plugin) and/or aren't supported (not even by the community).

New Idea:
1) Make plugin
2) Release in repository, set price of $1
3) Can still include "Donate More" button
4) Every download charges me automatically $1. Developer doesn't get my contact information (unless I want them to), doesn't feel as compelled (maybe) to include a "Donate" button everywhere all over the plugin, and is much more likely to continue supporting a plugin that has 20,000 downloads. Also helps not to have to maintain a Lite and Premium version - but they could if they still wanted to.
5) Plugin not abandoned by the community or the developer/support.
6) Repository is of higher quality if less plugins are abandoned. (And incentive for more developers to release.)

Considerations:
A) If plugin becomes abandoned or incompatible with latest version of WordPress, it automatically becomes free.
B) Pay each time to download to a different install? I don't see why not if it's only $1.
C) Or, you could just attach the WordPress Extend "Market" to our WordPress.com logins, as long as we have our blogs setup in there (like JetPack or WP.com Stats).
D) All updates mandatory no charge (just like iTunes store) - keeps things working nicely together and encourages updating to the newest release of WordPress.

Thoughts? Feedback?