You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 361a05e
Browse filesBrowse the repository at this point in the historyBrowse files
We have E2E errors again testimonials slide on mobile chrome and safari. I think the problem is that we are pausing carousels when part of the carousel is outside of the viewport, and the testimonials are too large to display on mobile without being off viewport.
@@ -52,10 +45,6 @@ We have E2E errors again testimonials slide on mobile chrome and safari. I think
52
45
53
46
We should start the mock containers with the dev server instead of with Playwright so that they're useable in a dev environment.
54
47
55
-
## Add Tooltip component
56
-
57
-
We need a Tooltip component. It should apply to the existing tooltips on the theme picker palettes.
58
-
59
48
## Improve print layout by hiding header and footer for articles, add tracking
60
49
61
50
```typescript
@@ -114,8 +103,14 @@ Link to the second-order category from the "Skills/Technologies Preview" icons o
114
103
115
104
- Show article titles only in drop-down search result box, and dedupe results
116
105
106
+
## Header
107
+
117
108
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
118
109
110
+
## Themepicker
111
+
112
+
Need to tweak 1px border for non-active theme cards
113
+
119
114
## ToolTips
120
115
121
116
Need a tooltip component for consistency. List to add tooltips to:
@@ -182,13 +177,3 @@ We have generated detailed outlines for each of the MDX proposed articles we hav
182
177
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.
183
178
184
179
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.
185
-
186
-
## Link Check
187
-
188
-
Should we disable external link checking? Or maybe require allow-listing them?
189
-
190
-
## Carousel
191
-
192
-
- On hover when it rises, the corners get cut off and squared. It should raise to a higher index and move up.
193
-
- The focus outline should just replace the existing border with the highlight border.
194
-
- The card background isn't distinct enough - maybe it needs shadow all the way around, or a darker color.
0 commit comments