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

Plans for moving forward #40

Open
nring opened this issue Apr 22, 2022 · 0 comments
Open

Plans for moving forward #40

nring opened this issue Apr 22, 2022 · 0 comments

Comments

@nring
Copy link
Contributor

nring commented Apr 22, 2022

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
@cmdea cmdea pinned this issue May 6, 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

No branches or pull requests

1 participant