Why write an article for a broken code base?

[mikepuerto]

I did not feel any of the questions were relevant to my "issue" I'm just curious as to why This article on Medium is NO WHERE near accurate to: nextjs-react-strapi-deliveroo-clone-tutorial ?

These sorts of things just throw people off as I'm sure you can tell by all the comments. Being that this is an "official" strapi article, it only makes sense that you properly write the article and don't leave steps out that appear to be sending everyone for a loop.

[Pedrock]

And it has no back-end validation of the payment with Stripe: huge vulnerability!

[soupette]

@mikepuerto I agree we are rewriting these articles at the moment!

[Palgie]

@soupette Thanks for revisiting these articles. If I could I'd like to put these two ideas forward for the refresh:

• Back-end validation of the payment from Stripe (as @Pedrock mentioned).
• Syncing product records to Stripe to use alongside Stripe Orders API rather than simple Stripe Transactions (Maybe a good way to demonstrate using Strapi lifecycle updates to mirror create / update)

Think these would make a great difference to the end result due to the added benefits.

Excited to see the see the new articles and source!

[krynv]

Have these been rewritten & submitted anywhere yet?

[8kigai]

I don't feel like the authentication and authorization should be written like this. Some of the code just don't make sense.