1. You fill out the form 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 (see https://cms.zdv.uni-mainz.de/kopie rvorlage-ag/2024/03/19/checkliste/ ).
4. Your new website is public. As the new subsite address is unknown to search engines, this is not a problem.
5. 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. Setting links, assigning parent pages, adding to the menu only works for public pages. Yes, draft also works. Password-protected does not really work.
6. URLS of your website that should also be found in search engines after the move should be named in exactly the same way as in the old website. The effect is then almost like a redirect to the old website!
   If the page content in the new website is contained in another page, you can simply link to this other page from a newly created page with the same URL, e.g. just insert this text there: “You can now find this content here: (enter the URL here)”.
   This makes it easier for users and search engines to find the content on the new website. Pages that only contain such a link can be deleted after a few weeks/months.
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. Possibly: Back up the contents of the old website, e.g. via httrack
9. You are finished with the move and notify us that the address can now be moved.
10. Your pages must no longer be private. Otherwise you will receive a “Page not found 404 error” after the address change.
11. We are moving the web address of the old website to the new one.
12. The moved old website is protected from access. Only pages are protected. The items are not protected! All your old files can still be found in the search engines.
13. If this bothers you, we can archive the website, in which case the entire website will no longer be accessible to anyone.
14. The final step is the complete removal of the old website after three months. We will do this for you.
15. These websites already use the new layout (as of February 2025)

Why is there no automatic move? The automatic move is undesirable for the following reasons:

• The structure of the web pages is completely different, you cannot use the block elements when moving automatically.
• Legacy content from the move before last would also be transferred. Outdated content is not good.
• The JGU management would like a target group-based presentation and approach.
• Everything internal should be stored on an intranet.
• Images must be supplied in the correct size. Automatic image transfer is therefore not practical.

You want to reuse the URL of your web pages. If the back part of the URL is identical in the old and new websites, you will achieve a user- and search engine-friendly move.

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/fb-xx-ihrinstitut/
• New website:
  • Subsite address: cms.zdv.uni-mainz.de/fb-xx-ihrinstitut
  • Login: cms.zdv.uni-mainz.de/fb-xx-ihrinstitut/wp-admin

After the move:

• New website:
  • Primary domain: ihrinstitut.uni-mainz.de
  • Subsite this address remains invisible: cms.zdv.uni-mainz.de/fb-xx-ihrinstitut
• Old website:
  • Subsite address: www.blogs.uni-mainz.de/fb-xx-ihrinstitut, this address will remain with all data for 3 months after the move.
  • Login: www.blogs.uni-mainz.de/fb-xx-ihrinstitut/wp-admin
• Blocks such as accordion, anchor navigation and tabs create jump labels. If you create these, name them appropriately so that your URLs remain meaningful!
• Example: living expenses & rent result in:
  https://ihrinstitut.uni-mainz.de/uebergeordnete-seite/seitentitel#lebenshaltungskosten-amp-miete
  Better: https://einrichtung.uni-mainz.de/seitentitel#kosten
  • /uebergeordnete-seite/: necessary for the order of the items and the breadcrumb menu: you defined this Wep page as a child page of another page. This is optional. May be you should do it like from your old web site!
  • seitentitel: title of the page itself. You should adopt the title of your old website.

Each page consists of blocks. The block list contains a short description for each block as well as a link to the video instructions and demo web page.

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

The demo website offers a short description of each of the blocks as well as examples of all variants.

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 only set up multilingualism at your request. WordPress Multilingual = WPML automatically translates your texts with DEEPL in the WPML Automatic Translation Editor. In contrast to the old blogs multisite, both languages are administered in one website.

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. Editors can now translate.
5. You decide whether to use automatic or your own translation page by page.

• WPML Editor automatically translates every single element one-to-one via DEEPL. You MUST ALWAYS make any changes in THIS EDITOR. You must NEVER switch to the WordPress editor.
• WordPress Editor. In the block editor, you can freely design the English page, also structured with other blocks.

Links and images on the website that has not been moved are broken after the first language has been moved, as the primary web address is used, which has already been moved. Images that are needed for the old web pages of the other language variant are missing on the new website. It therefore makes sense to move both spokespersons at the same time.

The JGU Translation Service is responsible for translating the central web pages and advises you in an advisory capacity on translation issues. On the web pages of the Translation Service you will find extensive information on machine translation and information and tips on translating websites as well as the JGU Glossary (German-English) with university-specific terminology.

• 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. Then an attempt is made for you to log in and THAT in turn only works with VPN, RDV, or directly at 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.
• 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.
• 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
• 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 contact Davina Hachgenei at: d.hachgenei@uni-mainz.de.

We meet on the first Monday at 11 a.m. and on the third Thursday at 10 a.m. for an hour about WordPress.

• Thursday, 17.4.24 10-11 a.m.
• Monday, 12.5.24 11am-12pm
• Thursday, 22.5. 10-11 a.m.
• Monday, 2.6. 11-12 h
• Thursday, 12.6. 10-11 a.m.
• Monday, 7.7. 11-12 a.m.
• Thursday, 24.7. 10-11 a.m.
• Monday, 4.8. 11-12 h
• Thursday, 21.8. 10-11 a.m.
• Monday,1.9. 11-12 o’clock
• Thursday, 18.9. 10-11 a.m.
• Monday, 6.10. 11-12 h
• Thursday, 23.10. 10-11 a.m.
• Monday, 3.11. 11-12 o’clock
• Thursday, 20.11. 10-11 a.m.
• Monday, 1.12. 11-12 h
• Thursday, 18.12. 10-11 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:

• 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.