Skip to content

Commit 7b93a6e

Browse files
committed
docs: fix more links
1 parent 3fd0123 commit 7b93a6e

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

packages/nuejs.org/@global/navigation.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ globalnav:
1515
# header toolbar (complementary)
1616
toolbar:
1717
- Slack: //join.slack.com/t/nuejs/shared_invite/zt-2wf8ozu5i-N2Y9PA_D17weIWuN2QPOqQ "slack"
18-
- 8.2k: //github.com/nuejs/nue "github pill"
18+
- 8.3k: //github.com/nuejs/nue "github pill"
1919

2020
# burger menu
2121
menu:

packages/nuejs.org/docs/interactivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Here, the view detects a form submission (step 1), sends the input to the model
4444

4545
## Routing
4646

47-
Routing in Nue drives navigation and state in single-page applications (SPAs), playing the controller role in the MVC pattern. Unlike React’s component-centric routing, Nue’s router — imported from `/@nue/app-router.js` — centralizes state and URL management, keeping views focused on display. It maps routes to data and components, syncing the app’s state with the browser’s URL. See the [router API](/docs/app-router.html) for full details.
47+
Routing in Nue drives navigation and state in single-page applications (SPAs), playing the controller role in the MVC pattern. Unlike React’s component-centric routing, Nue’s router — imported from `/@nue/app-router.js` — centralizes state and URL management, keeping views focused on display. It maps routes to data and components, syncing the app’s state with the browser’s URL. See the [router API](app-router.html) for full details.
4848

4949
Configure it like this:
5050

packages/nuejs.org/docs/reactivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ view_transitions: true
3636
3737
### Menus and dialogs
3838
39-
Today popovers, dialogs, and [burger menus](page-layout.html#burger) can be natively implemented with the [Popover API](//developer.mozilla.org/en-US/docs/Web/API/Popover_API) and page-transitions can be styled with the CSS [@starting-style](//developer.mozilla.org/en-US/docs/Web/CSS/@starting-style) at-rule:
39+
Today [popovers, dialogs, and burger menus](markdown-extensions.html#button-triggering-a-popover) can be natively implemented with the [Popover API](//developer.mozilla.org/en-US/docs/Web/API/Popover_API) and page-transitions can be styled with the CSS [@starting-style](//developer.mozilla.org/en-US/docs/Web/CSS/@starting-style) at-rule:
4040
4141
```css
4242
[popover] {
@@ -122,7 +122,7 @@ One major benefit of using a Web Component is that the browser automatically tak
122122

123123
### Dynamic sections { #sections }
124124

125-
You can turn all the [page sections](page-layout.html#sections) into web components with a `section_component` configuration option. This can be assigned in the front matter or globally in the application data. On the front page of this website, for example, we have a "scroll-transition" component to help implement all the scroll-triggered CSS transitions:
125+
You can turn all the [page sections](content-authoring.html#sections) into web components with a `section_component` configuration option. This can be assigned in the front matter or globally in the application data. On the front page of this website, for example, we have a "scroll-transition" component to help implement all the scroll-triggered CSS transitions:
126126

127127
```yaml
128128
section_component: scroll-transition

0 commit comments

Comments
 (0)