The content types in Drupalcms help you adhere to our guidelines for customer oriented web pages. For example, certain fields are required, and you can only enter content in a certain way. Nevertheless, as an editor, you still have considerable freedom to enter content and create web pages. We assume that you, as an editor, also adhere to the applicable editorial agreements.
This page outlines some of these agreements. For more specific agreements, see the entry guidelines per content type and the content quality checklist.
Content layout
The website's layout is based on customer journeys and topics, not our organisational structure.
- Visitors don't need to know how our university is structured (and therefore which organizational unit handles which topics) to get answers to their questions. When multiple organisational units work on interrelated topics, they jointly maintain one (or a set of) pages on that topic.
- Information about a specific topic is placed into the appropriate customer journey within the site structure. For example, information for students appears in the student route (under ru.nl/en/students), information for those seeking further development in their field appears under ru.nl/en/education/education-for-professionals, and so on.
- Organisational units that consider it important to promote not only their services but also themselves can use their organisation page. See the guidelines for setting up organisation pages. A few exceptions: POPs can use their section pages, research institutes can use their landing pages, and faculties can use their faculty pages under "About Us". (Faculty content for staff, students, etc. should still be included in the relevant customer journey.)
When publishing pages that aren't automatically accessible via an overview (such as a news overview or calendar), these pages must be included in the website's menu structure. The only exception to this are campaign pages that are separate from the website's content.
- Editors are not permitted to add pages to the menu or modify menu items themselves. Menu management is handled centrally. Faculty key users are permitted to manage the submenus of faculty pages under "About Us" and the submenus of their research institute landing pages. They must report any changes to the central menu manager.
Content may only be published in one location on the website, meaning that all content may only be accessible via one URL and appear in only one place in the menu. If the same content is relevant in multiple places in the customer journeys, do not create a duplicate page but link to the existing page on the topic. In exceptional cases, a canonical URL can be assigned to a duplicate URL.
- If content (such as an event) needs to be displayed in multiple sections, publish it in the central overview. Don't create multiple copies of it in all relevant sections.
Translations
Our website is bilingual. Therefore, in principle, both Dutch and English versions of all pages must be published.
The translated content is identical to the content in the other language: the content isn't tailored to either the Dutch or the international target audience. This is because Dutch-speaking visitors sometimes use the English version of the website, and international visitors sometimes use the Dutch version. Not publishing content in two languages can lead to your content being overlooked by some visitors.
Is your service's target audience (e.g., an event) exclusively for Dutch speakers, or is the primary language English? Even then, the content needs to be translated. Clearly state the primary language in the service description.
Disclosure of information
The basic principle is that all information on the website is public. This is to ensure that our content is easily found via Google, as current employees and students also frequently use Google to find content. Information intended for a limited audience belongs on the intranet, in Teams, etc.
However, there may be situations where information belongs on the website but is better not published publicly, for example, due to competitive considerations. Consider, for example, the publication of special rates we've negotiated with third parties to enable our employees to use their services. In that case, it's possible to make pages containing this content accessible only to visitors who log in with their student or employee accounts. Publishing this type of restricted content is only possible upon request and in consultation with the website core team.
To make the content discoverable for visitors who are not yet logged in (who cannot see the protected content and therefore do not know of its existence), the guideline is to also create a public page about the topic, and link to the protected page with additional information.
Editorial model
To maintain the quality of the website, we strive to have as few editors as possible and require that editors have sufficient knowledge and time to perform their work properly.
- Editors are assigned a role according to the editorial model.
- Key users and DMC team leads carefully consider the composition of their editorial teams. They request editorial roles for as few employees as possible and ensure that these employees have the opportunity to acquire the required skills and have sufficient time to perform their duties. They remain ultimately responsible for the quality of the web pages their editors produce.
- Editors will be assigned an editorial role that aligns with their responsibilities. Key users will not request a role with more Drupal rights than necessary.
- All editors must complete Drupal training before working in the CMS. They must also complete any other mandatory training courses within six months of starting their role.
- Student contributors should never be given ultimate responsibility for a (specific set of) webpages; they must always have a staff member who supervises them and bears ultimate responsibility. Student contributors should not be given a higher editorial role than Communications Assistant.