Thank you, I really like working with you too :)

You're awesome :)

author here, happy to answer any questions.

Agreed that they're separate, just wondering if anyone has experience using them in a production application.

Tailwind examples/docs are mostly for react so was wondering if there are any gotcha's that come about later down the line.

I've been a data engineer for years but still struggle with my local environment for data development. So I converted jupyter & airflow into plug-n-play apps and wrote a tutorial on how to set them up for local data development.

Let me know if you think this is a good approach and happy to answer any questions :)

Hi HN, author here and happy to answer any questions :)

<3 thank you! I've learnt a lot from you and the pleasure is all mine

Could someone explain to me why using a react app built using CRA is bad in this case? I have a similar use case where the app is on app.example.com (built using CRA) and I have a landing page (also built using CRA) on example.com

The landing page links to: - The App at app.example.com - Docs at docs.example.com - Blog at blog.example.com

I have 0 front-end experience so this is an honest attempt at understanding why I should NOT be using the CRA for a landing page.

The landing page isn't doing much so its a very simple react app. But don't understand the implications on SEO

It might be because CRA does not have server side rendering and it is hard for some search engines to index pages if they are entirely rendered the client side.

Also CRA comes with tons of dependencies. If all we need is to display some texts and images, as most landing pages are wont to be, it makes little sense to utilize such complex technology stack.