* Website: Follow up to strip leading slashes
re https://github.com/fleetdm/fleet/pull/6796#issuecomment-1193054810
* remove log
* Verified: whitespace trim not needed
And leading slash trim is only needed if using a regex route (not something I recommend most of the time). But since we are using one, I included it, and put it in all three places for consistency. (It doesn't ever hurt)
* Simplify regex syntax used for #2025
* extra trailing slashes now redirect instead of rendering
* Simplify regex
* Match implementation to view-basic-documentation, etc
* Match view-basic-documentation, and slurp up title and description logic to help indicate (and future proof) that it has no side effects
* Update view-basic-handbook.js
* Update view-basic-documentation.js
* trivial
* lint fix
* make handbook and doc landing pages continue working despite my recent commit in this same PR, and add some comment clarifications
* update regex to replace leading slashes and whitespace
Co-authored-by: Eric <eashaw@sailsjs.com>
* articles page
* update articles route to handle category urls
* update articles page
* add articleImageUrl meta tags to article pages
* basic empty state, add comments
* Update view-articles.js
* Update articles.less
* add articles, update styles and image url validation
* lint fix
* Update routes.js
* Update articles.ejs
* Update articles.page.js
Updated article category descriptions.
* migrated more articles
I migrated more articles so that all categories are populated.
* Added thumbnails to new posts
* Some style tweaks
- Tweaked a couple of styles
- Added cursor: pointer to filters
- Changed "Blog" to "Articles" in the navigation
- Changed /blog to /articles in the navigation
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
