Content Model
We organize types of materials, fields and connections. News, service or implementation can have their own, clear way of editing.
Offer / BXM Multimedia
CMS BxM Administrator Content under the control of the team.
BxM Administrator is a proprietary content management system for extended services. We select modules, roles and rules of publication to the content of the website and the work of editors.
Let’s discuss your projectCMS BxM AdministratorIdea → project → implementation
Customised to your company
What can we prepare?
Roles and publication
We determine who adds, changes and publishes the materials. We adjust the powers and the workflow to the responsibility of the team.
Modules and development
The scope of the panel is based on the project. We discuss additional functions, integrations and expansion possibilities along with the service.
Implementation and further cooperation
CMS matched to the team.
The advanced panel should order daily work, not require knowledge of the code. The scope of modules is due to types of content and division of responsibilities.
Content Model
We define fields, links and modules needed for editing.
Roles and publication
We set the permissions and how changes are verified before publication.
Panel expansion
We develop new content types, integrations and permission changes with the service.
Service Guide
Page panel expansion: modules, roles and integrations
The Advanced Panel organizes tasks beyond simple text editing. It can support a directory, reports, editorial work or data exchange, while maintaining control over access and changes.
When you need to configure, and when a new module
First we check whether the need can be handled with existing functions. The new module makes sense when a separate data type, acceptance or integration process appears, which the current panel does not support. Adding fields without the model being ordered quickly leads to difficult maintenance of the form.
We describe an example of a task from start to finish: who starts it, what data it introduces, and what result it receives. We also set exceptional cases. This helps to separate the necessary range from the functions that can be added after checking the first version.
Expand Subject:
Powers and history of important activities
Access may depend on the role, department or assignment to a particular record. The limitation cannot only consist of hiding the button. The system should also check permissions when recording, exporting and downloading data through integration.
For important operations we record the necessary trace: who, when and what the change was about. The scope of the story is selected for the process, avoiding unnecessary collection of confidential data. We also agree to withdraw permissions, replacements, and how to respond to user errors.
Expand Subject:
Integration requires error handling
Importing data, sending messages or syncing the directory can end in part. The panel should show the result of the operation and allow safe re-renewing. Identities and rules are needed to protect against duplicates.
We determine how long the task can last, who will see the error and whether the editor's work is to wait for the external system to respond. Automation must have a clear state and control capability. If the AI appears in the process, the result and scope of the independent operation are subject to separate rules.
Expand Subject:
Development without destabilising the existing site
Before changing, we analyze the dependence with the public part of the service and older data. The new field may require migration, default value or change the view. We prepare a copy and test on an environment separated from the current work.
The reception includes user scenarios and checking that the existing functions are still working. We document new permissions and the way the module is maintained. After publication, it is worth observing errors and collecting comments from the users of the panel before the next expansion stage begins.
Expand Subject:
Example: acceptance stage before publication
The author prepares the material and submits it for verification. The editor can either send comments or approve the publication. In the panel, you need unambiguous statuses, information about the leading person and the history of the most important changes. The "public" button itself is not enough to handle this process.
We describe what happens after the amendment of the already approved text, change of author or absence of editor. Notifications should be sent to the right person and not repeated without reason. Such a module is tested on several roles, also when trying to open the record by the user without permission. It is only possible to assess whether the process works.
Good start.
From Chatting
to a particular plan.
We set the goal, scope and way of receiving the work. We develop the project on the basis of agreed needs and materials.
See our realizationsWhat is worth preparing for the conversation?
- Types of published material
- Number of editors and their responsibility
- Modules, integrations and current data
You don't have to have the specifications in place, and we'll work out the most important decisions together.
Before the first conversation
It's worth knowing.
Does CMS require knowledge of programming?
The daily edition takes place through the panel. Before submitting, we determine the scope of the editors' tasks and show how they are performed.
Does every user have access to everything?
We set the scope in the project, including editors, authorising persons and administrators.
Can integration be added to another system?
First we check how data exchange, documentation and scope are exchanged. Integrations are valued and planned as part of the implementation.
What is the content transfer to the new CMS?
First we check available export and data quality. We establish field mapping, addresses and elements that need manual correction. Sample import allows to detect problems before changing the service.
Your next step
CMS matched to the team.
The advanced panel should order daily work, not require knowledge of the code. The scope of modules is due to types of content and division of responsibilities.
Let's start with your idea.
Write a few sentences about the project or call me.