Online Degrees & Certificates : LPNext Build plan page | Template = docs | Brand = docs | Academic Area =

We will set up an efficient modular system for production of new landing pages (LP) that allows authors and admins to quickly create campaigns, edit content locally or globally and quickly run A/B testing. The content for each page will be simplified HTML5 with sensible fall-backs for older browsers so pages are optimized for speed and semantic accessibility. Authors will easily be able to restructure page elements and apply templates to change the look and feel of the page design.

Requirements

  1. Templates are easy to apply and can be updated globally or individually.
  2. All common content is embedded into pages using modular content (includes).
  3. Page content is easily editable in any text editor.
  4. Authors can update <head> (meta tags, stylesheets, scripts) at global/template level and individual pages.
  5. cPanel and FTP provides File Explorer (directories, assets).
  6. cPanel and .htaccess provides redirect management (301, 302, page refresh).
  7. Authors can use preferred text editor or IDE for global search & replace.
  8. cPanel and 3rd party services provide automatic backups (in case of data loss or corruption).
  9. Site employs Pretty URLs that don't end in “.php.”
  10. Hide directory listings.

Strategy

The new pages will be build using HTML5 and Apache/PHP with little or no CMS implementation at the start. If CMS capabilities are desired, we will add features using a streamlined product such as Perch or Expression Engine.

The server we use will be standard Apache with cPanel. We will configure it to use pretty URLs and set up subdomains for AMU and APU so that mapping existing URLS to the new ones will be as simple as possible and included content can be leveraged to reduce duplication.

Domain & Subdomain configuration

(The actual domain “lpnext.com” is irrelevant – it could be anything.)

Directory structure

Our new landing pages have very specific filenames that act as degree level (aka programLevel) indicators which will be easy to isolate in analytics. The URL pathname consists of: programName/programLevel. The index page redirects to a generic page called Overview. The folder structure of the host will be like this:

We would try to use relative linking where possible so common assets will link to the appropriate resource.

DNS mapping

Our DNS (administered by IT) will be configured so that incoming requests to files and folders in certain domains will map to counterpart files and folders on our host. The effect will be transparent to the user who will not notice any change to URLs. Because the pages themselves are actually on the same host, we are able to leverage content and resources across subdomains. Our servers also have an additional subdomain of "www." that maps to the main branded subdomains.

Incoming URL maps to Our Host
amu.lpnext.com } amu.lpnext.com
start.amu.apus.edu*
www.apu.apus.edu/lp/
www.amu.apus.edu/lp2/
 
apu.lpnext.com } apu.lpnext.com
start.apu.apus.edu*
www.apu.apus.edu/lp/
www.apu.apus.edu/lp2/
Incoming URL maps to Our Host
amu.apuseducation.com } amu.apuseducation.com
amuonline.com*
 
apu.apuseducation.com } apu.apuseducation.com
studyatapu.com*

*Because we don't want users to ever leave the apus.edu domain, we had to set up hard-coded redirects in each index page to bounce them to the Overview page. We call this the "fail-over" domain. This requires us to set up a separate server for handling landing pages on amuonline.com and studyatapu.com. Those domain's must fail-over to a .com domain rather than apus.edu. They share the same content on a nearly identical server with the domain apuseducation.com. there are slight differences with the brand index pages and the server specific variables page but the rest of the content is synchronized with the main lpnext.com server and whenever content is added, deleted or edited, apuseducation.com is updated too.

Technical considerations

Other concerns

Since content in the LP system will be hosted separately from other public web content, some duplication of effort is necessary. Changed, added or deleted program names must be administered in our system separately from the rest of the public web authoring interfaces. The same would apply to updated messaging about disclosure, copyright, contact information or branding, logos and imagery. We believe that our system will facilitate better leveraging of shared content and faster updates when necessary. And since the LP have historically been a separate entity from the rest of the public web, we do not foresee a problem with this.