SSR ability for Web Components
This is a crucial consideration for me If I had Web Components for every layout component (having them rich -content -dynamic ) like hero , feature section etc . This would be absolutely insane but do they allow reliable serverside rendering , or even component -internal api requests ? My guess is no , but I want to have this confirmed . . . This would be relevant especially for SEO , and performance reasons . thx ! Since all of that would still have to be loaded Haha it is an ever confusing topic . 😆 I thought it would not be loaded , only on demand , as long as the request was server -side . And in the glorious intersection observer package @Jacob Kofoed stated , it would impact the loading of components . Jacob , can you assess how Nordcraft would behave in this scenario – having hundreds of components in one master -component , set to conditionally visible for dynamic content , like the nordcraft docs markdown ? Though I recognize it 's a bit different with nordcraft In some ways You can still accomplish it though , you may just have to reframe how you go about building it For something like web page /layout builder a similar approach may work Instead of necessarily hard -coding a bunch of components open , simply ok like what type of component but yeah , it should interact with contexts and so on (I hope , I 'm not wishing too much ) I 'm trying to think of what use cases would require loading components from API payloads Usually it 's stuff like forms or checkouts , dynamic things like taht When it comes to UI /layouts , that stuff is usually 'hard -coded ' thousand things , buddy ! my mind is exploding over this issue When you build an entire company in Nordcraft you would for example also want to build the website in it , but Nordcraft must become "invisible " , quasi "whitelabled " , when us , the developers build the "Webflow " for that company in Nordcraft in that companies ' company interface for example The app wouldn 't publish a bundle of components That would be a nightmare to maintain and build out Not to mention the performance implications you 're noting But what my builder would output would be final files The customer 's app wouldn 't load anything unnecessary Basically exactly what nordcraft does I 'm referring to the output The editor would have different ways to go about building it Idk , man , after all this magnificent stuff they built I can hardly believe that this is rocketscience , though it might be "hard to maintain " or "not best practices " it would open up a whole new world of possibilities for those maniacs like mine , obsessed over "keeping out " the clients / non -dev -members , out of nordcraft or a thousand other crazy ideas I could not wait to build , having assured this was possible . . . I 'm just saying I would try not to have a bunch of hard -coded components No , it is definitely possible Nordcraft is literally proof Essentially the gist of what we were saying was that having a lot of components loaded isn 't the only way to go about building that type of app out
.jpeg/public)