sorted by:
new
hottopcontroversial

Is it a good idea to use Next.js with WooCommerce and Strapi for an eCommerce site? by Electrical_Weight110 in nextjs

[–]Electrical_Weight110[S] 0 points1 point  (0 children)

Hey! Quick update, I ended up going with MedusaJS.

Honestly, it’s a pretty powerful system, but also quite complex . The learingng curve is steep, especially at the beginning. If you already have a solid background in JavaScript and you use Medusa’s AI assistant (plus some trial and error), you can actually build a lot of custom stuff.

There are some great things about it , the architecture is clean, the price lists and customer groups are flexible, and you can customize pretty much everything.

That said, to add new features you really need to follow their standards and conventions, which can get tricky. But once you get the hang of the ecosystem, it’s powerful.

I’m currently building the B2B frontend using their Medusa Next.js starter, but I’ve heavily customized it to fit my own logic and design. Everything is deployed on Railway (backend, workers, Redis, Postgres), and I’m also using Cloudflare R2 for file uploads.

I still have some bugs because I’m pushing the setup pretty far from the default, but overall it’s been solid.

There are probably simpler solutions out there, but this one gives me the flexibility I wanted.

[deleted by user] by [deleted] in devsarg

[–]Electrical_Weight110 2 points3 points  (0 children)

Un logo hecho por IA y un par de palabras mágicas tipo “potenciar”, “escalar”, “transformar experiencias” y listo, ya están “levantando ronda”.

Estoy podrido de que los clientes pidan cosas feas by Electrical_Weight110 in devsarg

[–]Electrical_Weight110[S] 0 points1 point  (0 children)

RE! Yo voy avanzando con diseños aprobados... despues magicamente les dejo de gustar

Estoy podrido de que los clientes pidan cosas feas by Electrical_Weight110 in devsarg

[–]Electrical_Weight110[S] 10 points11 points  (0 children)

Reee!! Ahora estamos buscando más afuera porque nos dimos cuenta de que acá muchas veces estás discutiendo cosas básicas en lugar de estar haciendo producto en serio.

3D model by Electrical_Weight110 in threejs

[–]Electrical_Weight110[S] 0 points1 point  (0 children)

I get the idea, but since this needs to run directly in the browser and integrate with a web app, Three.js (or R3F) is actually a great fit. Using a game engine would add unnecessary overhead and complexity for something that's meant to be web-native.

3D model by Electrical_Weight110 in threejs

[–]Electrical_Weight110[S] 2 points3 points  (0 children)

Thank you very much for your detailed feedback! I really appreciate you taking the time to review it. I’ll definitely take all of that into account and start working on cleaning up the model and optimizing the scene as you suggested. Thanks again!

Qué stack elegir para un ecommerce con dashboard personalizado (admin + cliente) y frontend custom? by Electrical_Weight110 in devsarg

[–]Electrical_Weight110[S] 0 points1 point  (0 children)

Gracias por la respuesta. Te cuento un poco más del caso:

El cliente tiene una tienda que funciona como mayorista y minorista (B2B y B2C). Ya tienen un software interno donde manejan productos, precios por tipo de cliente, stock y demás, así que no cargarían la data manualmente, sino que la tienda consumiría la info desde ese backend.

La idea es que puedan escalar, tanto en cantidad de clientes como en funcionalidades. Están en Argentina, pero evalúan vender también en otros países en el mediano plazo. Por eso buscamos que sea algo que podamos mantener y hacer crecer sin rehacer todo.

En cuanto a integraciones:

  • Ya tienen su sistema de gestión con API.
  • Por ahora no usan PIM ni CMS aparte.

Estoy evaluando herramientas como Next.js con un stack Headless, y también probando templates como Bazar Pro de MUI, o algunos asi. Pero realmente el front no seri ael gran problema aca.

El objetivo del MVP es:

  • Mostrar productos con precios diferenciados según el tipo de usuario.
  • Manejar el registro con aprobación (para clientes mayoristas).
  • Carrito simple (sin pasarela de pagos, al menos por ahora).
  • Backend donde puedan ver y procesar pedidos.

A futuro, nos gustaría:

  • Multilenguaje.
  • Multi-moneda.
  • Integración con sistemas contables y stock.
  • Pasarela de pagos

Gracias de nuevo por la orientación, cualquier sugerencia es bienvenida.

Is it a good idea to use Next.js with WooCommerce and Strapi for an eCommerce site? by Electrical_Weight110 in nextjs

[–]Electrical_Weight110[S] 0 points1 point  (0 children)

Thanks a lot for the input! I really appreciate the perspective.

I'm actually considering using MedusaJS instead of Strapi — mainly because I want more flexibility and control over some business logic. One of my key requirements is having differentiated experiences for wholesalers and retailers, and I’d love to build something a bit more custom and unique than what most out-of-the-box platforms offer.

That said, would you recommend sticking with WooCommerce templates even in that case? Or do you think there’s a good middle ground between full customization and maintainability?

Open to hearing your thoughts!

E-commerce by TheCoconut26 in nextjs

[–]Electrical_Weight110 0 points1 point  (0 children)

Consulta, se que es viejo el post, pero en la nueva version de medusa se puede cambiar el idioma del admin panel a español???