Skip to content

Commit 6785f7f

Browse files
committed
2 parents 4092fea + e25018e commit 6785f7f

File tree

8 files changed

+129
-4
lines changed

8 files changed

+129
-4
lines changed

CLAUDE.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# CLAUDE.md
2+
3+
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
4+
5+
## About This Site
6+
7+
This is a personal website built with Hugo static site generator, hosted on GitHub Pages at https://gusperez.com/. The site uses the Anatole theme and includes sections for blog posts, music, software projects, photography, art, and maker content.
8+
9+
## Development Commands
10+
11+
### Local Development
12+
- `hugo server` - Start local development server at http://localhost:1313/
13+
- `hugo server --buildDrafts` - Include draft posts in local development
14+
- `hugo server --buildFuture` - Include future-dated posts (already enabled via config)
15+
16+
### Content Management
17+
- `hugo new blog/YYYY-MM-DD_post-title.md` - Create new blog post in the blog section
18+
- `hugo new posts/post-title.md` - Create new post in the posts section (alternative)
19+
- `hugo new section/page-title.md` - Create new content in any section
20+
21+
### Building
22+
- `hugo` - Build the site for production (outputs to `/public`)
23+
- `hugo --minify` - Build with minification
24+
- `hugo --gc` - Build with garbage collection to clean up unused cache files
25+
26+
## Site Architecture
27+
28+
### Theme and Configuration
29+
- Uses the Anatole Hugo theme (github.com/lxndrblz/anatole v1.15.1)
30+
- Theme is imported as a Hugo module via `go.mod`
31+
- Main configuration in `config.toml`
32+
- Custom CSS styling in `assets/css/custom.css`
33+
- Custom fonts: Bricolage Grotesque and Carrois Gothic SC from Google Fonts
34+
- `buildFuture = true` allows posts with future dates to be published
35+
36+
### Content Structure
37+
- `content/blog/` - Blog posts with date-prefixed filenames (YYYY-MM-DD_title.md)
38+
- `content/software/` - Software project pages
39+
- `content/music/`, `content/photography/`, `content/art/`, `content/maker/` - Other content sections
40+
- Images for blog posts go in `content/blog/images/`
41+
- Static assets (favicons, profile images) in `static/`
42+
43+
### Layout Customization
44+
- Custom layouts in `layouts/` override theme defaults
45+
- Specialized layouts for software section in `layouts/software/`
46+
- Custom head partial in `layouts/partials/head.html` with font loading optimizations
47+
- Custom footer in `layouts/partials/footer.html`
48+
49+
### Styling Notes
50+
- Inline code styling uses pastelly dark-ish blue colors (#4a6fa5 light, #7eb3d3 dark)
51+
- Code backgrounds match page backgrounds (transparent)
52+
- Dark theme uses #181818 background
53+
- Custom mobile burger menu styling
54+
- Responsive layout with custom breakpoints for large screens (1921px+)
55+
56+
### Content Front Matter
57+
Blog posts typically include:
58+
```yaml
59+
title: "Post Title"
60+
date: 2025-08-31T11:32:51-07:00
61+
draft: false
62+
```
63+
64+
Images in blog posts should use absolute paths: `/blog/images/filename.png`

assets/css/custom.css

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,28 @@ p {
6464
color: #7eace4;
6565
}
6666

67+
/* Inline code styling */
68+
code {
69+
background-color: #eee;
70+
padding: 0.2em 0.4em;
71+
border-radius: 3px;
72+
font-size: 0.9em;
73+
color: #4a6fa5;
74+
}
75+
76+
.theme--dark code {
77+
background-color: #292929;
78+
color: #7eb3d3;
79+
}
80+
81+
/* Override code block backgrounds */
82+
.theme--light .post__content pre {
83+
background-color: #eee;
84+
}
85+
/* Override code block backgrounds */
86+
.theme--dark .post__content pre {
87+
background-color: #292929;
88+
}
6789
/* Mobile burger more prominent */
6890
a.navbar-burger {
6991
height: 4.25rem;
@@ -127,4 +149,5 @@ a.navbar-burger {
127149
.wrapper__sidebar {
128150
width:calc(calc(1 - .7) * 80%)
129151
}
130-
}
152+
}
153+

config.toml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ languageCode = 'en-us'
33
title = 'Gus Perez'
44
include = ["/.well-known"]
55
pluralizeListTitles = false
6+
buildFuture = true
67

78
[params]
89
title = "Gus Perez"

content/blog/2024-11-02_glen-hansard-leave-tab-chords.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ This is one I guess I missed posting on Ultimate Guitar. Sharing it here in the
88

99
### Verse Chords:
1010
```
11-
E5 C#/Dbm9 Badd11 Aadd9
11+
E5 C#/Dbm9 Badd11 Aadd9
1212
E --0---0-------0------0------
1313
B --0---0-------0------0------
1414
G --9---8-------8------6------
@@ -18,7 +18,7 @@ E --0---9-------7------5------
1818
```
1919
### Chorus and Outro Chords:
2020
```
21-
C#m/E B5 A5 F#11 E G#
21+
C#m/E B5 A5 F#11 E G#
2222
E --0-----0---0---0-----0---4--
2323
B --5-----0---0---0-----0---4--
2424
G --6-----4---2---3-----1---5--
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: "Remapping Copilot key to END key (and others)"
3+
date: 2025-08-31T11:32:51-07:00
4+
draft: false
5+
---
6+
This was a bit of a frustrating journey, so writing it up here in case it helps others running into the same frustration.
7+
8+
I've become accustomed to remapping the two keys immediately to the right of the spacebar on my keyboards to `HOME` and `END` (in that order). Usually that means mapping the `Right ALT` key to `HOME` and the Windows Menu (or right-click context menu) key to `END`. However, my two newer laptops replaced the latter button and introduced a new `Copilot` button. It turns out that one hasn't been as straightforward to remap, but I did finally find a way.
9+
10+
The only way I've gotten it to work so far is to use [Microsoft PowerToys](https://learn.microsoft.com/en-us/windows/powertoys/install#install-with-windows-executable-file-from-github). Once installed, follow these instructions to get it set up:
11+
12+
1. Open up PowerToys settings
13+
2. Expand the `Input / Output` section
14+
3. Select the `Keyboard Manager` tool
15+
4. Turn on the `Enable Keyboard Manager` option
16+
5. Click on `Remap a shortcut` which will open a new window
17+
6. Click on the `+ Add shortcut remapping`
18+
7. Click the pencil icon on the left side
19+
8. Press the `Copilot` key on your keyboard
20+
9. Click on the `OK` button to go back to the `Remap shortcuts` screen
21+
10. Click on the pencil icon in the center of the window (under the `To:` heading)
22+
11. Press the `END` key on your keyboard (including any additional keys you need such as Fn on many laptops)
23+
12. Click on the `OK` button to go back again
24+
13. Click on the `OK` button in the top right of the `Remap shortcuts` window
25+
14. You're likely to get a warning message of some kind, but it should be okay to ignore (e.g., something about the `F23` key not being mapped)
26+
27+
You should be good now. In my case, I also remapped the Right ALT key to HOME. That one can be done by just using the `Remap a key` feature, so it's a little bit simpler. In the end, you'll end up with the following:
28+
29+
![PowerToys screenshot after setting up the two remappings.](/blog/images/2025-08-31_powertoys_1.png)
30+
31+
## More about the journey
32+
You'll notice in the screenshot that the Copilot key maps to `Left Windows + Left Shift + F23` key combo. I first tried to just update my AutoHotkey script that I use on all of my PCs to map that combo to End by simply adding a line such as `#<+F23::END` to it. However, it seems a SHIFT key would still keep getting through which meant instead of just an `END`, I'd get a `SHIFT`+`END` combination. That means that Windows would *select* the text between where the caret started off and the end of that line instead of simply moving the caret to the end of the line.
33+
34+
That led me to see if PowerToys would work. Less than ideal as it's nicer to keep all of this kind of config consolidated in one simple script I already have working on all of my machines, but still worth trying. I tried using the `Remap a key` support to map it (just like I described doing for the `RALT`->`HOME` key above), and it resulted in the same selection behavior I ran into with AutoHotkey.
35+
36+
Somewhere along the way, I decided to try using the other `Remap a shortcut` feature instead. And it worked beautifully. Unfortunately, this took me several hours across an evening, a night's sleep, and the following morning to discover. I was determined to figure out a way to make it work even picturing myself having to write some lower level Win32 code (which has been ages since I did that) as I really couldn't see how this would be impossible to do. I still may end up spending some more time on seeing if I can get AutoHotkey to work for this case, but we'll see. For now, I'm just going to enjoy this little victory that would have driven me nuts for a long time to come.
52.1 KB
Loading
56.3 KB
Loading

layouts/partials/head.html

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,8 @@
127127
{{ $url := printf "%s" "&display=swap" | printf "%s%s" $fontParam | printf "%s%s" $baseUrl | printf "%s" }}
128128
<link rel="preconnect" href="https://fonts.googleapis.com" />
129129
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
130-
<link href="{{ $url }}" rel="stylesheet" />
130+
<link rel="preload" as="style" href="{{ $url }}" />
131+
<link href="{{ $url }}" rel="stylesheet" media="print" onload="this.media='all'" />
131132
{{- end -}}
132133

133134
<!-- Favicons -->

0 commit comments

Comments
 (0)