Next.js Commerce store, one-click deploy to Netlify
github.com
github.com
Be wary when using eCommerce SDKs, especially in the absence of exact, legalese-free clarification about what "data processing" means. Here is the privacy policy: https://www.iubenda.com/privacy-policy/60591797/full-legal
Keep in mind that if Chec is acquired, the durably stored data will also be transferred per this policy. Beyond the usual callouts like fraud and geolocation, the policy also allows the company to use customer data to "improve its services", with no specificity on what exactly that would entail.
What bothers me about these lowering the bar for new front end developer/designer is that it is free feast for these kind of non compliance :(
Based on living in the US and seeing many reactions similar to yours over time, I would say your "problem" isn't that new people are getting into an industry. Your problem is that you need to get over yourself and grow up. Sorry the normies make it hard for you to think of yourself as an elit3 uberhax0r anymore, but nobody really cares.
I'm tired of these people that dont understand how easy it is to violate personal privacy with digital technology getting into digital technology.
I'm happy for you that you love the work so much to even have such a perspective. But it isn't a fair perspective to everyone else.
software development is NOT for everyone. Either you got or you put in a lot of work and get it. Other wise go do something else.
Programming isn’t special. If someone wants to do it for a job, so be it. Shame on you for trying to gatekeeper what they learn or do.
Don't judge people by the reasons they want to become devs.
I wanted to do it out of passion, I do it even in my free time, when I'm bored, but many people don't and that's okay.
http://support.commercejs.com/en/articles/1942216-gdpr-with-...
> We collect our merchants’ customers’ name, email, shipping and billing address, payment details, company name, phone number, IP address, information about orders you initiate, information about the Chec powered merchant stores/integrations that you visit and interact with, and information about the device and browser you use.
The FAQ is "what" and "why", but only the "what" is answered.
I told my boss that, while I was not a lawyer, in my opinion we simply could not sign that contract and provide a service without blatantly violating the then-recent GDPR. (We didn't sign it, although I don't know if that played a part.)
Chec seems to be using a similar approach? They're running a B2B service which doesn't provide analytics opt-out, and their B2C users are supposed to tell the customers "hey, we can't offer you an opt-out on data collection because it's required to make the software platform work" (except that you're not required to run your store on Chec specifically, otherwise it would be a trivial method to bypass the GDPR).
Nonetheless, it's inexcusable that the words 'purpose' and 'analytics' do not appear in that blog post. Those are essential aspects of the GDPR, and if you're not explicitly stating that you won't re-sell the collect data to third parties without the owner's consent, I assume you do.
It looks like rendering a new page is blocked until API requests to both "categories" and "products" endpoints are completed, which is terrible. They should be background requests that aren't render-blocking. Also, these requests fire _every time_ you click a link.
Right now, the user experience is 0/10. Would not recommend.
As you say, the large images and poor navigation are definitely separate issues.
we're clearly discussing radically non-optimized (ie, misconfigured) build, making criticisms of nextjs per se entirely moot.
From the looks of that issue there are workarounds in some instances though.
Some notes:
- This looks like a SPA - And it's a really bad pattern for e-commerce.
- There are a lot of issues with Web Vitals. TTFB is blocking user interaction.
- Looks like SEO (due to SPA) is not being correctly populated?
- It's using Redux (Why??)
- Uses React Classes (Why???)
I'd recommend taking a look at https://nextjs.org/commerce where you can check all recommended patterns from Next.js 10 and more to deploy a successful e-commerce site.
Next.js Commerce supports:
- i18n Internationalization
- Lazy and eagerly loading Images with the Image Component
- Responsive by default
- UI Components
- SEO Ready
- Easily Customizable with TailwindCSS - Themes!
- Data Hooks - to fetch data from your headless e-comm of preference. (BigCommerce support by default)
- Site Speed due to Incremental Static Regeneration and blocking rendering/fallback when needed.
- Auth
and if you deploy with Vercel you have Analytics to stay on track - REAL Web Vitals are key for successful e-commerces.
This means you can easily clone this and run your own store with good practices: e.g https://chicos-commerce.vercel.app/ - Also built with Next.js Commerce.
A few years ago, I had a tiny studio where I built and sold small webshops.
I have no idea how I'd convince a small customer how this is any better than WooCommerce slapped on a $5 droplet.
After a while, I swallowed my pride and started to use them. I am not building the next google, or the next Uber. I'm writing projects on the side for small businesses.
Nothing comes even close to the wordpress, PHP ecosystem. Nothing
I’m not a fan. But I’m not a fan for the use case of major publishing platform.
For small businesses, small e-commerce, small blogs or publications it’s great. But for the love of god, I wish people would stop extrapolating that fact to mean it’s good for everything. But now there’s a cottage industry built around selling that very idea to ignorant people for a high fee. Total racket.
If it's going to take more than a week, I directly involve Entity Framework (recently more Dapper than EF but anyway), React/Next.js, Typescript (switched from NHibernate + knockout.js to this stack lately). Most of the pages are rendered on the server. Performance is crazy. Maintainability is great too! They need to call me, or hire one of the many react/.NET devs available if an update/migration is needed, but it's easy to understand as no magic is involved.
We need to understand that these 2 are shockingly separate worlds. So, all these words just to say that I agree with you :) But there is one catch: Sometimes a quickly implemented site organically grows into multi-sites, or into an app that does more than to manage content, that's the point the customer needs to understand these concepts too.
Better to explain to them from the beginning!
I see so many major publishers doing just what I've described, too, and it bewilders me. There are still a lot of brilliant people working in publishing, even traditional publishing. See the New York Times digital teams, after all.
But there is a gaping void of high-functioning software for digital publishing that is extensible, and that is easily integrated with existing workflows (InDesign/InCopy as either an endpoint or an entry point—or better yet, two-way) and capable of multichannel publishing out of the box.
And not just in the creative and digital ends. There is a sore lack of labour-reducing software in the print world as well. Flyer creation—tens of thousands of hours a year are burned just moving data from a spreadsheet into templates. (I have similar critiques of Excel here: use it for the data entry, tabling, what have you. But don't try and make your mock-up layout in there and expect that to 1:1 translate to InDesign without any labour. And for the love of god do not promote it as such)
The impasses I've seen are as such: a lot of tech assumes publishing and printing are "dead", people in industries that have tradition baked into workflows are not open to learning a new tool every year to do the same task so it needs to be a substantial improvement/change, and publishing doesn't have the same piles of VC/investor cash behind it that it had in the 90's (much like "tech" does now).
But I digress...
You don’t have to build Wordpress sites as a freelancer if you’re in a good commercial position where you can find other kinds of work, but to your point I agree that one needs to admit when it’s the better solution. And for small businesses, it’s quite often so.
Maybe it's not in this demo yet.
That being said, maybe it's because Vercel already made a Next.js Commerce product: https://nextjs.org/commerce
I'm currently running a cobbled together "stack" on my solar site https://sunboxlabs.com (Hugo, Paypal, NetlifyCMS, custom JS for coupon and affiliate codes) and have been refusing to move to Shopify.
Maybe I'll give one of these two a shot. 3% on top of the CC processing fees is not too bad. But not great either for a $599 product...
The other big show-stopper from our experience is multi-lingual support, but tbh that sucks on 95% of ecommerce platforms.
Is there a way to test the administration pages?
I didn't have any issues with buy-in since we were only a few people at the time and basically got the ok as long as there wasn't any downtime in the transition (which there wasn't).