Skip to content

Commit 672f776

Browse files
devalogdevalog
committed
fix css
1 parent a976f67 commit 672f776

File tree

4 files changed

+100
-607
lines changed

4 files changed

+100
-607
lines changed

‎_site/assets/main.css‎

Lines changed: 10 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎_site/assets/main.scss‎

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
---
3+
4+
@import "minima";
5+
6+
/* Override the site header border */
7+
.site-header {
8+
border-top: none !important;
9+
}
10+
11+
img {
12+
border: 1px solid #ddd;
13+
border-radius: 4px;
14+
padding: 5px;
15+
display: block;
16+
margin-left: auto;
17+
margin-right: auto;
18+
max-width: 600px;
19+
height: auto;
20+
margin: 20px auto;
21+
}
22+
23+
.smaller-image {
24+
max-width: 300px;
25+
height: auto;
26+
}
27+
28+
/* New styles for side-by-side images */
29+
.image-container {
30+
display: flex;
31+
justify-content: center;
32+
gap: 20px; /* Space between images */
33+
margin: 20px 0; /* Vertical spacing around the container */
34+
}
35+
36+
.side-by-side-image {
37+
max-width: 200px;
38+
height: auto; /* Make images smaller to fit side by side */
39+
margin: 0; /* Remove the margin we set on regular images */
40+
}
41+
42+
/* Spacing after posts */
43+
.post-list article {
44+
margin-bottom: 2em;
45+
}
46+
47+
/* TOC styling */
48+
.table-of-contents {
49+
background: #f8f9fa;
50+
border: 1px solid #e9ecef;
51+
border-radius: 6px;
52+
padding: 1.5rem;
53+
margin-bottom: 2rem;
54+
}
55+
56+
.table-of-contents h3 {
57+
margin-top: 0;
58+
margin-bottom: 1rem;
59+
font-size: 1.1rem;
60+
color: #6c757d;
61+
font-style: italic;
62+
}
63+
64+
.table-of-contents ul {
65+
margin-bottom: 0;
66+
}
67+
68+
/* Indent nested heading levels */
69+
.toc-level-2 {
70+
/* H2 headings - no indent */
71+
}
72+
73+
.toc-level-3 {
74+
margin-left: 1.5rem;
75+
list-style-type: circle;
76+
}
77+
78+
.toc-level-4 {
79+
margin-left: 3rem;
80+
list-style-type: square;
81+
}
82+
83+
.toc-level-5 {
84+
margin-left: 4.5rem;
85+
}
86+
87+
.toc-level-6 {
88+
margin-left: 6rem;
89+
}

‎_site/feed.xml‎

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,4 @@
1-
<<<<<<< HEAD
2-
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="http://localhost:4000/feed.xml" rel="self" type="application/atom+xml" /><link href="http://localhost:4000/" rel="alternate" type="text/html" /><updated>2025-06-04T20:03:20-04:00</updated><id>http://localhost:4000/feed.xml</id><title type="html">Devin Logan, Technical Writer and Editor</title><subtitle></subtitle><author><name> </name></author><entry><title type="html">Getting into technical writing: a primer</title><link href="http://localhost:4000/2025/05/23/primer.html" rel="alternate" type="text/html" title="Getting into technical writing: a primer" /><published>2025-05-23T00:00:00-04:00</published><updated>2025-05-23T00:00:00-04:00</updated><id>http://localhost:4000/2025/05/23/primer</id><content type="html" xml:base="http://localhost:4000/2025/05/23/primer.html"><![CDATA[<p>Over the past few years I’ve talked to a number of people who are interested in getting into the technical writing field. After years of meaning to do this, I finally took some time to write up the thoughts and resources I typically share with people looking to get into the field. This is far from a comprehensive guide and notably doesn’t include much specific resume or cover letter advice.</p>
3-
=======
4-
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="http://localhost:4000/feed.xml" rel="self" type="application/atom+xml" /><link href="http://localhost:4000/" rel="alternate" type="text/html" /><updated>2025-06-04T16:38:30-04:00</updated><id>http://localhost:4000/feed.xml</id><title type="html">Devin Logan, Technical Writer and Editor</title><subtitle></subtitle><author><name> </name></author><entry><title type="html">Getting into technical writing: a primer</title><link href="http://localhost:4000/2025/05/23/primer.html" rel="alternate" type="text/html" title="Getting into technical writing: a primer" /><published>2025-05-23T00:00:00-04:00</published><updated>2025-05-23T00:00:00-04:00</updated><id>http://localhost:4000/2025/05/23/primer</id><content type="html" xml:base="http://localhost:4000/2025/05/23/primer.html"><![CDATA[<p>Over the past few years I’ve talked to a number of people who are interested in getting into the technical writing field. After years of meaning to do this, I finally took some time to write up the thoughts and resources I typically share with people looking to get into the field. This is far from a comprehensive guide and notably doesn’t include much specific resume or cover letter advice.</p>
5-
>>>>>>> c9b72b6622ce6a73df7352dedc5ccb11b7fa2d47
1+
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="http://localhost:4000/feed.xml" rel="self" type="application/atom+xml" /><link href="http://localhost:4000/" rel="alternate" type="text/html" /><updated>2025-06-04T20:13:25-04:00</updated><id>http://localhost:4000/feed.xml</id><title type="html">Devin Logan, Technical Writer and Editor</title><subtitle></subtitle><author><name> </name></author><entry><title type="html">Getting into technical writing: a primer</title><link href="http://localhost:4000/2025/05/23/primer.html" rel="alternate" type="text/html" title="Getting into technical writing: a primer" /><published>2025-05-23T00:00:00-04:00</published><updated>2025-05-23T00:00:00-04:00</updated><id>http://localhost:4000/2025/05/23/primer</id><content type="html" xml:base="http://localhost:4000/2025/05/23/primer.html"><![CDATA[<p>Over the past few years I’ve talked to a number of people who are interested in getting into the technical writing field. After years of meaning to do this, I finally took some time to write up the thoughts and resources I typically share with people looking to get into the field. This is far from a comprehensive guide and notably doesn’t include much specific resume or cover letter advice.</p>
62

73
<p>I worked as a technical writer at Google for almost 7 years. (And wrote <a href="https://blog.google/inside-google/life-at-google/sowhat-does-technical-writer-actually-do/">this blog post</a> for Google’s The Keyword back in 2021, which captured my own journey into technical writing.) During that time, I interviewed a lot of candidates, including some people who were switching careers. Now, I’m a freelance technical writer and have spent a lot of time refining my resume and applying to jobs.</p>
84

0 commit comments

Comments
 (0)