content: #255 final draft

Author: thescientist13

src/pages/blog/state-of-greenwood-2025.md

@@ -19,11 +19,11 @@ layout: blog
           /assets/blog/greenwood-logo-1000w.webp 1000w,
           /assets/blog/greenwood-logo-1500w.webp 1500w"/>
 
-Looking back on the past year since our [previous end of year post for 2024](https://greenwoodjs.dev/blog/state-of-greenwood-2024/), the Greenwood team held true to its promise ensuring a broad set of ecosystem compatibility around import map generation, adapters, and package managers, as well as continuing our participation in related standards and community groups.
+Looking back on this past year since our previous [end of year post](https://greenwoodjs.dev/blog/state-of-greenwood-2024/), the Greenwood team held true to its promise in ensuring a broad set of ecosystem compatibility around import map generation, hosting adapters, and package managers, as well as continuing our participation in related standards and community groups. Greenwood was even featured in the latest episode of [Shop Talk Show](https://youtu.be/CuBKsa92nL0?si=Iq4adydliQ3ksN03&t=2775)!
 
-For component libraries, you can see demonstrations of using Greenwood with [**Spectrum Web Components**](https://github.com/thescientist13/greenwood-lit-ssr/tree/demo-spectrum), [the **USWDS**](https://github.com/thescientist13/greenwood-lit-ssr/tree/demo-uswds), and [**Web Awesome**](https://github.com/thescientist13/greenwood-lit-ssr/tree/web-awesome). All of these help further refine and validate Greenwood's capabilities for generating import maps, inlining and bundling CSS and package manager support; all in the pursuit of making sure you can always use your favorite library with Greenwood as simply as running `npm i`. In addition, we've created demonstration repos for using Greenwood with [**tRCP**](https://github.com/thescientist13/greenwood-trpc) and [**Lume**](https://github.com/thescientist13/greenwood-lume) (still dependent on upcoming changes in v0.34.0).
+For component libraries, you can see demonstrations of using Greenwood with [**Spectrum Web Components**](https://github.com/thescientist13/greenwood-lit-ssr/tree/demo-spectrum), [the **USWDS**](https://github.com/thescientist13/greenwood-lit-ssr/tree/demo-uswds), and [**Web Awesome**](https://github.com/thescientist13/greenwood-lit-ssr/tree/web-awesome). These demonstration projects helped further refine and validate Greenwood's capabilities for generating import maps, inlining and bundling of CSS, and supporting the most popular package managers in the ecosystem; all in the pursuit of making sure you can always use your favorite library with Greenwood as simply as running `npm i`. In addition, we've created demonstration repos for using Greenwood with [**tRCP**](https://github.com/thescientist13/greenwood-trpc) and [**Lume**](https://github.com/thescientist13/greenwood-lume) (still dependent on upcoming features coming in our [v0.34.0](https://github.com/ProjectEvergreen/greenwood/issues/1597) release).
 
-On the community side, we were happy to see the WinterCG [graduate and become an official ECMA Technical Committee group](https://www.w3.org/community/wintercg/2025/01/10/goodbye-wintercg-welcome-wintertc/) as the [WinterTC(55)](https://ecma-international.org/technical-committees/tc55/). Promoting standards for both the web and sever-side JavaScript runtimes is a valuable and meaningful vision and effort for the Greenwood team, and are happy to participate and contribute to the WinterTC and the [WCCG (Web Components Community Group)](https://www.w3.org/community/webcomponents/).
+On the community side, we were happy to see the WinterCG [graduate and become an official ECMA Technical Committee group](https://www.w3.org/community/wintercg/2025/01/10/goodbye-wintercg-welcome-wintertc/) as the [WinterTC(55)](https://ecma-international.org/technical-committees/tc55/). Promoting standards for both the web and sever-side JavaScript runtimes is a valuable and meaningful vision and effort for the Greenwood team, and we are happy to participate and contribute to the WinterTC and the [WCCG (Web Components Community Group)](https://www.w3.org/community/webcomponents/).
 
 We hope these initiatives and improvements over the past year have worked to make Greenwood even better for building websites so please feel free to share your thoughts and feedback with us.
 
@@ -33,7 +33,7 @@ Now, on to the year in review! 👇
 
 ### TypeScript Support
 
-Greenwood now provides built-in support for TypeScript, with the ability to fallback to using `tsc` if certain TypeScript features you're using (like Decorators, [enums, namespaces, etc](https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/#the---erasablesyntaxonly-option)) are not supported through just type stripping alone. This was motivated in part due to NodeJS adding support out of the box. This means you can write your entire project, including SSR pages and API routes, entirely in TypeScript with no configuration required!
+Greenwood now provides built-in support for TypeScript, with the ability to fallback to using `tsc` if certain TypeScript features you're using (like Decorators, [enums, namespaces, etc](https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/#the---erasablesyntaxonly-option)) are not supported through just type stripping alone. This was motivated in part due to NodeJS adding TypeScript (type-stripping) support out of the box. This means you can write your entire project, including SSR pages and API routes, entirely in TypeScript with no configuration required!
 
 This also means that you can author your Greenwood configuration files and plugins with TypeScript too:
 
@@ -48,7 +48,7 @@ const config: Config = {
 export default config;
 ```
 
-For actual _type-checking_, below is Greenwood's recommended _tsconfig.json_ settings so that you can run `tsc` during CI.
+For actual _type-checking_, below is Greenwood's recommended _tsconfig.json_ settings so that you can get full IDE support and so that you can run `tsc` during CI.
 
 <!-- prettier-ignore-start -->
 
@@ -96,7 +96,7 @@ $ npx @greenwood/init@latest
 
 This year we released an official adapter plugin for generating Lambda compatible function code for your SSR pages and API routes with AWS. ☁️
 
-SimplY install the plugin and add it to your Greenwood config file:
+Simply install the plugin and add it to your Greenwood config file:
 
 ```js
 import { greenwoodPluginAdapterAws } from "@greenwood/plugin-adapter-aws";
@@ -112,7 +112,7 @@ Taking into consideration that there are many methods and options for deploying
 
 ## The Year Ahead
 
-As the team looks to the coming year ahead, we're currently in progress on the next Greenwood release; [v0.34.0](https://github.com/ProjectEvergreen/greenwood/issues/1597), which we aim to release with a key feature being dynamic routes, which will allow file-system based routing like below, including for our serverless adapter plugins:
+As the team looks to the coming year ahead, we're currently in progress on the next Greenwood release; [v0.34.0](https://github.com/ProjectEvergreen/greenwood/issues/1597), which we aim to release with a key feature; dynamic routes! Dynamic routes will allow file-system based routing like below for serving dynamic routing paths, and will be supported by all our serverless adapter plugins:
 
 ```shell
 src/
@@ -121,7 +121,13 @@ src/
       [slug].js
 ```
 
-Although dependent on compatibility and upstream needs on these platforms and runtimes, we are actively working on **Bun** runtime support as well as an official **Cloudflare** adapter. Both of these are in various stages of development and testing, and we hope to close out our current ecosystem milestone with by delivering on them in some capacity.
+This would serve any number of the following routes:
+
+- `/blog/my-first-post/`
+- `/blog/my-second-post/`
+- etc
+
+Additionally, and although dependent on compatibility and upstream needs on these platforms and runtimes, we are actively working on **Bun** runtime support as well as an official **Cloudflare** adapter. Both of these are in various stages of development and testing, and we hope to close out our current ecosystem milestone by delivering on them in some capacity.
 
 Lastly, and already [supported in **WCC**](https://merry-caramel-524e61.netlify.app/docs/#tsx), TSX support will be coming to Greenwood for scripts and SSR pages, enabling JSX for templating through a custom `render` function, enabling **type-safe** HTML!
 
@@ -165,12 +171,8 @@ customElements.define("x-card", Card);
 
 > You can see a preview of this upcoming work in [this demonstration repo](https://github.com/thescientist13/greenwood-jsx).
 
----
-
-The Greenwood team is very eager to wrap up our current efforts to release v0.34.0 and continue our ongoing march towards a [1.0 release](https://github.com/ProjectEvergreen/greenwood/milestone/3).
-
 ## In Closing
 
-Greenwood wants to be there every step of the way to help you get the most out of the web and ensure you have full ownership of your code and content. From SPA to SSG to SSR and everything in between, building vanilla or with friends, we want Greenwood to run wherever the web can run so the choice can always be yours.
+The Greenwood team is very eager to wrap up our current efforts to release v0.34.0 and continue our ongoing march towards a [1.0 release](https://github.com/ProjectEvergreen/greenwood/milestone/3). Greenwood wants to be there every step of the way to help you get the most out of the web and ensure you have full ownership of your code and content. From SPA to SSG to SSR and everything in between, building vanilla or with friends, we want Greenwood to run wherever the web can run so the choice can always be yours.
 
 Please come join us on [GitHub](https://github.com/ProjectEvergreen/greenwood) and [Discord](/discord/) and we can't wait to see what you build with Greenwood! <img style="width: 15px; display: inline-block; margin: 0;" src="/assets/blog/evergreen.svg" alt="Project Evergreen logo"/>