diff --git a/meetings/2026-06-08.md b/meetings/2026-06-08.md
new file mode 100644
index 0000000..c6b0726
--- /dev/null
+++ b/meetings/2026-06-08.md
@@ -0,0 +1,54 @@
+# Node.js Web Team Meeting 2026-06-08
+
+## Links
+
+- **Recording**:  
+- **GitHub Issue**: https://github.com/nodejs/web-team/issues/143
+
+## Present
+
+- Aviv Keller @avivkeller
+- Brian Muenzenmeyer @bmuenzenmeyer
+- Matt Cowley @MattIPv4
+- flakey5 @flakey5
+- Augustin Mauroy @AugustinMauroy
+
+## Agenda
+
+## Announcements
+
+- Extracted from **web-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
+
+### nodejs/doc-kit
+
+- fix(web): shorten method labels in sidebar [#798](https://github.com/nodejs/doc-kit/pull/798)
+    - Minifying is fine, omitting overloads.
+    - Always use the heading that is first (which should _always_ be the most stable)
+    - Show only one entry per function (the function name itself rather than full signatures), linking to the most stable version.
+    - Maintain both compact and full anchor versions in the page content to allow deep linking while keeping the table of contents simpler.
+- feat: assets copying [#753](https://github.com/nodejs/doc-kit/pull/753)
+    - Use `pathsToCopy: [{ '/path/to/my/assets': '/path/to/my/output' }, '/path/to/my/other/asset']`
+    - Use a config-based approach with default directories (e.g. `public` or `assets`) that users can override if needed.
+- Monorepo? [#681](https://github.com/nodejs/doc-kit/issues/681)
+    - Package size and memory usage are a concern. Could reduce size by moving certain dependencies to optional peer dependencies and breaking generators out into separate packages.
+        - Aviv will work on trimming dependencies in `@node-core/ui-components`, which attributes to most of the size problem. 
+    - Aviv reported memory allocation problems integrating doc-kit into Core, particularly out-of-memory errors on CI runners with limited memory (e.g. Ubuntu Slim). To be investigated and optimized.
+
+### nodejs/web-team
+
+- Update our policies on relevancy [#98](https://github.com/nodejs/web-team/issues/98)
+    - After reviewing the policy as a group, and making slight amends to the wording, the updated policy has landed in [#112](https://github.com/nodejs/web-team/pull/112).
+- Require secondary approval for fast-track [#97](https://github.com/nodejs/web-team/issues/97)
+    - Fast-tracking limited to changes that are "urgent or time sensitive" (trivial fixes removed).
+    - Written justification now required for bypassing standard processes / unorthodox merges.
+
+## Q&A, Other
+
+- Chase the open auto-merge issue, and propose to use a GitHub App token as an alternative to generating multiple tokens.
+- Write access to Node.js repositories was granted to several external contributors without proper documentation or approval, bypassing standard onboarding processes and violating security policy. We've removed the external contributors' access.
+
+## Upcoming Meetings
+
+- **Node.js Project Calendar**: <https://nodejs.org/calendar>
+
+Click `Add to Google Calendar` at the bottom left to add to your own Google calendar.