Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jamstack + Hybrid Content Architecture (Phase 2) #13

Open
1 of 17 tasks
thescientist13 opened this issue Jul 30, 2021 · 0 comments · May be fixed by #72
Open
1 of 17 tasks

Jamstack + Hybrid Content Architecture (Phase 2) #13

thescientist13 opened this issue Jul 30, 2021 · 0 comments · May be fixed by #72
Assignees

Comments

@thescientist13
Copy link
Contributor

thescientist13 commented Jul 30, 2021

Type of Change

  • New Feature Request
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

Coming out of #9 , tracking all the work specifically needed to go (more) static, introducing a CMS and going full Jamstack with more static content where appropriate, and a CMS for the rest. This discussion has a good ongoing thread about the over plan - #37.

Details

  1. Explore SSR export vs SSG prerender w/ Lit ( ⚠️ may require additional upstream features from Greenwood)
  2. Convert Home Page to HTML
  3. Convert top level Artists page to HTML and content to markdown,
  4. Convert top level Albums page to HTML and content to markdown,
    • how to link artists with albums - just hardcoded links, or prerendered graphql?
  5. Put events into a CMS
  6. Convert Events Page to HTML
  7. Convert Contact Page to HTML
  8. Fix styles, including getting custom resource processing for <link> tags (needs upstream)
  • e.g. <link rel="stylesheet" href="../styles/home.css?type=css"></link>
  1. Put posts into ... ??? (HTML?)
  2. Drop DB in AWS?
  3. Static export and / or prerender w/Lit renderer?
  4. Cloudinary for images (maybe a better fit for TT.tv?)
  5. Better CloudFront caching for API responses (instead of manual invalidations)
@thescientist13 thescientist13 added the feature New feature or request label Jul 30, 2021
@thescientist13 thescientist13 added this to the Jamstack Migration milestone Jul 30, 2021
@thescientist13 thescientist13 self-assigned this Jul 30, 2021
This was referenced Jul 30, 2021
@thescientist13 thescientist13 removed their assignment Jul 30, 2021
@thescientist13 thescientist13 self-assigned this Oct 28, 2021
@thescientist13 thescientist13 changed the title Phase 3 - Jamstack cutover Phase 3 - Hybrid Content Architecture Nov 27, 2021
@thescientist13 thescientist13 changed the title Phase 3 - Hybrid Content Architecture Phase 3 - Jamstack + Hybrid Content Architecture Nov 27, 2021
@thescientist13 thescientist13 changed the title Phase 3 - Jamstack + Hybrid Content Architecture Phase 2 - Jamstack + Hybrid Content Architecture Dec 3, 2021
@thescientist13 thescientist13 changed the title Phase 2 - Jamstack + Hybrid Content Architecture Jamstack + Hybrid Content Architecture Dec 3, 2021
@thescientist13 thescientist13 removed the feature New feature or request label Dec 3, 2021
@thescientist13 thescientist13 changed the title Jamstack + Hybrid Content Architecture Jamstack + Hybrid Content Architecture (Phase 2) Feb 5, 2022
@thescientist13 thescientist13 pinned this issue Feb 5, 2022
@thescientist13 thescientist13 linked a pull request Feb 19, 2022 that will close this issue
17 tasks
@thescientist13 thescientist13 moved this to In Progress in General Activities Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant