search

strapi / nextjs-corporate-starter

Strapi Demo application for Corporate Websites using Next.js
MIT License
1.1k stars 353 forks source link

Will this project be ported to Strapi 5 any time soon? #147

Closed webhype closed 1 month ago

webhype commented 1 month ago

Love the overhaul of the old nextjs-corporate-starter, breath of fresh air! Now with Strapi 5 out, is there an ETA for this starter template to be ported over? Also NextJS 15? (one can ask lol)

PaulBratslavsky commented 1 month ago

@webhype I have migrated the project in this branch and outlined the steps in this blog post.

Since Strapi 5 is out, we have build an official demo and starter project called LaunchPad, that will be replacing this starter.

You can learn more about the LaunchPad app here

Project repo: https://github.com/strapi/LaunchPad

webhype commented 1 month ago

Thanks for the great work! I got it to work under Strapi 5. I find the LaunchPad app a bit overdesigned and weak on hard features that developers actually want; there's not even a working form submit. Unless you want the site to look exactly as "overdesigned" as the template, it's hard to undo all these changes for a simpler layout. Most devs want just a simple blog, a sales page, and a private members area for their SaaS service.

An example about logging into a private area with various security providers would be great leap forward for any template (Google OAuth or simply email).

Anywho, there's something wrong with the i8n which was the case under Strapi 4 also, but there it failed "quietly" (showing WSOD only), whereas under Strapi 5 it throws hard errors.

NextJS build seems to want to build languages "de" and "cs" as well, and that fails also when calling up i8n urls like so: http://localhost:3000/de/about

  28 |   const response = await fetch(url, authToken ? headerWithAuth : baseHeader);
  29 |   const data = await response.json();
> 30 |   if (!response.ok) throw new Error("Failed to fetch data");
     |                          ^
  31 |   return data;
  32 | } catch (error) {
  33 |   console.error("Error fetching data:", error);

I guess I could just take out "de" and "cs" in the NextJS configuration but I would rather the site work in other languages, which goes back to issue #145

Edit: Actually this problem with adding locales in the backend disappeared in the v5 port so was probably solved between v4 and v5... closing this for now, will try and get localization to work by myself first, cheers!

Thanks for the labor of love, I think for now this is the superior starter template...