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

Should we replace our Next.js for Storefront? #2625

Open
1 task
mimarz opened this issue Oct 16, 2024 · 2 comments
Open
1 task

Should we replace our Next.js for Storefront? #2625

mimarz opened this issue Oct 16, 2024 · 2 comments
Labels
🖥️ storefront designsystemet.no

Comments

@mimarz
Copy link
Collaborator

mimarz commented Oct 16, 2024

This is not a priority until after v1.

Replace with Remix, Astro?

Create a new folder (apps/www?) for our remix version of the storefront.

  • Should we use Sanity instead of plain mdx?

Tasks

Preview Give feedback
@mimarz mimarz converted this from a draft issue Oct 16, 2024
@mimarz mimarz added the 🖥️ storefront designsystemet.no label Oct 16, 2024
@mimarz mimarz changed the title Should we replace Next.js with Remix? Should we replace our Next.js with Remix? Oct 16, 2024
@Barsnes
Copy link
Member

Barsnes commented Oct 17, 2024

I think it would be nice to change to using a CMS, wether we change framework or not.
Sanity supports both Next.js and Remix, and it would be nice to test this out when testing Remix.
image

This is suggested in #1704

@mimarz mimarz changed the title Should we replace our Next.js with Remix? Should we replace our Next.js for Storefront? Nov 15, 2024
@sudazzle
Copy link

sudazzle commented Nov 15, 2024

What are the motivations to replace Next.js?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖥️ storefront designsystemet.no
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants