Edit from frontend or backend?

[EliezerIsrael]

To record the scale of a pattern, there's a custom taxonomy applied to patterns.

The WP_User_Frontend plugin, which is used to let users enter patterns form the frontend, doesn't natively support custom taxonomies.

The plugin author says that it can be extended to support this, and points to:
http://tareq.wedevs.com/2012/04/how-to-extend-wp-user-frontend/

[theo-armour]

Can you explain what this plugin does, that you need, that is not within the capabilities and limitations of say a 'contributor' role in WP?

[EliezerIsrael]

It's a good question. I'm beginning to ask myself as well.
I had thought to keep front-end users entirely on the front-end - letting all pattern editing happen on the front-end.

"why", you ask? I had thought that would make the user experience simpler, more unified, and less daunting for the layman.
I'm realizing that the tradeoff - having to recode things that are already built quite well in the backend, is likely more trouble than it's worth for an alpha.

[EliezerIsrael]

(Changed title of issue to reflect changing conversation.)

I just investigated the built-in roles system, and how the backend looks to various roles.
It could work. The built in roles are subscriber (which is a reader, essentially), contributor (can write but not publish), author (can publish and edit own work), editor (can edit other's work), and admin.

There's a little bit of hiding of capabilities that would have to happen on the back end, but generally, it looks pretty good.

Changes I would suggest in this direction:

Contributor/Author/Editor role:

• remove 'post' functionality
• remove 'tools' ('press this') functionality - (or else figure out what to do with it.)

Editor role:

• remove 'links' functionality

All

• set first-page after login appropriately. Likely the home page for subscribers/contributors/authors and dash for editors?

[theo-armour]

Changes I would suggest in this direction: ...

WP has a well established 'pattern' for roles and capabilities. I suggest leaving the capabilities as they as much as possible are until the actual patterns established by our pattern-makers begin to dictate the changes/improvments.

set first-page after login appropriately.

Everybody should see the default home page every time they log in - even if only for milliseconds:

The home page is our product. We need people who love looking at the pages they make for others to look at.

Also, frequent viewing increases the likelihood of spotting a malicious hack or bug more quickly.