You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reckon this might be totally out of scope for the project, but since I find myself in the position of wanting this, I do wonder if someone else does, and in that case, if it would be of interest for the prime users to have such a package/boilerplate/documentation available, and of course, as long as @birkir allows it and considers it makes sense. If not it might be just a good exercise to document here or on a blog post or gist or somewhere else.
The thing is, I had never used TypeScript before knowing primeCMS, and also either of the libraries it's using. Peeking around the codebase, has helped me discover great gems like typeorm (which I already adopted and developed my seeds/factories with, thanks to a great w3cc example on a tpyescript/typegraphql seeding.
Anyways, I find myself wanting to replicate pretty much all the basic-libs primeCMS is using, but for a bigger project which may benefit from a CMS, but it requires much more stuff to be developed asides from the CMS as a social/marketplace/platform.
So what I am really asking.
I want to create a trimmed version of prime-core/ui which allows anyone to boilerplate/scaffold a project however they want.
Adding or not CMS features for all or partial of the codebase, should be optional.
I want to use all the same libs, just weight it down so it's usable in more scenarios, both with or without a need for a CMS
does this make any sense?
Do feel free to reject it if it's just not for this project, I understand it's not exactly on the direction of the beta or the roadmap that has been shared so far.
The text was updated successfully, but these errors were encountered:
I reckon this might be totally out of scope for the project, but since I find myself in the position of wanting this, I do wonder if someone else does, and in that case, if it would be of interest for the prime users to have such a package/boilerplate/documentation available, and of course, as long as @birkir allows it and considers it makes sense. If not it might be just a good exercise to document here or on a blog post or gist or somewhere else.
The thing is, I had never used TypeScript before knowing primeCMS, and also either of the libraries it's using. Peeking around the codebase, has helped me discover great gems like typeorm (which I already adopted and developed my seeds/factories with, thanks to a great w3cc example on a tpyescript/typegraphql seeding.
Anyways, I find myself wanting to replicate pretty much all the basic-libs primeCMS is using, but for a bigger project which may benefit from a CMS, but it requires much more stuff to be developed asides from the CMS as a social/marketplace/platform.
So what I am really asking.
I want to create a trimmed version of prime-core/ui which allows anyone to boilerplate/scaffold a project however they want.
Adding or not CMS features for all or partial of the codebase, should be optional.
I want to use all the same libs, just weight it down so it's usable in more scenarios, both with or without a need for a CMS
does this make any sense?
Do feel free to reject it if it's just not for this project, I understand it's not exactly on the direction of the beta or the roadmap that has been shared so far.
The text was updated successfully, but these errors were encountered: