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
Copy file name to clipboardExpand all lines: src/content/7/en/part7c.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ In part 2, we examined two different ways of adding styles to our application: t
13
13
14
14
One approach to defining styles for an application is to use a ready-made "UI framework".
15
15
16
-
One of the first widely popular UI frameworks was the [Bootstrap](https://getbootstrap.com/) toolkit created by Twitter which may still be the most popular framework. Recently, there has been an explosion in the number of new UI frameworks that have entered the arena. The selection is so vast that there is little hope of creating an exhaustive list of options.
16
+
One of the first widely popular UI frameworks was the [Bootstrap](https://getbootstrap.com/) toolkit created by Twitter which may still be the most popular. Recently, there has been an explosion in the number of new UI frameworks that have entered the arena. The selection is so vast that there is little hope of creating an exhaustive list of options.
17
17
18
18
Many UI frameworks provide developers of web applications with ready-made themes and "components" like buttons, menus, and tables. We write components in quotes because, in this context, we are not talking about React components. Usually, UI frameworks are used by including the CSS stylesheets and JavaScript code of the framework in the application.
19
19
@@ -411,7 +411,7 @@ we do get working navigation, but it could look better
411
411
412
412

413
413
414
-
We can find a better way from the [documentation](https://mui.com/material-ui/guides/composition/#routing-libraries). We can use [component props](https://mui.com/material-ui/guides/composition/#component-prop) to define how the root element of a MaterialUI component is rendered.
414
+
We can find a better way in the [documentation](https://mui.com/material-ui/integrations/routing/#button). We can use [component props](https://mui.com/material-ui/guides/composition/#component-prop) to define how the root element of a MaterialUI component is rendered.
415
415
416
416
By defining
417
417
@@ -421,7 +421,7 @@ By defining
421
421
</Button>
422
422
```
423
423
424
-
the _Button_ component is rendered so that its root component is react-router-dom's _Link_ which receives its path as the prop field _to_.
424
+
the _Button_ component is rendered so that its root component is react-router-dom's _Link_, which receives its path as the prop field _to_.
425
425
426
426
The code for the navigation bar is the following:
427
427
@@ -489,7 +489,7 @@ There is also the question of whether or not UI framework libraries should be us
489
489
490
490
### Other UI frameworks
491
491
492
-
Here are some other UI frameworks for your consideration. If you do not see your favorite UI framework in the list, please make a pull request to the course material.
492
+
Here are some other UI frameworks for your consideration. If you do not see your favorite UI framework in the list, please make a pull request to the course material for adding it.
0 commit comments