You also have to prioritise which functionality should be developed, with regards to the costs and benefits involved. Thus, it is important that you have overall knowledge of the platform involved, knowing what is straightforward and what is difficult to do, since there is otheriwse a risk that valuable time is spent on functionality of little interest to the end customer.
We do not want to leave you alone with all these tasks and thoughts. Thus, Atex Web CMS is offering a course for you who have a non-technical role in a Atex Web CMS project. We offer the knowledge foundation that you need to bring the technical part of the project to shore.
We discuss the needs that can motivate the decision to buy a Content Management system for your organization. What is the difference between an Enterprise Content Management system and a basic publishing
What are the main needs that Atex Web CMS fulfil?
In what way does Atex Web CMS see Content Management?
The thoughts that once inspired the Atex Web CMS developers to build a Content Management-system are still relevant today.
We look at the functionality within the Atex Web CMS product, the adjustable functions and the functionality that needs to be built. What corner stones does the developer have at his/her disposal?
The Atex Web CMS publishing functions are built on a template system with input templates, which control the format of the information being entered, and presentation templates, which control the appearance of the information being presented on the website.
What does the Atex Web CMS user interface look like, and how does it work? What are the configuration possibilities?
We will also run through the environment that surrounds the Atex Web CMS Content Manager in your organisation, and look at how Atex Web CMS can interface with other systems, and with other functions within the organisation.
Basic IT knowledge
No
½ day