Replies: 1 comment 2 replies
-
|
I'm open to the idea - do you still use Primo or does this keep you from developing in it? |
Beta Was this translation helpful? Give feedback.
-
|
Developers likes Can I ask why Primo is limited to only static sites? Why not consider options such as Single Page Applications (SPA) or Server-Side Rendering (SSR)? why not having an option to use dynamic content? |
Beta Was this translation helpful? Give feedback.
-
|
As far as I can tell, the kinds of components you'd write for a web app are different from the ones you'd use on a content site (e.g. landing page, docs, etc.) so you wouldn't actually be copy-pasting between two code-bases, just keeping app components in one place and site components in another. But I agree that it's a hinderance, at least on the basis of demanding a change of habit.
Those are definitely possibilities, just a matter of resources |
Beta Was this translation helpful? Give feedback.
-
features:
write a component outside primo and import it to primo.
there would be a specification on how to write a svelte components that can be imported
write a component in primo and export it and use it in any svelte app
there would be a documentation on how to use primo components in svelte app
why is this important?
more flexibility:
more adaption and bigger community, etc...
Beta Was this translation helpful? Give feedback.
All reactions