Project and Drupal CMS Q&A

The reusable component library is currently available to site admins and is being used on widely used content types like program pages. It’s not yet available to Groups, but we’ve added it to our list for post-launch review.

You can, however, duplicate a component you've built on a page, but the duplicate will exist only on that same page.

We planned to add department templates to groups by using the clone tool, but during testing we found that media files were shared across clones. If one person deleted a shared image, it disappeared from everyone’s template. To avoid that risk, we chose not to group templates and turned off the clone tool for now. The clone tool can cause issues and be risky even inside its own group. We’ll revisit cloning later when we can explore a safer setup.You can still view the design reference and other visual resources here.

SVGs are now allowed on the site. They may look like regular images, but they’re actually code-based and can contain scripts — making them a security risk. Unlike JPGs or PNGs, they behave more like mini webpages than images. To keep our site safe, we don’t allow general SVG uploads.

We will not be using autosave on the site. Autosave can save changes you didn’t mean to keep, create version clutter, and cause conflicts when multiple people edit the same content. Manual saving gives you more control and helps prevent mistakes.

Legacy components were created to accommodate older content and functionality carried over from the previous version of our site. These components exist to ensure continuity and minimize disruption during the transition.

However, they are not intended as long-term solutions. Over time, you should replace them with our updated components that better align with the new system’s design, accessibility and performance standards.

The addition of a file editor to the wysiwyg editor is a fairly large task and is on our list, but we might not get to it for a bit. That said, there is a work around.

You can currently link to files in the WYSIWYG but they need to upload them to the media library first. Here is a quick Loom video to walk you through it.

When you upload a file in Drupal with the same name as an existing one (e.g., filename.pdf), Drupal automatically renames the new file to prevent accidental overwrites — resulting in filenames like filename_0.pdf, filename_1.pdf, and so on. This behavior ensures that files with the same name don’t unintentionally replace each other, which is especially important in environments with multiple editors.

Best Current Solution:
To effectively "replace" a file, upload the new version using a slightly different name, then update any links to point to the new file. There is a contributed module that supports true file replacement, but changing the file name and updating the link is the simplest method without added tools. We can add this to our list to revisit post-launch.

Important Note About PDFs:
Whenever possible, avoid uploading PDFs for web content. Instead, convert the content into an HTML webpage. This improves accessibility, works better on mobile devices and ensures users always see the most up-to-date information — especially important if someone bookmarks the page.

Yes! In the main menu or group menus, add a top level/parent item that has a url of <nolink>.

We have discovered there is known issue with a module in the site as pertains to editing existing links in Groups and Menus. To solve this issue:

• Create a new link
• Delete the old link.
• Move any child pages under the new link.

We are looking into the patch that is available and will apply the patch the week of May 12.

When linking to another page within the website, always use the autofill link selector instead of manually pasting the URL. This ensures your link remains accurate even if the destination page’s URL changes. Using the autofill tool helps keep your content reliable and up to date by automatically updating links, reducing the need for manual maintenance, preventing broken links and maintaining consistent formatting across pages.

Files migrated from Typo3 are found at /sites/default/files/fileadmin/<filemonthfolder>/<filename>

Files migrated from Drupal are found at /sites/default/files/<filename>