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 abdffa0
Browse filesBrowse the repository at this point in the historyBrowse files
Remove underline from footnote superscript, add local time zone and timeZone prop to Time component, spacing in Testimonials component and testimonials integration and that checks length
Copy file name to clipboardExpand all lines: _TODO.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,3 +197,18 @@ We have generated detailed outlines for each of the MDX proposed articles we hav
197
197
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.
198
198
199
199
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.
200
+
201
+
## Move hard-coded options from integrations to astro.config.ts
202
+
203
+
### CTA validator
204
+
205
+
Let's also refactor the CtaValidator integration to allow passing in options from astro.config.ts instead of hard-coding things in the integration. We should be able to:
206
+
207
+
- pass in the required CallToActions in the src/components/CallToAction as an array
208
+
- pass in the debug flag
209
+
210
+
I think we can remove the additionalPatterns option, it appears unused but need to check.
211
+
212
+
I added a new folder in the CallToAction component folder that won't be required for articles.
Copy file name to clipboardExpand all lines: src/content/articles/demo/index.mdx
+59-19Lines changed: 59 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,24 +13,6 @@ import Demo from '@components/Test/Demo.mdx'
13
13
14
14
## Components (looping)
15
15
16
-
### Social Sharing Component
17
-
18
-
Add social sharing buttons for the article. The social image is auto-generated, and can be passed as an optional param to override the generated version.
19
-
20
-
```markdown
21
-
<Shares
22
-
title="Demo Page"
23
-
description="This is just a demo page to show how things work on the site"
24
-
url="/articles/demo"
25
-
/>
26
-
```
27
-
28
-
<Shares
29
-
title="Demo Page"
30
-
description="This is just a demo page to show how things work on the site"
31
-
url="/articles/demo"
32
-
/>
33
-
34
16
### Testimonials Component
35
17
36
18
Display customer feedback and testimonials:
@@ -49,6 +31,42 @@ Let's go to the disco <Time datetime="2026-01-01T00:00:00.000Z" />.
49
31
50
32
Let's go to the disco <Timedatetime="2026-01-01T00:00:00.000Z" />.
51
33
34
+
```markdown
35
+
This demonstrates `format="datetime"` explicitly (same as the default): <Timeformat="datetime"datetime="2026-01-01T00:00:00.000Z" />.
36
+
```
37
+
38
+
This demonstrates `format="datetime"` explicitly (same as the default): <Timeformat="datetime"datetime="2026-01-01T00:00:00.000Z" />.
39
+
40
+
```markdown
41
+
This demonstrates `formatStyle="short"` for a compact date: <Timeformat="datetime"formatStyle="short"datetime="2026-01-01T00:00:00.000Z" />.
42
+
```
43
+
44
+
This demonstrates `formatStyle="short"` for a compact date: <Timeformat="datetime"formatStyle="short"datetime="2026-01-01T00:00:00.000Z" />.
45
+
46
+
```markdown
47
+
This demonstrates showing a time and time zone name: <Timeformat="datetime"hour="2-digit"minute="2-digit"datetime="2026-01-01T00:00:00.000Z" />.
48
+
```
49
+
50
+
This demostrates showing a time that should adjust to user's local timezone: <Timeformat="datetime"hour="2-digit"minute="2-digit"datetime="2026-01-01T00:00:00.000Z" />.
51
+
52
+
```markdown
53
+
This demonstrates showing a time and time zone name: <Timeformat="datetime"hour="2-digit"minute="2-digit"timeZoneName="short"datetime="2026-01-01T00:00:00.000Z" />.
54
+
```
55
+
56
+
This demostrates showing a time and time zone name: <Timeformat="datetime"hour="2-digit"minute="2-digit"timeZoneName="short"datetime="2026-01-01T00:00:00.000Z" />.
57
+
58
+
```markdown
59
+
This demonstrates `format="relative"` with `tense="past"` and `precision="day"`: <Timeformat="relative"tense="past"precision="day"datetime="2020-01-01T00:00:00Z" />.
60
+
```
61
+
62
+
This demonstrates `format="relative"` with `tense="past"` and `precision="day"`: <Timeformat="relative"tense="past"precision="day"datetime="2020-01-01T00:00:00Z" />.
63
+
64
+
```markdown
65
+
This demonstrates `now` (uses the current time at render): <Timeformat="datetime"now />.
66
+
```
67
+
68
+
This demonstrates `now` (uses the current time at render): <Timeformat="datetime"now />.
69
+
52
70
## GFM
53
71
54
72
### Footnote
@@ -85,7 +103,11 @@ The references can be anywhere in the document, before or after their use:
85
103
86
104
### Strikethrough
87
105
88
-
`~one~` or `~~two~~` tildes: ~one~~~two~~
106
+
`~~two~~` tildes: ~~two~~
107
+
108
+
### Subscript
109
+
110
+
`~one~` tilde: Subscript~one~
89
111
90
112
### Table
91
113
@@ -1240,3 +1262,21 @@ Use SVG sprites for icons throughout your content:
1240
1262
Encourage readers to subscribe to your newsletter:
1241
1263
1242
1264
<Newsletter />
1265
+
1266
+
### Social Sharing Component
1267
+
1268
+
Add social sharing buttons for the article. The social image is auto-generated, and can be passed as an optional param to override the generated version.
1269
+
1270
+
```markdown
1271
+
<Shares
1272
+
title="Demo Page"
1273
+
description="This is just a demo page to show how things work on the site"
1274
+
url="/articles/demo"
1275
+
/>
1276
+
```
1277
+
1278
+
<Shares
1279
+
title="Demo Page"
1280
+
description="This is just a demo page to show how things work on the site"
Copy file name to clipboardExpand all lines: src/content/testimonials/english-first/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,4 +5,4 @@ publishDate: 2021-03-31
5
5
tags: []
6
6
---
7
7
8
-
We have had a web presence since 2006. When advancements in web technology passed our skill levels we hired various developers, but there was always a certain amount of monitoring and adjustment required to achieve the proper result. Working with Kevin has been a refreshing change. Kevin is an authority on web development and is clearly in the upper percentile in terms of developer qualifications. Kevin's invaluable suggestions and improvements helped create a stable, cross platform site.
8
+
We have had a web presence since 2006. When advancements in web technology passed our skill levels we hired various developers, but there was always a certain amount of monitoring and adjustment required to achieve the proper result. Working with Kevin has been a refreshing change.
0 commit comments