Sometimes we need to give different tasks to different admin-users in our word-press blogs, in order to do so, we need to have some way to give them what we want, and just that. The safest way to do it is the WYSIWYG way, “they will only get what they see”.

This means you will only show them the menus or options they are supposed to act upon. We can achieve this by means of the Word Press roles “user level capabilities”, as was described in the previous article (“Word Press roles and capabilities“), and that will here be put to practice.

There are pre determined admin-roles in every word press installation.
This means every registered user can have a specific role, with specific capabilities within the blog.

This capabilities, relate to  access levels, and are granted by the blog’s administrators.

This doesn’t mean that a user can’t perform someone-else’s task, it just means it will only be able to  do  a determined number of tasks, allowed by his user level.

“Every user with an access level can do  everything his access level allows, plus all the capabilities of the user levels bellow.”

The Word Press roles and Capabilities hierarchy will be described in this article, along with the allowed admin-tasks for each level or role.

2 Comments »

Word Press Accessibility: The <noscript> attribute.

The basic rules of accessibility state that you should always provide alternative content to users no able to access it, if you rely only on scripts to deploy it.

No one should be left out, and all users are entitled to have a similar “rich browsing experience” regardless of their personal physical challenges.

With this article I intend to bring your Word Press websites a bit closer to what I state in the previous paragraph that sometimes, to some people seems like a utopia.

Let’s get our hands dirty with code!

1 Comment »