search

deptagency / dept-engineering-blog-ui

dept-engineering-blog-ui.vercel.app
MIT License
1 stars 3 forks source link

Plans for moving forward #40

Open nring opened 2 years ago

nring commented 2 years ago

We'd love to get this code in a state where it can be shared amongst other DEPT® blogs. So what do we need to do to get it there?

  1. Remove all unneeded feature code inherited from the parent next-cms-ghost template. It's a fantastic starting point, but the template project has a boatload of features that we won't need.
    • Identify specific features to keep and which ones to remove
    • Do we want comments? If so, what system do we go with? The template supports Disqus and Commento out of the box
    • See issues 41-44
  2. Revamp styling
    • Switch to a more maintainable styling system
    • Maintain high Lighthouse scores
    • Standardize breakpoints and behavior
    • Verify content displays correctly (CodeSandbox.io iframes, prisma highlighting, videos, etc)
    • Homegrown Grid system (currently using MUI just for Grid)
  3. Create shareable components
    • Layout components (full-bleed wrappers, wrappers, PostCard, Posts, Buttons, Tags)
      • Probably not worth it to get more fine-grained just yet