[Epic][AP] CMS preview

[timcosgrove]

Requirements & Goals

As a CMS editor, I need to see how my content will be rendered on the front-end of VA.gov, so I can check that it is correct.

How will we know we've achieved our goals?

Preview Give feedback

1. The CMS can render a single front-end build of content using Next Build
2. Next Build preview is able to render previews with draft or otherwise unpublished content.
3. Content Build preview continues to work without issue
4. CMS uses Content Build preview or Next Build preview as appropriate.
5. The UX for CMS preview is unaltered, even when using Next Build - we continue to use the button
6. Preview works for Tugboat environments
7. Preview works for BRD environments
8. Preview works for local environments

Work and Supporting Info

Tickets

Preview Give feedback

1. Next Build Prod CMS preview server logging #16474
   1 of 5
   Accelerated Publishing Blocked +2
   
2. [SPIKE] Explore Argo CD Blue/Green and/or zero-downtime Deployment for Next.js servers on EKS #16866
   4 of 4
   Accelerated Publishing review-necessity +2
   

   
3. Prod and Test Prod Next.js preview servers should use https #17778
   0 of 2
   Accelerated Publishing Needs refining +2
   
4. Plan, document, and implement AP content-type rollout strategy #18544
   6 of 6
   Accelerated Publishing Needs refining +2
   

Completed work

Preview Give feedback

1. Next.js 'site' configuration for BRD #15793
   0 of 2
   Accelerated Publishing Needs refining +2
   
2. Create Next-Build remaining EKS Environments #16949
   6 of 6
   Accelerated Publishing Blocked +2
   
3. Create Next-Build Workflow to Update Helm Chart Container Image Version #16863
   3 of 3
   Accelerated Publishing Blocked +2
   
4. Create Next-Build Container Image Workflow #16857
   5 of 5
   Accelerated Publishing rollover +2
   
5. Next-build preview server running for one BRD environment #9886
   6 of 12
   Accelerated Publishing DevOps Next Build +3
   
6. Write Next Build Preview Oauth keys to BRD filesystems #15796
   3 of 4
   Accelerated Publishing +1
   

   
7. Env variables for authentication to BRD CMS instances are available on EKS Next Servers #15801
   4 of 5
   Accelerated Publishing Blocked +2
   
8. Tugboat next-build preview server branch can be chosen via CMS interface #9887
   Accelerated Publishing Needs refining Next Build +3
9. Create Next-Build Dev and Staging EKS Environments #16861
   5 of 5
   Accelerated Publishing Needs refining +2
10. CMS Editors should not see error messages due to CMS Preview secrets expiring #16289
    0 of 3
    Accelerated Publishing Needs refining +2
    
11. CMS Preview EKS servers should update after Next Build production tag/deploy #16283
    1 of 4
    Accelerated Publishing Blocked +2
    
12. Next Build Tugboat preview servers need files from vets-website build #16288
    0 of 2
    Accelerated Publishing +1
    
13. CMS Preview should clearly indicate when a draft or archive is being previewed #16287
    0 of 3
    Accelerated Publishing +1
    
14. Spike: determine infrastructure implementation for Staging and Prod and test Next.js Servers #16187
    3 of 4
    Accelerated Publishing rollover +2
15. drupalClient configured for Drupal authentication on Tugboat #15800
    0 of 4
    Accelerated Publishing Needs refining +2
16. Write Next Build Preview Oauth keys to Tugboat filesystem #15795
    1 of 3
    Accelerated Publishing +1
17. Next-build server running per Tugboat environment #10068
    Accelerated Publishing DevOps Needs refining Next Build +4
18. Next-drupal content type entities #9891
    Accelerated Publishing Next Build +2
    
19. SitePreviewer plugin for Next.build preview #9885
    Accelerated Publishing Next Build +2
    
20. Specify Oauth private/public key location in Oauth settings #15798
    0 of 2
    Accelerated Publishing +1
    
21. Set up basic Next.js site entity #15791
    0 of 2
    Accelerated Publishing +1
    
22. Next.js 'site' configuration for Tugboat #15792
    0 of 4
    Accelerated Publishing +1
    
23. Spike: Stand up running Next.js server per Tugboat instance #15240
    0 of 3
    Accelerated Publishing repeat-rollover rollover +3
    
24. Spike: CMS Preview with Next.js #14419
    Accelerated Publishing +1
    
25. Generate Next Build Preview consumer #15799
    0 of 3
    Accelerated Publishing +1
    
26. Create Oauth public/private keys and store in AWS SSM #15794
    2 of 3
    Accelerated Publishing +1
    
27. Set up user and role for Next/Drupal CMS Preview #15245
    2 of 3
    Accelerated Publishing rollover +2
    
28. Next-drupal configuration per environment #9889
    Accelerated Publishing Blocked DevOps Next Build +4

Assumptions

• We are only building preview for VA.gov front-end. Preview does not take COPE into account (i.e. if the content were used in a chatbot agent, this preview makes no attempt to cover that case).
• We are making no changes to the UX of CMS Preview.