Admin Interface
All content in the system can be managed through a single admin interface at /admin/content. This single admin screen provides a filterable table view based on:
- Content type
- Source feed
- Categories and tags
- Created date
As with all screens in the admin interface, the view is drag/drop configurable to meet changing requirements without the need for new custom code.
New content can be created by navigating to Content > Create Content in the admin toolbar.
Taxonomy is used is used to relate entities, such as content, using descriptive and fieldable terms.
Individual taxonomy items are called "taxonomy terms", and "taxonomy vocabularies" are used to group terms together and provide different fields, logic, and anything else per vocabulary.
Example taxonomy vocabularies:
- Tags
- Categories
- Event type
- Company type
- Podcast season
As a global practice, all options lists on entity forms (such as article form) are built as taxonomy fields. Because taxonomy terms are fieldable entities, this practice provides the greatest amount of flexibility in meeting future requirements.
Users can be managed at /admin/people. The client administrator role has permission to create and edit users.
Users can be put in to "blocked" status without deleting their account. This will preserve the state of their user account while blocking the user from logging in to the system.
As a global practice, media entities are created whenever images, documents, or other file types are uploaded in to the system. Media is managed as an extension of the Drupal media_entity module.
But media entities are not necessarily limited to uploaded files. Instagram posts, Youtube videos, tweets, and other things on the internet could be normalized in Drupal as media entities.
This system is role based, meaning we can create any number of roles and associate any set of permissions with those roles. Any user can have any set of roles, and they gain all permissions associated with all of their roles.
Below are the important roles currently used by this system:
| Role name | Description | Example permissions |
|---|---|---|
| Client administrator | Provides access to manage content, media, and anything necessary for client to manage the application without exposing unnecessary or dangerous permissions. |
|
| Administrator | This is a super admin used by developers with more risk. |
|
| Authenticated user | Any user authenticated in to the system. If and when this system allows anonymous user registration, those users will have this role. |
|
| Anonymous user | Users who have not authenticated in the system are given this role |
|