docs(blog): integrate HTML module support as entry points without plugins

Author: bjohansebas

src/content/blog/2026-04-02-roadmap-2026.mdx

@@ -31,7 +31,9 @@ and there’s still much more to do
 
 - **TypeScript** — built-in support. [`enhanced-resolve`](https://github.com/webpack/enhanced-resolve) honors [`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html). Add parser wrapper to `module.javascript.parse`, improve resolver for `ts/cts/mts`, support `extensionAlias`, and add tests.
 
-- **HTML modules** — first-class HTML: import HTML files and use HTML entry points. Aim to replace `html-webpack-plugin`. See [webpack#536](https://github.com/webpack/webpack/issues/536).
+### Import HTML files and use them as entry points without the need for plugins
+
+Currently, to import HTML files and use them as entry points, it’s necessary to use a plugin (html-webpack-plugin). The idea is to integrate that plugin into the core, similar to how CSS Modules are being handled, and remove the need for a plugin for such a common task. Like CSS Modules, this would be introduced as an experimental option so that in webpack 6 you’ll be able to remove that dependency. You can follow the idea and its progress in [webpack#536](https://github.com/webpack/webpack/issues/536).
 
 - **ESM output** — fixes and improvements. See [webpack#17121](https://github.com/webpack/webpack/issues/17121).