Version Agnostic

File Management Basics

At some point, you or your content manager will have a need to share files via your unit's Drupal website, but what is the right way to do this?

This section houses guides, tips, and tricks for working with multimedia (video, audio, etc.) in Drupal, whether through the Drupal 8/9 Media library system, or through other means.

Eventually, the time comes to say goodbye to a Drupal site, but doing so is not always as easy as it may seem.  Below are tips and tricks for shutting down a site gracefully without losing your sanity along the way.

Here are some example .lando.yml files (and associated settings.php files for drupal) of commonly-used configurations.

1. First install WSL version 2.

Submodules allow you to keep a Git repository as a subdirectory of another Git repository. This lets you clone another repository into your project and keep your commits separate.

To define the submodules for the various GT Theme components, add the following sections to the .gitmodules file for each repository:

Whether you are an experienced Drupal developer / site administrator who has come to Georgia Tech, or an existing staff member asked to venture into the world of Drupal, you may be wondering how you should get started with using Drupal for a Georgia Tech website.

The Lando Drupal 7 recipe does not come with mail functionality out-of-the-box. However, DrupalEasy has written straight-forward documentation on how to enable server mail functionality.

This is helpful for enabling mail notifications for password resets, trigger/Rules configuration.

This section contains tips on how to install Drupal from scratch, how to apply routine point release updates, and how to migrate between major version of Drupal.  There is also a guide to moving sites from development (either on your local computer, or on a development server) to a production environment (e.g. OIT Web Hosting).  For more generic but also more official guidance, the official Drupal website has a Guide to Migrating a Drupal Site.

Notes on the setup of the drupal.gatech.edu site.

• The user roles "leadership", "advisory" and "editor" are not permission granting roles, but just categorization roles as follows:
  • leadership = User who is on the Georgia Tech Drupal User's Group leadership board
  • advisory = User who is on the Georgia Tech Drupal User's Group advisory board

  • editor = User who, at the time of the Drupal 7 to Drupal 8 site conversion, had edited at least one page on the site