Skip to content

Commit f9d270c

Browse files
committed
Add Build //LOCALHOST section and update event timing in documentation
1 parent 8d06b01 commit f9d270c

3 files changed

Lines changed: 10 additions & 2 deletions

File tree

.vitepress/config.mjs

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,14 @@ export default defineConfig({
111111
{ text: 'FAQ', link: '/agentcamp/faq' },
112112
]
113113
},
114+
{ text: 'Build //LOCALHOST', link: '/build/organize',
115+
collapsed: true,
116+
items: [
117+
{ text: 'Register', link: '/build/register' },
118+
{ text: 'Branding', link: '/build/branding' },
119+
{ text: 'Content', link: '/build/content' },
120+
]
121+
},
114122
]
115123
},
116124
{

build/organize.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ We are in the early stages of planning Microsoft Build //LOCALHOST, so n
1010
:::
1111

1212
### Key things to know!
13-
- **Time frame:** Within 21 days after Microsoft Build (typically late May – mid June 2026).
13+
- **Time frame:** Directly after Build 2026 (June 4–30, 2026).
1414
- **Topic:** Microsoft Build content redelivery
1515
- **Event Format:** MeetUp
1616
- **Duration:** 3–4 Hours (Evening)

build/register.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ External registration platforms (Eventbrite, Meetup, etc.) are not allowed for B
2929
:::
3030

3131
## Step 4 - When
32-
- Enter the date (must be within 21 days after Microsoft Build)
32+
- Enter the date (directly after Build 2026, between June 4–30, 2026)
3333
- Enter the time, use the local time
3434
- Set the timezone
3535

0 commit comments

Comments
 (0)