1. You fill out the proposal for a relocation website (below under “Apply for a website”).
2. You will receive a new website on the new server with a new address, pre-filled with your desired template.
3. You set up your website using the enclosed checklist and fill in the template with your data.
4. Your new website is public. If you don’t want anyone to see the intermediate state of your website: Set to private works for all pages in Dashboard > Pages > check all > Click on Edit for multiple actions > Take over > Status > Private > Update. Set links, assign parent page, integrate in menu only works for public pages. Draft also works. Password protected does not really work.
5. Which web addresses should also be found after the move? Avoid “Page not found”. Name the pages exactly the same as on the old website. The effect is then almost like a redirect to the old website!
   Wenn die Seiteninhalte in der neuen Website in einer anderen Seite enthalten sind, können Sie übergangsweise von einer neu angelegten Seite mit der gleichen URL auf diese andere Seite verweisen.
   Dies macht es Benutzern und Suchmaschinen einfacher, die Inhalte in der neuen Website zu finden. Seiten, die nur solch einen Verweis enthalten, löschen Sie nach einigen Wochen.
6. Never link “back” to your old website! The addresses of all old pages and files change when you move from yourwebsite.uni-mainz.de/pfad/ to www.blogs.uni-mainz.de/pfad and are therefore no longer accessible.
7. You can move intern information to Sharepoint. You can find more information here Teamweb: Documentation and FAQ | Center for Data Processing (uni-mainz.de)
8. The English version should move at the same time, otherwise there will be chaos in the links of the English version.
9. If you want to keep the website permanently locally for archiving purposes, back up the old website using httrack, for example. If you only need the old website for some time after the move to look something up and compare, this is unnecessary, as the old website will remain intact for months!
10. You are finished with the move and notify us that the address can now be moved. Allow 2-3 working days for the address change to be distributed on the Internet.
11. By now at the latest, your new pages must no longer be private . Otherwise you will receive a “Page not found 404 error” after the address change.
12. We are moving the web address of the old website to the new one.
13. The old website is now protected from public access. Only pages are protected, not items. You can reach your old website at: https://www.blogs.uni-mainz.de/subsite-teilen-wir-ihnen-mit
14. The old website with all its files will be retained and thus represents a complete data backup at the time of the move!
15. We will email you the access link after the move has been completed.
16. Last step: full deletion of the old site after three months.
17. These websites already use the new layout (as of February 2025)

You should reuse the URL of your web pages. If the trailing part of the URL is identical in the old and new websites, you will achieve a search engine-friendly move without “File not Found” errors!

All addresses and their names for monolingual websites:

Before the move:

• Old website:
  • Primary domain: ihrinstitut.uni-mainz.de
  • Subsite address (invisible): www.blogs.uni-mainz.de/dies-bekommen-sie-von-uns
• New website:
  • Subsite address: cms.zdv.uni-mainz.de/dies-bekommen-sie-von-uns
  • Login: cms.zdv.uni-mainz.de/dies-bekommen-sie-von-uns/wp-admin

After the move:

• New website:
  • Primary domain: ihrinstitut.uni-mainz.de
  • Subsite this address remains invisible: cms.zdv.uni-mainz.de/dies-bekommen-sie-von-uns
• Old website:
  • Subsite address: www.blogs.uni-mainz.de/dies-bekommen-sie-von-uns, this address will remain with all data for 3 months after the move.
  • Login: www.blogs.uni-mainz.de/dies-bekommen-sie-von-uns/wp-admin
• Links within the new pages are retained even after the primary domain has been moved, the new address is added.

Each page consists of blocks. The block list describes the block and refers to the detailed instructions with examples in the demo website and the video instructions.

Blocks that dynamically display data from other systems such as FIS = publication lists, IdM = persons and organizational structures, Jogustine = courses are particularly labour-saving.

Header icon, site title, quick links footer and menu are all set in the Customizer. Go to Dashboard → Design → Customizer and take a look at the options.

• Footer: Easy language, accessibility, imprint, data protection: You must take care of the content of these pages.
• Imprint: Each page requires its own legal notice. The copy template contains the imprint of the home page. Enter your editorial team as the contact.
• Data protection: We use JGU’s central data protection statement in the copy template. If you collect additional data, for example in forms, please contact the data protection officer if necessary.

We can set up multilingualism at your request. WordPress Multilingual = WPML automatically translates your texts.

1. The future Translation Manager (very possibly that might be you) must have successfully logged into the site at least once.
2. We configure the translation software WPML for you.
3. The translation manager gives himself and his editors translation rights.
4. From now on, these editors are allowed to translate.
5. You decide whether to use automatic or your own translation page by page.
6. You also have the option of making sentence-by-sentence changes to the automatic translation.
7. After each change to the German page, WPML indicates via the round arrow that you must update the English version. You do this by clicking on the round arrow.

• WPML Editor translates every single element. You MUST ALWAYS make any changes in THIS EDITOR.
• WordPress Editor. In the block editor, you can freely design the English page, also structured with other blocks. Your changes here will be lost as soon as you return to the WPML editor.
• You can change this decision page by page later: start with the WPML editor and if it turns out that the translation should be very different, switch to the WordPress editor.

