Accelerating International Education via Drupal: A Georgia Tech Case Study
summary
Georgia Tech’s international office moves heavy form traffic off the main site by splitting into a read-only HTTPS front end and a separate user-content server, solves Web Application Firewall false positives by deploying SSL to stop blocked submissions, speeds global access with a CDN pull setup, and serves critical arrival pages with Google AMP. Remote-post webforms feed a ticketing system, card-swipe kiosks capture arrivals, and the site supports ~1,500 incoming students each fall while trimming modules and aggressive caching.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:19Who am I
- 0:51What is the Office of International Education
- 2:06History and Hosting
- 2:38IT Support
- 3:46Shared Hosting
- 4:58Site Failure
- 5:59Test and Question Everything
- 8:37Split Site in Two
- 9:48Web Application Firewall
- 11:37SSL
- 12:04Installing SSL
- 13:01Configuring SSL
- 14:19Signatures
- 16:06CDN
- 16:49Reliability
- 17:06Cost
- 17:53Push vs Pull
- 18:29Drupal CDN Module
- 19:58CDN Test
- 20:31Why not use a CDN
- 22:11Part 3 Google Lamp
- 22:23What is Google Lamp
- 24:21Module Theme
- 24:54Search Results
- 25:34Customization
- 26:09Signin Sheet
- 26:34Signin Pitfalls
- 26:59The Solution
- 28:06Remote Submission
- 29:35Customer Service
- 30:36What Drupal does
- 31:22QA
related talks
53mSuccess at scale: Preparing Drupal 8 for large events
56mLarge scale websites performance optimisation tricks
42mCase Study: Using Drupal as a Back-End for Japan's Digital Government
53mA Survey of Emerging Technologies That Complement Drupal
23mBeyond Chatbots: Creating Smarter, Personalized Experiences
56mHow to keep Drupal relevant in the Git-based and API-driven CMS era
28mThe Path to Scaling a Digital Enterprise
01h 01mThink Locally, Build Globally - How Drupal is powering headless omni-channel web platforms