My process to decide which framework, library, etc to use. 1.

Question

My process to decide which framework, library, etc to use. 1.

What does already exist?
It doesn't make sense to pull in an entirely new framework if one already is in place. No matter if server-side only or full-stack (laravel -> vue, next, nuxt, etc) if you have standalone php or html pages where you need to integrate a framework, may become cumbersome to manage. If I could, I would always try to reach for a base framework like nuxt, vuepress or whatever on the clientside to give me the opportunity to easily extend. While we are at extending:
2. Plan for more
If all you need is one standalone gadget or widget, you will be fine finding one standalone library doing only one thing.
If you need an entire app with interconnected components, you should pick a framework and pick your ui components based on that framework. Then follow this path:
if you need a design system to make things look alike across a wide range of pages and views: pick a collection of ui components (such as vuetify, quasar, ionic, bootstrap, ant, etc)
If you need a specific component that does not exist within that design system or you don't want to have the overhead of a design system: search with npm or github or cdn or even google for the package you are looking for. If you use a framework, use that as an additional keyword.
3. How is your project built and deployed?
Do you have a build step for the front-end to allow bundling of npm packages? If not, chances are, that this npm package is also available as standalone package via cdn or to copy to your own file structure. as in step 2, you can still use these keywords to search for that package you need.

0

20.07.2020

1 ответов

21 просмотр

commandline · Accepted Answer

commandline

thanks for clarity

0

20.07.2020

Похожие чаты

My process to decide which framework, library, etc to use. 1.

1 ответов

Похожие вопросы