The JGU Translation Service is responsible for translating the central web pages and advises you in an advisory capacity on translation issues and machine translation. The JGU Glossary (German-English) with university-specific terminology is also maintained there.

• The page you requested is not accessible from your browser. Please use a workspace PC in your office at Johannes Gutenberg University Mainz or use the remote desktop connection: This error message appears if you are working from outside JGU and VPN is not switched on. The message also appears if you have saved a page as a draft. Dann wird versucht, daß Sie sich anmelden und DAS wiederum geht nur mit VPN, RDV, oder direkt an der JGU.
• Page not found 404: the page is still marked as private. You can only access it if you are an editor and logged in.
• Write permissions: in the dashboard > JGU Tools > Users, the persons with access to the authorization resource are displayed. These persons manage the write permissions via Account.uni-mainz.de > Permissions > Resource web page. Administrators means the rights managers, “Edit content” means the people in the editorial department. It is sufficient to enter users in the correct group at account.uni-mainz.de. Clicking on the ‘Update user list’ button is no longer necessary in the new WordPress.
• Hyphenation: This is not solved across all browsers.
• Colors are missing: The background colors of the blocks are limited to the colors specified in JGU’s corporate design.
• Use your own icons: This is technically feasible in principle, but not yet possible at present.
• Intranet function: Find in Teams, LMS, Sharepoint, depending on the use case.
• Download Center: Where to put the downloads?
• Old multisite will be shut down: no date has been set yet
• Re-launch /ˈriːlɔːnt͜ʃ,/ is what your website got with the move 😉

• Courses – everything to do with operation: We provide instructions and training, are there for you in question hours and forums, and help in the event of errors.
• Newsletter subscription: Mailing list (open newsletter) for information on the block-based layout. Start the subscription by sending an e-mail with the subject subscribe jgu-cms to sympa@lists.uni-mainz.de.
• WordPress forum: Ask your questions about the operation of WordPress, watch the problem solving in the WordPress forum, which takes place via BBB: https://bbb.rlp.net/rooms/slo-mk5-tdt-xe0
• WordPress Instructions Layout 2012 with shortcodes and three-column standard layout.
• Coordination web pages: Ask organizational and content-related questions in the web page coordination group (accessible with a JGU account). It meets every two weeks on Mondays from 12-13 o’clock. If you are interested, please contactbei:cio@uni-mainz.de.

We meet on the first Monday from 11am to 12pm and on the third Thursday from 10am to 11am for an hour about WordPress.

• 19.2. Thursday 10 a.m.
• 2.3. Monday 11 a.m.
• 19.3. Thursday 10 a.m.
• 6.4. Monday 11 a.m.
• 16.4. Thursday 10 a.m.
• 4.5. Monday 11 a.m.
• 21.5. Thursday 10 a.m.
• 1.6. Monday 11 a.m.
• 18.6. Thursday 10 a.m.
• 6.7. Monday 11 a.m.
• 16.7. Thursday 10 a.m.
• 3.8. Monday 11 a.m.
• 20.8. Thursday 10 a.m.
• 7.9. Monday 11 a.m.
• 17.9. Thursday 10 a.m.
• 5.10. Monday 11 a.m.
• 15.10.Thursday 10 a.m.
• 2.11. Monday 11 a.m.
• 19.11. Thursday 10 a.m.
• 7.12. Monday 11 a.m.
• 17.12. Thursday 10 a.m.

You will certainly notice that there are always incomplete or incorrect things. With the amount of blocks and functions, the nesting possibilities and the resulting interactions, a team of web programmers is needed to fix all errors and fulfill all wishes.

We have recorded several hundred errors and are working through them one by one, always keeping an eye on performance, accessibility and data security.

Current issues that we would like to resolve as quickly as possible:

• Optimizing posts for social items: open-graph (og) featured pic
• Burgermenu mobile view: The learn more will be removed.
• Category and keyword pages that can be selected in the menu do not yet work and are not displayed in the menu. There is a similar function through the blocks: Post Listing (=Post Listing), Closed Stacks, Post Archive
• Images: are always enlarged to fit the available space. Small images should therefore only be used in the context of sliders, post images and in columns, otherwise you will see the pixels. Text no longer flows around in the new layout. Use items and images or the image gallery.
• “Correct” font sizes: don’t bother with this. If a visitor to your site cannot read the font, they will know how to enlarge the font on their device.
• Font colors: don’t bother with this. The default font color is black on white. This is specified by the JGU layout and should not be changed.
• Text alignment: should be and remain left-aligned. Centered looks strange, and justified text is illegible and cannot be compared with the justified text on a printed page.
• Image scaling: good topic, we are currently introducing a new 16:9. Anything over 1200 pixels wide is usually unnecessary.
• Layout in general: do not confuse a website with the design options of e.g. Word, PowerPoint or image editing software. WordPress is there to publish content. Don’t worry about the layout. This is predefined and should not be artificially and laboriously changed by hand. This will make life difficult for the editors who follow you. WordPress has many more optional design options, keyword Full Site Editing. But not within the scope of the JGU layout.