To seed a new portal project, we have historically copied the configuration of an existing portal (one that most closely matches the new portal).
You’ll need to update the style resource. This includes the favicon, socialmedia image, logo, and palette. Palettes are defined in the SRC project, and are pulled into other applications (like OneSage).
The next step is to establish the infrastructure for the portal. For this we rely on IT support to set up the stack (which includes creating the new staging and production buckets, setting up the subdomains via Route53, and creating the CloudFront distributions).
After the subdomains are available, you’ll need to add these to various authorization lists.
SWC CORS Filter to detect existing sessions cross-domain
The next step is to work with the Design Team and Data Curators to define the objects (and object relationships) being surfaced in the portal. The Home Page and Detail Page(s) tend to require the most work because they are typically customized and/or complicated.
Add Comment