If you need a website for a Georgetown department or office, an academic degree program, or a university initiative or project, you may be eligible for a WordPress at Georgetown site. If you need a website for something else, like a blog or a faculty bio, check out these website options instead.
Requests
Requests for sites in the new theme fall under two categories: existing sites wanting to migrate to 1789, and new sites wanting to start in 1789.
- For a new site, you’ll need to fill out the domain name request form to get your domain approved before work can begin.
- For existing sites migrating from Whitehaven Nu to 1789, review our Whitehaven Nu to 1789 page before requesting the theme to get a sense of what’s different, common mistakes in 1789, and tips for working in the new theme.
You can request the theme by emailing webservices@georgetown.edu. In your request, make sure to include:
- The name of the site. If the site already exists, include a link!
- The affiliation (ex: GUMC, MSB).
- Desired launch date
- Type of sandbox site. For requests to migrate an existing site in 1789, you’ll have the option to start from a blank site or a clone of the current site. A blank site is a good option if you plan on making major content and site architecture changes. A clone site is a good option if you plan on reusing the majority of the existing content.
- Approval from school contact. Each school has a different way of handling 1789 site requests. If you’re unsure how your school handles 1789 requests, reach out to your school’s contact or the Web Services team.
If the request is approved, Web Services will create a sandbox site for you to work on your new site! The site creation process can take up to two business days after the request is approved.
Migration Guide
Take a look at the 1789 Migration Guide to learn about the process of building a website in the new 1789 theme and the website launch process (please give Web Services a minimum of one week’s notice for the site launch).
Example 1789 Migration Plan
Check out our recommended step-by-step process! You can create a copy of our Example 1789 Migration Plan and use it as a template.
Examples of Sites in 1789
Not sure if 1789 is the right theme for you? Check out some sites currently in the 1789 theme below!
- Biomedical Graduate Education
- McCourt School of Public Policy
- The Office of Public Affairs (1789 Unit)
- The Massive Data Institute (1789 Unit)
- Common Home (1789 Unit)
- Georgetown Humanities Initiative (1789 Unit)
Sandbox Site Management Policy
This policy will apply to all sandbox sites requested for new or migrated sites, and for old sites once a new version is launched. It aims to streamline our processes and optimize our server resources.
One-Year Maintenance Period:
Once a sandbox site is requested and set up by the Web Services team, it will be maintained for a period of one year. This timeframe is provided to allow site managers and editors ample opportunity to develop and finalize the site before its official launch or relaunch in the case of a site migration.
When a migrated site is launched, the old site will be renamed and blocked from search engines but will be available for those with the new link for one year. This will allow site managers to have access to the original content in case anything was missed in the migration.
Archiving After One Year:
After one year, the Web services team will archive all old sites and any sandbox site that has not been launched within the one-year maintenance period. The archiving process involves preserving the site’s data in a secure state, but that data is no longer accessible.
One-Year Archival Period and Site Deletion:
The archived site will be retained for an additional one year. During this time, site managers and editors can request access to retrieve content or continue development if needed. However, if no action is taken within this period, the archived site will be permanently deleted from our servers after the additional year has passed. Once the site is deleted after 2 years it cannot be restored.
By setting a defined maintenance and archiving schedule, we can better manage our server resources. This ensures that our systems are not overburdened with inactive or abandoned sites, leading to improved performance and reliability for all live sites across the University.
Archiving sites that are not launched within the one-year period also helps maintain data security and integrity. It ensures that unused or outdated content does not remain indefinitely on our servers, reducing the risk of potential security vulnerabilities.
For Site Managers and Editors:
We encourage all site managers and editors to review their current sandbox sites and plan accordingly. If your site is nearing the one-year mark and is not yet ready for launch, please contact the Web Services team to discuss your options. For archived sites, remember that you have one year from the date of archiving to retrieve any necessary data or request continued development.