-
Notifications
You must be signed in to change notification settings - Fork 1
/
rss.xml
92 lines (92 loc) · 4.14 KB
/
rss.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>technicalwriting.dev</title>
<link>https://technicalwriting.dev</link>
<description>
A blog about technical writing by Kayce Basques.
</description>
<language>en-us</language>
<pubDate>Mon, 21 Oct 2024 09:09:03 -0700</pubDate>
<atom:link href="https://technicalwriting.dev/rss.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Embeddings are underrated</title>
<link>https://technicalwriting.dev/data/embeddings.html</link>
<description>
Machine learning (ML) has the potential to advance the state of the art
in technical writing. No, I'm not talking about text generation models.
The ML technology that might end up having the biggest impact on technical
writing is embeddings. What embeddings offer to technical writers is the
ability to discover connections between texts at previously impossible scales.
</description>
<pubDate>Mon, 21 Oct 2024 09:09:03 -0700</pubDate>
<guid>https://technicalwriting.dev/data/embeddings.html</guid>
</item>
<item>
<title>Exploring the intertwingularity of a docs site</title>
<link>https://technicalwriting.dev/data/intertwingularity.html</link>
<description>
I’m building a web crawler so that I can track how pages in my docs
site link to each other and to the outside web more broadly. If a lot of my docs pages link to
some particular page, then that page is probably important. PageRank Lite, basically, except
with much more focus on intra-site backlinks.
</description>
<pubDate>Wed, 16 Oct 2024 22:02:44 -0700</pubDate>
<guid>https://technicalwriting.dev/data/intertwingularity.html</guid>
</item>
<item>
<title>Focus on decisions, not tasks</title>
<link>https://technicalwriting.dev/strategy/decisions.html</link>
<description>
A quote from Every Page Is Page One that has deeply changed how I
approach technical writing.
</description>
<pubDate>Tue, 15 Oct 2024 16:16:16 -0700</pubDate>
<guid>https://technicalwriting.dev/strategy/decisions.html</guid>
</item>
<item>
<title>Development log: Migrating pigweed.dev to Bazel</title>
<link>https://technicalwriting.dev/build/bazel.html</link>
<description>
I have been tasked with the fascinating and somewhat-overwhelming
project of migrating pigweed.dev's build system from GN to Bazel.
These are my notes on the project.
</description>
<pubDate>Wed, 25 Sep 2024 11:50:34 -0700</pubDate>
<guid>https://technicalwriting.dev/build/bazel.html</guid>
</item>
<item>
<title>You can deeplink to a specific PDF page</title>
<link>https://technicalwriting.dev/www/pdf.html</link>
<description>
Just append #page=X to your URL, where X is the page you
want to deeplink to.
</description>
<pubDate>Thu, 11 Jul 2024 09:01:07 -0700</pubDate>
<guid>https://technicalwriting.dev/www/pdf.html</guid>
</item>
<item>
<title>Please support “skip to main content” on your docs site</title>
<link>https://technicalwriting.dev/a11y/skip.html</link>
<description>
I'm trying to become proficient at keyboard-only navigation and
have learned that a lot of docs sites aren't friendly to people
who rely on Tab...
</description>
<pubDate>Sun, 2 Jun 2024 17:48:00 -0700</pubDate>
<guid>https://technicalwriting.dev/a11y/skip.html</guid>
</item>
<item>
<title>Field research: search boxes</title>
<link>https://technicalwriting.dev/ux/searchboxes.html</link>
<description>
Where should I put the search box on my documentation site?
What text should I put inside the search box? What should
happen when I type stuff into the search box? What should the
search results page look like?
</description>
<pubDate>Mon, 19 Feb 2024 14:37:03 -0700</pubDate>
<guid>https://technicalwriting.dev/ux/searchboxes.html</guid>
</item>
</channel>
</rss>