Skip to content

Commit a98e870

Browse files
committed
part 7c
1 parent f6fdc21 commit a98e870

File tree

2 files changed

+87
-94
lines changed

2 files changed

+87
-94
lines changed

src/content/7/en/part7c.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ In part 2, we examined two different ways of adding styles to our application: t
1313

1414
One approach to defining styles for an application is to use a ready-made "UI framework".
1515

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.
1717

1818
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.
1919

@@ -411,7 +411,7 @@ we do get working navigation, but it could look better
411411

412412
![browser notes app materialUI blue navbar](../../images/7/66ea.png)
413413

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.
415415

416416
By defining
417417

@@ -421,7 +421,7 @@ By defining
421421
</Button>
422422
```
423423

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_.
425425

426426
The code for the navigation bar is the following:
427427

@@ -489,7 +489,7 @@ There is also the question of whether or not UI framework libraries should be us
489489

490490
### Other UI frameworks
491491

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.
493493

494494
- <https://bulma.io/>
495495
- <https://ant.design/>

0 commit comments

Comments
 (0)