Don't use the pre-built CSS in practice... setup your SCSS processor, and reference the built-ins directly... copy the main scss, update the paths and comment out the pieces you aren't using... override your variables (colors, details, options) and build directly. This will help you if you're integrating other tooling. Devs tend to make the mistake of modifying the original css build to change colors etc, and it winds up breaking things. Worse is when designers do it, and release patch css files for components, with a lot of duplications and more bugs.
Use the source, it's there for you.
Angular is probably not something you should jump into from a tutorial, if you aren't working against an existing project, you probably want to start with a good book, or from the getting started documentation[1].
Also, you probably don't want to work with Bootstrap this way... you should probably look toward ng-bootstrap[2] or another library meant for integration into the framework. You may also want to look into material design[3].
1. https://angular.io/start
2. https://ng-bootstrap.github.io/
3. https://material.angular.io/
Aside: Personally, I don't like Angular, I've used it from the old AngularJS to some of the newer versions. The DSL, API and complexity just irritate me. Creating just a simple hello world component in Angular compared to React or Vue will show you why you probably don't want to dive down that rabbit hole. Over half of Angular developers wouldn't want to use it again, and I've only ever met one developer who has worked with Angular and either React or Vue and would choose Angular... all of the rest would choose mostly React and a couple for Vue.
This is about the only place I would choose Vue over React is when I'm enhancing an existing, mostly static site/app. I feel the story is a lot better here for Vue. On the flip side, I find that for entire applications, I like React much better than everything else.
cute...
I have a relatively limited set of plugins I use though, and this is unlikely to make it onto the list. Would suggest, if you are considering it, to audit the code and the dependency code, then dev install.
Not saying this is a bad extension, only that with all that has come to light recently on plugins, trust is limited.
"React's use of JSX results in a steeper learning curve as you must learn this on top of familiarizing yourself with the library."
I cannot disagree more... JSX is an XML syntax mostly similar to html in it's lowest common denominator + JavaScript. For someone who should be familiar with JS and HTML going in, JSX is much less of a learning curve than a specific rendering DSL like Angular or others in practice.
The co-mingling of your component markup into your component JS is harder for those locked into a certain mindset to change, that does not make it harder conceptually.
Aside: materal-ui is the single nicest component library I have ever used in 24 years of working on web based applications. I've seen and used a *LOT* of tools and frameworks over the years. React + Material-UI feels right to me.
This is getting very cool... when I first looked at GraphQL a few years ago, the tooling was much less mature and took a lot of effort. It seems to be getting much better to use in practice. Would still like to see more articles about how to attach/handle security (jwt bearer tokens, for example) with a GraphQL server and client.
On #2, when using a getter that calls a function that can throw, it's a good idea to wrap in a try/catch as property getting should not be a point where an application throws in practice.
You could alternatively use the following pattern, and have your application loader parse and inject the configuration for the rest of your application to utilize...
export const configuration = {};
export function setConfiguration(data) {
Object.keys(configuration).forEach(c => {
delete configuration[c];
});
Object.assign(configuration, data);
};
export default configuration;
On #2, when using a getter that calls a function that can throw, it's a good idea to wrap in a try/catch as property getting should not be a point where an application throws in practice. You could alternatively use the following pattern, and have your application loader parse and inject the configuration for the rest of your application to utilize... export const configuration = {}; export function setConfiguration(data) { Object.keys(configuration).forEach(c => { delete configuration[c]; }); Object.assign(configuration, data); }; export default configuration;