Style updates on footer

Author: webstackdev

.alexrc

@@ -0,0 +1,5 @@
+{
+  "allow": [
+    "hostesses-hosts"
+  ]
+}

@types/speech-recognition.d.ts

@@ -106,8 +106,33 @@ Maybe change the "ready..." in the hero to "get in touch..."
 
 ## Search Box
 
+- Show article titles only in drop-down search result box, and dedupe results
+
 Title box - need to squish to 75% and have it absolute in place as you scroll down, go back to 100% when you scroll back up
 
+## ToolTips
+
+Need a tooltip component for consistency. List to add tooltips to:
+
+- Themepicker button
+- Search button
+- Abbreviations in markdown
+- "Report a Bug" in footer
+- RSS feed icon in footer
+
+## Support Pages to Style
+
+- /offline
+- /404
+- Bug reporter modal
+- /search
+- /consent
+- /privacy
+- /tags/[tag]
+- /about
+- /contact
+- /
+
 ## Image generation models
 
 - dall-e (OpenAI)
@@ -135,6 +160,3 @@ We have generated detailed outlines for each of the MDX proposed articles we hav
 Act as a principal software engineer. Your goal is to write a detailed technical article based on the provided outline. Context: The target audience is Senior DevOps and infrastructure Engineers. The tone should be authoritative, professional, and concise, avoiding fluff or filler words. Think step-by-step before writing to improve the accuracy of technical explanations. Use a friendly first-person voice. Anything that reads like generic marketing copy is not what we want but we still want the effect of being "real" and approachable - try not to sound like technical documentation. We want to show empathy for our readers.
 
 Let's work through each article section by section based on the H2 headers in the outline. If the section looks good as-is, I'll just type "ok" so you know to continue to the next section.
-
-
-There are a number of properties in that are hard-coding values instead of using the css variable values we have defined in src/styles, like