Fix crossword url on dev server

Author: DanielCliftonGuardian

dotcom-rendering/src/server/dev-index.html

@@ -648,8 +648,13 @@ <h2>Test Articles By Element (Missing)</h2>
 				// All interactive pages include this in the URL
 				if (url.includes('/ng-interactive/')) return 'Interactive';
 				// We're looking for the date string, e.g /2022/jul/30
-				else if (url.match(/[0-9]{4}\/[a-z]{3}\/[0-9]{2}\/.+/))
+				else if (
+					url.match(/(\/\d{4}\/[a-z]{3}\/\d{2}\/|\/[a-z-]+\/\d+$)/)
+				)
 					return 'Article';
+				// This is imperfect, but covers some cases of tag pages, consider expanding in the future
+				else if (url.match(/\/(tone|series|profile)\/[a-z-]+/))
+					return 'TagPage';
 				// Fall back to fronts for all other page types
 				else return 'Front';
 			};

dotcom-rendering/src/server/server.dev.ts

@@ -22,7 +22,7 @@ import {
 } from './handler.front.web';
 
 /** article URLs contain a part that looks like “2022/nov/25” */
-const ARTICLE_URL = /\/\d{4}\/[a-z]{3}\/\d{2}\//;
+const ARTICLE_URL = /(\/\d{4}\/[a-z]{3}\/\d{2}\/|\/[a-z-]+\/\d+$)/;
 /** fronts are a series of lowercase strings, dashes and forward slashes */
 const FRONT_URL = /^\/[a-z-/]+(?<!\.css)$/;
 /** This is imperfect, but covers *some* cases of tag pages, consider expanding in the future */