Update roadmap with Prototype Pages info

bridgetownrb · Apr 21, 2020 · ae4e220 · ae4e220
1 parent f6848d1
commit ae4e220
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/bridgetown-website/src/about.md b/bridgetown-website/src/about.md
@@ -23,7 +23,8 @@ As of spring 2020, here is the vision for where Bridgetown is headed. And this i
 - ✅ _DONE!_ **Improve default site file/folder structure** to bring Bridgetown in line with other popular static site generators.
 - ✅ _DONE!_ Add a `bridgetown console` command to **interactively interact with the site data and plugins** (just like the Rails console).
 - ✅ _DONE!_ Remove the aging asset pipeline and **regroup around a modern solution: Webpack**. (Similar to how Rails adopted Webpack and distanced itself from Sprockets.) [Check out the preliminary documentation here.](/docs/frontend-assets/)
-- ✅ _DONE!_ Integrate **pagination features** directly into the monorepo.
+- ✅ _DONE!_ Integrate **pagination features** directly into the monorepo. [Preliminary docs here.](/docs/content/pagination/)
+- ✅ _DONE!_ Add streamlined **taxonomy pages (for categories, tags, and other metadata)** solution (called [Prototype Pages](/docs/prototype-pages/).)
 - ✅ _DONE!_ Move most site data vars to a **reloadable file** (aka `_data/site_metadata.yml`). Coming soon: env-specific settings (development vs. production).
 - ✳️ _IN PROGRESS…_ Modernize various aspects of the codebase, incrementally **improving
   the developer experience (DX)** on a number of different fronts.
@@ -32,7 +33,6 @@ As of spring 2020, here is the vision for where Bridgetown is headed. And this i
 - ✳️ _IN PROGRESS…_ **Liquid Components** — this would build upon the new `render` tag functionality and add a ton of new features to make component-based design and authoring a reality, bringing Ruby/Liquid syntax closer to the world of React & Vue. Ready for "Bridgebook"? 😁 (aka integration with Storybook.js). [Preliminary spec here.](https://github.com/bridgetownrb/liquid-component)
 - Straightforward support for **third-party data APIs** (think GraphQL as a first-class citizen).
 - Easy **multilingual setup** right out of the box.
-- Add streamlined **taxonomy pages (for categories, tags, and other metadata)** solution.
 - **Simple webhooks** — allow remote webhooks to be pinged after a successful build.
   - **“Private” pages** — aka put a website section behind a randomized URL that changes frequently and then allow that to be pinged to a webhook somewhere.
 - **Auto-reload plugins** during development. (No more stop-and-restart every 5 seconds!)