Back to basic HTML
This commit is contained in:
parent
cdfcdfd2d9
commit
90723b7362
30 changed files with 158 additions and 801 deletions
3
.gitignore
vendored
3
.gitignore
vendored
|
|
@ -1,3 +0,0 @@
|
|||
__pycache__
|
||||
.venv
|
||||
dist
|
||||
4
atom.xml
4
atom.xml
|
|
@ -1,4 +0,0 @@
|
|||
---
|
||||
template: atom
|
||||
---
|
||||
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
---
|
||||
template: gemlog
|
||||
---
|
||||
14
index.gmi
14
index.gmi
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
template: home
|
||||
---
|
||||
Hi 👋, I'm Erick!
|
||||
|
||||
I live in the U.S. with my wife, Lizzy, and our dogter, Masha. I'm fluent in both English and Spanish.
|
||||
|
||||
I work as a Software Engineer at Bloomberg, where I'm passionate about software architecture, automation, and enhancing the developer experience.
|
||||
|
||||
Giving back to the community is something I truly enjoy. I do this through mentorships, conducting mock interviews, and hosting knowledge-sharing sessions to pass on what I've learned throughout my career.
|
||||
|
||||
In my free time, I love watching movies and TV shows, listening to audiobooks and music, playing video games with Lizzy, and upgrading our home with smart automation.
|
||||
|
||||
My pronouns are he/him/his.
|
||||
47
index.html
Normal file
47
index.html
Normal file
|
|
@ -0,0 +1,47 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
||||
<link rel="stylesheet" href="styles.css" />
|
||||
<title>Erick Ruiz de Chavez</title>
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<img
|
||||
class="panda"
|
||||
src="panda.webp"
|
||||
alt="Generated Image of an anthropomorphic Panda wearing a sweater and jeans, sitting on a couch, using a laptop."
|
||||
/>
|
||||
|
||||
<nav>
|
||||
<a href="https://gts.erick.sh/@erick" rel="me noreferrer" target="_blank"> Fediverse </a>
|
||||
<a href="https://code.erick.sh" rel="me noreferrer" target="_blank"> Source Code </a>
|
||||
<a href="https://github.com/eruizdechavez" rel="me noreferrer" target="_blank"> GitHub </a>
|
||||
<a href="https://linkedin.com/in/erickruizdechavez" rel="me noreferrer" target="_blank"> LinkedIn </a>
|
||||
</nav>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
<p>Hi 👋, I'm Erick!</p>
|
||||
<p>
|
||||
I live in the U.S. with my wife, Lizzy, and our dogter, Masha. I'm fluent in both English and Spanish.
|
||||
</p>
|
||||
<p>
|
||||
I work as a Software Engineer at Bloomberg, where I'm passionate about software architecture,
|
||||
automation, and enhancing the developer experience.
|
||||
</p>
|
||||
<p>
|
||||
Giving back to the community is something I truly enjoy. I do this through mentorships, conducting mock
|
||||
interviews, and hosting knowledge-sharing sessions to pass on what I've learned throughout my career.
|
||||
</p>
|
||||
<p>
|
||||
In my free time, I love watching movies and TV shows, listening to audiobooks and music, playing video
|
||||
games with Lizzy, and upgrading our home with smart automation.
|
||||
</p>
|
||||
<p>My pronouns are he/him/his.</p>
|
||||
</main>
|
||||
|
||||
<footer>© 2025 Erick Ruiz de Chavez</footer>
|
||||
</body>
|
||||
</html>
|
||||
BIN
panda.webp
Normal file
BIN
panda.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.3 KiB |
|
|
@ -1,11 +0,0 @@
|
|||
---
|
||||
title: 'Regenerating My Blog: A Fresh Start'
|
||||
date: 2024-12-22 00:45 +0000
|
||||
---
|
||||
Hey there! Looks like I'm back to writing after some time away. Over the years, I've started many blogs and personal sites, experimenting with different technologies and styles. And here I am again, excited to share my thoughts with you.
|
||||
|
||||
Even though I've never considered myself a great writer, the idea of having a blog to share my thoughts, experiences, and ideas has always been in the back of my mind. This time, I'm keeping it simple—sharing small bits whenever inspiration strikes.
|
||||
|
||||
The biggest difference this time is how I'm publishing the site and blog. In the past, I've used various tools like WordPress or Jekyll. This time, I'm back on Jekyll, which somehow feels intuitive and easy to use, even with zero Ruby experience. However, there's one key change: I'm also sharing and publishing the same content as a Gemlog—a blog hosted and shared using the Gemini Protocol. There are plenty of great articles about Gemini out there, and I might write about it briefly in a future post.
|
||||
|
||||
Feel free to use any of my social links to connect or share your thoughts. I'm looking forward to hearing from you and sharing this renewed journey. Thanks for stopping by!
|
||||
|
|
@ -1,100 +0,0 @@
|
|||
---
|
||||
title: 'Energy Shields at Minimum: Automating Laptop Power Mode'
|
||||
date: 2024-12-29 12:35 +0000
|
||||
---
|
||||
I love automation—not just home automation but anything that simplifies my life. For example, I use a Shortcut on my iPhone that automatically turns on Low Power Mode when the battery drops below a certain percentage.
|
||||
|
||||
This morning, while working on my laptop, I realized that macOS allows Low Power Mode to be set to "always on" when on battery power, but it doesn't provide an option like "only when the battery level is below X%." Naturally, I decided to create a script to achieve the same functionality on my laptop that I already enjoy on my phone.
|
||||
|
||||
After a quick search, I found the commands needed to set the power mode and check the battery level. Another search revealed that macOS supports allowing specific users to execute scripts with sudo privileges without needing a password. 💥 A few minutes later, I had my laptop automatically enabling or disabling Low Power Mode based on the battery percentage. 🤓
|
||||
|
||||
Here's how you can achieve the same result.
|
||||
|
||||
### Step 1: Create the Script
|
||||
|
||||
First, create a script to check the current battery level and set the Low Power Mode accordingly. I like to save my scripts in `$HOME/bin`. On my laptop, that's `/Users/Erick/bin`. So, I created a script at `/Users/Erick/bin/low-power-mode` with the following contents:
|
||||
|
||||
```shell
|
||||
#!/usr/bin/env bash
|
||||
|
||||
# Get the current battery level
|
||||
_level=$(pmset -g batt | grep "InternalBattery" | awk -F '[\t;]' '{print $2}')
|
||||
|
||||
# Remove "%" symbol from the battery level
|
||||
_level=${_level/\%/}
|
||||
|
||||
# Get the current Low Power Mode state
|
||||
_current_mode=$(pmset -g | grep lowpowermode | awk '{print $2}')
|
||||
|
||||
# Initialize the new mode variable
|
||||
_new_mode=
|
||||
|
||||
# Enable Low Power Mode if the battery level is <= 10%
|
||||
if [ $_level -le 10 ]; then
|
||||
_new_mode=1
|
||||
|
||||
# Disable Low Power Mode if the battery level is >= 25%
|
||||
elif [ $_level -ge 25 ]; then
|
||||
_new_mode=0
|
||||
|
||||
fi
|
||||
|
||||
# Update the Low Power Mode state if it differs from the current state
|
||||
if [ "$_current_mode" != "$_new_mode" ]; then
|
||||
pmset -a lowpowermode $_new_mode
|
||||
fi
|
||||
```
|
||||
|
||||
### Step 2: Make the Script Executable
|
||||
|
||||
Make your script executable with the following command:
|
||||
|
||||
```shell
|
||||
chmod +x /Users/Erick/bin/low-power-mode
|
||||
```
|
||||
|
||||
### Step 3: Allow Passwordless Execution
|
||||
|
||||
The `pmset` command requires root privileges, and since the script will run automatically, it needs to execute without prompting for a password. To achieve this, update the sudoers file:
|
||||
|
||||
1. Open the sudoers file with the following command:
|
||||
|
||||
```shell
|
||||
sudo visudo
|
||||
```
|
||||
|
||||
2. Find a line near the end of the file that looks like this:
|
||||
|
||||
```
|
||||
%admin ALL = (ALL) ALL
|
||||
```
|
||||
|
||||
3. Add the following line immediately after it:
|
||||
|
||||
```
|
||||
%admin ALL = (ALL) NOPASSWD:/Users/Erick/bin/low-power-mode
|
||||
```
|
||||
|
||||
4. Save and exit (in Vim, use :x⏎).
|
||||
|
||||
### Step 4: Automate with Cron
|
||||
|
||||
To run the script automatically, schedule it using cron:
|
||||
|
||||
1. Open your crontab file:
|
||||
|
||||
```shell
|
||||
crontab -e
|
||||
```
|
||||
|
||||
2. Add the following line to run the script every minute:
|
||||
|
||||
```
|
||||
* * * * * sudo /Users/Erick/bin/low-power-mode
|
||||
```
|
||||
|
||||
3. Save and exit (in Vim, use :x⏎).
|
||||
|
||||
And That's It!
|
||||
|
||||
Now, your laptop will automatically check the battery level every minute and adjust the power mode accordingly. Whether you're a beginner or a seasoned scriptwriter, this approach ensures your laptop's energy efficiency is always optimal.
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
---
|
||||
date: 2025-01-08 11:01 +0000
|
||||
title: 'Prime Directive: Minimalism and Efficiency with Gemini Protocol'
|
||||
---
|
||||
Just a couple of weeks ago, I restarted my site (the one you are reading right now) with the goal of maintaining a minimalist approach—focusing on content rather than flashy styles or colorful themes. For the first time, I also decided to implement dual hosting, making the site available via HTTPS and the Gemini protocol.
|
||||
|
||||
An idea that had been floating around in my mind for a few days was that, since the HTTPS version of the site was already quite basic in terms of styles and layout, why not serve the same content I use for Gemini? Yesterday morning, this idea came to life thanks to a small proxy tool called Kineto [1]. This tool acts as a proxy, allowing a single Gemini capsule to be served to regular web browsers.
|
||||
|
||||
After making a few tweaks to my code and deployment, I was able to completely remove Jekyll and keep only the minimal components. Additionally, since the Gemtext [2] format is already simple and easy to write, there was no need to transform Markdown to Gemtext. I refactored all my content files from Markdown to Gemtext, which consisted only of changing their file extensions.
|
||||
|
||||
The capsule generator is still quite basic (honestly, I'd even call it a pre-alpha version). I still need to decide whether to continue using my own code or switch to a more formal capsule generator. For those who are curious, the source code for both my site and the generator can be found in my Forgejo repo [3].
|
||||
|
||||
=> https://sr.ht/~sircmpwn/kineto/ [1]: Kineto
|
||||
=> gemini://geminiprotocol.net/docs/gemtext.gmi [2]: A quick introduction to "gemtext" markup
|
||||
=> https://code.palmiers.xyz/erick/erick.is [3]: erick/erick.is
|
||||
|
|
@ -1,23 +0,0 @@
|
|||
---
|
||||
date: 2025-01-12 14:01 +0000
|
||||
title: "New Capsule Generator: \U0001F48E Stargem"
|
||||
---
|
||||
For the last couple of days, I've been working on polishing and improving a collection of Python 🐍 scripts I've been using to publish my site. After getting all the basics working as I wanted, it was time to refactor them into a proper command-line tool with subcommands, flags, and more. The result is 💎 Stargem, a “Static Capsule Generator.” While I still need to polish a few details and document it properly, it's more than ready for personal use. I am planning on publishing to PyPi once I get it properly documented and the code is in a better shape.
|
||||
|
||||
Stargem borrows some ideas from tools like Jekyll and Hugo (I think). It supports a handful of commands for tasks I frequently perform: new, draft, publish, unpublish, and build.
|
||||
|
||||
* new: Generates a new Capsule with all the expected folders, files, and a few examples.
|
||||
* draft: Creates a new draft in the drafts folder. I can set the title as a command-line argument or, if missing, as an interactive prompt.
|
||||
* publish: Publishes a draft into the posts folder. This uses the current date and time to rename the file and includes it in the front matter.
|
||||
* unpublish: Moves a post back to the drafts folder and removes the published date from both the file name and the front matter.
|
||||
* build: Generates the site into a dist folder.
|
||||
|
||||
If you're curious about the site structure, you can check out this site's repo at:
|
||||
|
||||
=> https://code.palmiers.xyz/erick/erick.is
|
||||
|
||||
If you'd like to follow my progress on Stargem (still under development), you can visit:
|
||||
|
||||
=> https://code.palmiers.xyz/erick/stargem
|
||||
|
||||
As usual, feel free to reach out using any of my contact links. 😉
|
||||
|
|
@ -1,78 +0,0 @@
|
|||
---
|
||||
date: 2025-01-23 11:01 +0000
|
||||
title: Blog Questions Challenge 2025
|
||||
---
|
||||
While reading Cosmos[1], I found an entry[2] about a "Blog Questions Challenge 2025." At the end, the author nominated anyone who read their post to participate. Since I thought it would be interesting to answer those questions, here are my answers.
|
||||
|
||||
|
||||
### Why did you start blogging in the first place?
|
||||
|
||||
I don't remember exactly when I started blogging, but I do remember it was pretty soon after I discovered the internet, IRC, web forums, etc. The idea of being able to publish a website for anyone in the world to read for free was mind-blowing, and I think that's what eventually led me down the rabbit hole of web development. This was around late 1999 or early 2000 when I started college for the first time.
|
||||
|
||||
I didn't have internet at home nor a computer capable of connecting to it, so I used as much time as I could at college labs or nearby internet cafes. I remember using Geocities and writing HTML in Notepad with animated "Under Construction" GIFs, marquee tags, visitor counters, and whatnot. Some time after that (I'm not sure how long exactly), I discovered Blogger and started my first actual blog.
|
||||
|
||||
|
||||
### What platform are you using to manage your blog, and why do you use it?
|
||||
|
||||
I am currently using a self-hosted gmid[3] Gemini[4] capsule, generated using my own capsule generator, Stargem[5]. The capsule is, in turn, proxied via a custom Kineto[6] to the regular internet as my website.
|
||||
|
||||
I like the idea of minimalism—using only what's needed and removing all the cruft. In this age of modern websites with videos, parallax effects, indiscriminate tracking, and ads, I find Gemini's simplicity very compelling and even relaxing. Focus on content, forget everything else.
|
||||
|
||||
As I mentioned at the beginning of this paragraph, the capsule is also available via the regular internet, as that's what most people use. It's very easy to make it accessible on both protocols.
|
||||
|
||||
|
||||
### Have you blogged on other platforms before?
|
||||
|
||||
Not only have I blogged on other platforms, but I've also had so many blog and website attempts that I've lost count. In the past, I've used many platforms. I can at least remember using Blogger, WordPress.com, Ghost, Medium, DEV, and WriteFreely, to name a few.
|
||||
|
||||
The platforms I've used the most, however, are self-hosted WordPress and Jekyll. I like WordPress for sites that require dynamic components. It's very flexible and, when used properly, a powerful platform that can be adapted to almost any need.
|
||||
|
||||
For static sites (which is what I need most of the time), I prefer static site generators. That's why I like Jekyll so much. Jekyll was my first static site generator, and even though I've tried others like Hugo and Eleventy, I always return to Jekyll because of its simplicity and flexibility.
|
||||
|
||||
|
||||
### How do you write your posts?
|
||||
|
||||
Most of the time, I write them on my personal laptop using Visual Studio Code. For this entry, though, I am using NeoVim.
|
||||
|
||||
Over the years, I've used different IDEs and code editors. I've always wanted to love Vim and make it my default editor, but even though I've learned some basic (and maybe intermediate) features, it's never fully clicked for me. That said, I keep pushing myself to use it occasionally to keep what I've learned fresh in my head.
|
||||
|
||||
|
||||
### When do you feel the most inspired to write?
|
||||
|
||||
Probably either right after discovering and testing some new tool/library/framework/toy, or when I wake up very early with an idea in my head. Once my day starts rolling, I rarely have the time or energy to focus on writing.
|
||||
|
||||
Every now and then, I'll also feel inspired while commuting to or from the office, but that doesn't happen often.
|
||||
|
||||
|
||||
### Do you normally publish immediately after writing, or do you let it simmer?
|
||||
|
||||
I'd say it's 50/50. If it's a short post or if I have a very clear idea of what I want to write, I'll finish and publish it immediately.
|
||||
|
||||
For more technical or longer posts, I tend to write in chunks and let them simmer as drafts before publishing.
|
||||
|
||||
|
||||
### What's your favorite post on your blog?
|
||||
|
||||
I don't think I have a favorite post--at least, not yet. I really like how this iteration of my capsule/site/blog is shaping up, but we'll see!
|
||||
|
||||
|
||||
### Any future plans for the blog?
|
||||
|
||||
Just to keep it alive and fresh with new content. While reading another entry in the same challenge that inspired this post, I came across another challenge called "100 Days to Offload."
|
||||
|
||||
It's a big challenge for me because it would require writing a new entry every 3 or 4 days. Still, I'm thinking about giving it a try.
|
||||
|
||||
|
||||
### Who will participate next?
|
||||
|
||||
Like JP did in their post, I don't have anyone specific in mind to nominate. I'll leave the invitation open to you.
|
||||
|
||||
If you, like me, decide to do it, share your answers with me—I'd love to learn a bit about you. If not, that's okay too.
|
||||
|
||||
|
||||
=> gemini://skyjake.fi/~Cosmos/ [1]: Cosmos
|
||||
=> gemini://moddedbear.xyz/logs/2025-01-21-blog-questions-challenge.gmi [2] JP's Blog Questions Challenge 2025
|
||||
=> https://gmid.omarpolo.com/ [3]: gmid
|
||||
=> gemini://geminiprotocol.net/ [4]: Gemini Protocol
|
||||
=> https://code.palmiers.xyz/erick/stargem [5]: Stargem
|
||||
=> https://code.palmiers.xyz/erick/kineto [6]: Kineto (Personal Fork)
|
||||
|
|
@ -1,95 +0,0 @@
|
|||
---
|
||||
date: 2025-01-24 10:01 +0000
|
||||
title: 'Command Line: The Next Generation of My Workflow with Vim and kitty'
|
||||
---
|
||||
In my previous post I mentioned that I have tried to make myself love Vim for a long time. I've read books and posts about it, watched courses, practiced a lot, but still, most of my Vim use tends to be quick edits on my rc files in my laptop or in one of my Raspberry Pi servers. I do know my basic commands and moves, and some not-so-basic ones, but still, I find it counterintuitive to use a terminal as my main driver at work or even for personal projects. But that seems to be changing now.
|
||||
|
||||
|
||||
### My Journey with Vim
|
||||
|
||||
Over the years, I've taken several stabs at mastering Vim. I've read popular resources like "Practical Vim", watched YouTube tutorials, and even taken online courses. While I could manage basic tasks and some advanced workflows, Vim never felt natural as my primary tool. I mostly used it for quick edits, like tweaking my rc files on my laptop or Raspberry Pi servers. However, I've always admired developers who seamlessly navigate and edit code in Vim. I wanted that level of proficiency—and finally, I feel like I'm starting to get there.
|
||||
|
||||
|
||||
### The VS Code Vim Plugin Experience
|
||||
|
||||
This time, the big difference is that I decided to use the Vim extension in Visual Studio Code. By adding the Vim extension, you can bring Vim's keybindings and workflow into a more beginner-friendly environment. At first, it felt odd to use Vim commands in a GUI-based editor, but the combination of VS Code's interface and Vim's power made it click. I've been feeling more comfortable doing my regular work, like writing code, reviewing pull requests, and even editing markdown files. The plugin also introduced me to new Vim extensions, like vim-easymotion, which I've since added to my Vim setup.
|
||||
|
||||
|
||||
### Keeping Vim in the Mix
|
||||
|
||||
While I'm enjoying the Vim extension in VS Code, I'm not giving up on Vim. My goal is to configure Vim to mirror my VS Code setup as closely as possible. I want features like linting, formatting, and autocomplete to work seamlessly in both environments. I know it's possible with the right plugins and configurations, but it takes time to research and set everything up.
|
||||
|
||||
In the past, I experienced the power of a properly configured Vim setup while working with WordPress. I had a streamlined workflow that made editing templates and managing files a breeze. Now, I'm working towards replicating that experience across both Vim and VS Code.
|
||||
|
||||
|
||||
### Exploring Terminal Emulators
|
||||
|
||||
Another part of my workflow that's evolving is my terminal setup. I am currently an iTerm2 user but I've always enjoyed experimenting with other terminal emulators to find tools that enhance my productivity. Previously, I tried Alacritty, which is known for its speed and simplicity, but it didn't quite fit my needs. The default Terminal app on macOS also felt too basic and lacked essential features like fallback fonts and copy-on-select.
|
||||
|
||||
After some research, I discovered kitty, a feature-rich and customizable terminal emulator. Kitty stands out for its excellent font rendering, advanced tab and panel management, and easy configuration. The basic setup was straightforward, and most defaults worked out of the box. I quickly found the color theme I use in iTerm (Tomorrow) and made a few custom keyboard shortcuts. The result? A terminal experience that's both functional and enjoyable.
|
||||
|
||||
One unexpected benefit of using kitty is how it simplifies multitasking. Switching between tabs and panels is so smooth that I've paused my experiment with tmux for local use. I still plan to use tmux for managing remote sessions, but kitty handles local workflows beautifully.
|
||||
|
||||
|
||||
### Sharing My Setup
|
||||
|
||||
I'll keep you posted on my progress and findings, and if everything works as intended, I'll share my tips and tricks for configuring Vim and kitty.
|
||||
|
||||
```
|
||||
font_family family="MonoLisa Variable"
|
||||
bold_font auto
|
||||
italic_font auto
|
||||
bold_italic_font auto
|
||||
font_size 14.0
|
||||
symbol_map U+e000-U+e00a,U+ea60-U+ebeb,U+e0a0-U+e0c8,U+e0ca,U+e0cc-U+e0d7,U+e200-U+e2a9,U+e300-U+e3e3,U+e5fa-U+e6b1,U+e700-U+e7c5,U+ed00-U+efc1,U+f000-U+f2ff,U+f000-U+f2e0,U+f300-U+f372,U+f400-U+f533,U+f0001-U+f1af0 Symbols Nerd Font Mono
|
||||
scrollback_lines 10000
|
||||
show_hyperlink_targets yes
|
||||
underline_hyperlinks always
|
||||
copy_on_select yes
|
||||
macos_quit_when_last_window_closed yes
|
||||
|
||||
include Tomorrow.conf
|
||||
|
||||
map cmd+alt+left previous_tab
|
||||
map cmd+alt+right next_tab
|
||||
map cmd+up neighboring_window up
|
||||
map cmd+down neighboring_window down
|
||||
map cmd+left neighboring_window left
|
||||
map cmd+right neighboring_window right
|
||||
```
|
||||
|
||||
|
||||
### Current Color Theme (Tomorrow):
|
||||
|
||||
```
|
||||
background #ffffff
|
||||
foreground #4c4c4c
|
||||
cursor none
|
||||
selection_background #d6d6d6
|
||||
color0 #000000
|
||||
color8 #000000
|
||||
color1 #c82828
|
||||
color9 #c82828
|
||||
color2 #708b00
|
||||
color10 #708b00
|
||||
color3 #e9b600
|
||||
color11 #e9b600
|
||||
color4 #4170ae
|
||||
color12 #4170ae
|
||||
color5 #8958a7
|
||||
color13 #8958a7
|
||||
color6 #3d999f
|
||||
color14 #3d999f
|
||||
color7 #fffefe
|
||||
color15 #fffefe
|
||||
selection_foreground #ffffff
|
||||
```
|
||||
|
||||
|
||||
### What's Next?
|
||||
|
||||
I'm excited to continue refining my setup and learning more about Vim, VS Code, and terminal emulators. If you have any recommendations for plugins, configurations, or tools I should try, let me know! I'm always on the lookout for new ways to optimize my workflow.
|
||||
|
||||
|
||||
=> https://sw.kovidgoyal.net/kitty/ kitty
|
||||
=> https://github.com/dexpota/kitty-themes kitty-themes
|
||||
|
|
@ -1,26 +0,0 @@
|
|||
---
|
||||
date: 2025-01-28 19:01 +0000
|
||||
title: Timey Wimey Watch Adventures
|
||||
---
|
||||
|
||||
During my life, I've used all sorts of different watches, from regular analog watches to modern smart ones. I stopped using analog watches a long time ago - I was never an "expert" watch reader capable of telling the precise hours minutes and seconds, but I used to consider myself a "normal" reader that could confidenly tell you the time rounded to 5 min intervals. When I started carrying around a mobile phone, specifically a smartphone, I decided to drop the watch. After all, I had a more reliable device that could do way more than just tell the time.
|
||||
|
||||
Fast forward through several smartphones, I discovered a Kickstarter project called Pebble. It was a smartwatch with an e-ink display (I think), a battery that lasted several days, and the ability to fetch live data from the internet and deliver notifications for calls, messages, and apps. The initial model wasn't appealing to me, but they later released a nicer-looking one, the Pebble Steel. That's when I decided to give it a try. I remember enjoying it a lot - customizable watch faces, apps, notifications - you name it, heck I even remember starting to learn how to code my own watch face!.
|
||||
|
||||
Then came the Apple Watch. I got one and enjoyed wearing it, but it wasn't as comfortable as the Pebble, mostly because of the sensor on the back. Still, I kept wearing it. Something I discovered was that my "normal" skill of reading an analog watch face was almost completely gone. I could still read it—I hadn't forgotten—but it took me longer than I'd like to admit to correctly figure out the time. Over time, I found my "sweet spot" for the watch band and wearing style, but I'd still get wrist pain. Sometimes I'd take the watch off for a few hours, a day, or even a weekend. I ignored the discomfort and kept using it - until last year.
|
||||
|
||||
Around this time last year, I decided to experiment. I completely stopped wearing the watch for a week to see how it felt. There were minor inconveniences, like typing my password every time I unlocked my laptop or password manager, but it wasn't too bad. That week turned into two weeks with no major complaints. By the end of the second week, I unpaired and erased the watch to make it harder to just throw it back on. By week four, I was sold - I didn't need the watch, and I wasn't going back. (Or so I thought... but more on that later.)
|
||||
|
||||
One thing I did notice, though, was that I needed a watch, just not a smartwatch. Even with my phone nearby, there were times I wanted to check the time without reaching for it. I started looking for light, thin, and inexpensive watches that looked like they were made for a grown-up, not a 5-year-old. That's how I stumbled upon vintage-looking Casio watches. I was thrilled! They were exactly what I was looking for: slim, light, nice-looking, and affordable. I got myself a Casio A700.
|
||||
|
||||
I loved it! It looked great and made me understand why people get into collecting watches - they're fun, affordable, and stylish. I started wearing my A700 daily and kept visiting the Casio website for more models. Eventually, I decided to get a second model for dressier occasions: the Casio A1100. It's a stainless-steel watch with a comfy wristband and easy-to-use buttons. However, it's heavier than I'd like, the numbers are smaller, and the date isn't visible by default. So, the A1100 became my "dress watch," and the A700 remained my daily driver.
|
||||
|
||||
Fast forward to September and Apple's event: a new Apple Watch, lighter, slimmer, with a slightly larger screen. The smaller model's screen is now as big as the original large model. I decided to try it again, this time going for the 42mm model instead of the 46mm. The size and weight were great, and the features were what you'd expect from Apple. But, once again, my wrist wasn't happy. It wasn't long before I stopped using it again.
|
||||
|
||||
Now I'm back to my A700. While browsing for more Casio models, I found a YouTube video showcasing a model I hadn't seen before: the A500. It has 5 independent alarms, a timer, a stopwatch, and an automatic calendar up to 2099, and a 3 year battery life. A quick search led me to WalMart, and long story short - it's on its way! I should have it in about a week.
|
||||
|
||||
Finally, this morning, I read a note in my RSS feed: Pebble is coming back! I'm not planning to get one right away, but I'll keep an eye on it. Who knows? Maybe next year I'll post another entry about how happy I am with my new Pebble - or how I gave it a try and ended up selling it or leaving it on my desk.
|
||||
|
||||
Edits:
|
||||
|
||||
* 2025-02-05 - Corrected the battery life. In my initial post I stated A500 had a 10 year battery life but that was incorrect. The A500 has a 3 year battery life. The mixup happened because I was also reading the A178WA specs which do mention a 10 year battery life.
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
# Bookmarks
|
||||
|
||||
## Social
|
||||
=> gemini://station.martinrue.com/ Station
|
||||
=> gemini://bbs.geminispace.org/ BBS
|
||||
=> gemini://astrobotany.mozz.us/app Astrobotany
|
||||
|
||||
## Agregators
|
||||
=> gemini://skyjake.fi/~Cosmos/ Cosmos
|
||||
=> gemini://warmedal.se/~antenna/ Antenna
|
||||
|
||||
## Capsules
|
||||
=> gemini://erick.is/ Erick
|
||||
=> gemini://gemi.dev/ Gemi.dev
|
||||
=> gemini://skyjake.fi/ skyjake
|
||||
=> gemini://cities.yesterweb.org/ Yestercities
|
||||
|
||||
## Gemini
|
||||
=> gemini://geminiprotocol.net/ Project Gemini
|
||||
=> gemini://skyjake.fi/lagrange/getting_started.gmi Getting Started
|
||||
|
|
@ -1 +0,0 @@
|
|||
🐼
|
||||
|
|
@ -1,74 +0,0 @@
|
|||
# Modified GoToSocial robots.txt
|
||||
|
||||
# AI scrapers and the like.
|
||||
# https://github.com/ai-robots-txt/ai.robots.txt/
|
||||
User-agent: AI2Bot
|
||||
User-agent: Ai2Bot-Dolma
|
||||
User-agent: Amazonbot
|
||||
User-agent: anthropic-ai
|
||||
User-agent: Applebot
|
||||
User-agent: Applebot-Extended
|
||||
User-agent: Brightbot 1.0
|
||||
User-agent: Bytespider
|
||||
User-agent: CCBot
|
||||
User-agent: ChatGPT-User
|
||||
User-agent: Claude-Web
|
||||
User-agent: ClaudeBot
|
||||
User-agent: cohere-ai
|
||||
User-agent: cohere-training-data-crawler
|
||||
User-agent: Crawlspace
|
||||
User-agent: Diffbot
|
||||
User-agent: DuckAssistBot
|
||||
User-agent: FacebookBot
|
||||
User-agent: FriendlyCrawler
|
||||
User-agent: Google-Extended
|
||||
User-agent: GoogleOther
|
||||
User-agent: GoogleOther-Image
|
||||
User-agent: GoogleOther-Video
|
||||
User-agent: GPTBot
|
||||
User-agent: iaskspider/2.0
|
||||
User-agent: ICC-Crawler
|
||||
User-agent: ImagesiftBot
|
||||
User-agent: img2dataset
|
||||
User-agent: ISSCyberRiskCrawler
|
||||
User-agent: Kangaroo Bot
|
||||
User-agent: Meta-ExternalAgent
|
||||
User-agent: Meta-ExternalFetcher
|
||||
User-agent: OAI-SearchBot
|
||||
User-agent: omgili
|
||||
User-agent: omgilibot
|
||||
User-agent: PanguBot
|
||||
User-agent: PerplexityBot
|
||||
User-agent: PetalBot
|
||||
User-agent: Scrapy
|
||||
User-agent: SemrushBot-OCOB
|
||||
User-agent: SemrushBot-SWA
|
||||
User-agent: Sidetrade indexer bot
|
||||
User-agent: Timpibot
|
||||
User-agent: VelenPublicWebCrawler
|
||||
User-agent: Webzio-Extended
|
||||
User-agent: YouBot
|
||||
Disallow: /
|
||||
|
||||
# Marketing/SEO "intelligence" data scrapers
|
||||
User-agent: AwarioRssBot
|
||||
User-agent: AwarioSmartBot
|
||||
User-agent: DataForSeoBot
|
||||
User-agent: magpie-crawler
|
||||
User-agent: Meltwater
|
||||
User-agent: peer39_crawler
|
||||
User-agent: peer39_crawler/1.0
|
||||
User-agent: PiplBot
|
||||
User-agent: scoop.it
|
||||
User-agent: Seekr
|
||||
Disallow: /
|
||||
|
||||
# Well-known.dev crawler. Indexes stuff under /.well-known.
|
||||
# https://well-known.dev/about/
|
||||
User-agent: WellKnownBot
|
||||
Disallow: /
|
||||
|
||||
# Rules for everything else.
|
||||
User-agent: *
|
||||
Crawl-delay: 500
|
||||
|
||||
|
|
@ -1,171 +0,0 @@
|
|||
html {
|
||||
font-family: sans-serif;
|
||||
color: #444;
|
||||
box-sizing: border-box;
|
||||
}
|
||||
|
||||
*,
|
||||
*:before,
|
||||
*:after {
|
||||
box-sizing: inherit;
|
||||
}
|
||||
|
||||
body {
|
||||
max-width: 800px;
|
||||
margin: 0 auto;
|
||||
padding: 1rem 2rem;
|
||||
}
|
||||
|
||||
blockquote {
|
||||
background-color: #eee;
|
||||
border-left: 3px solid #555;
|
||||
margin: 1rem -1rem 1rem calc(-1rem - 3px);
|
||||
padding: 1rem;
|
||||
}
|
||||
|
||||
ul {
|
||||
margin-top: 1.5rem;
|
||||
margin-bottom: 2rem;
|
||||
margin-left: 0;
|
||||
padding: 0;
|
||||
}
|
||||
|
||||
li {
|
||||
padding: 0;
|
||||
margin: 0;
|
||||
}
|
||||
|
||||
p:has(img) {
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
img {
|
||||
max-width: 80%;
|
||||
}
|
||||
|
||||
a {
|
||||
position: relative;
|
||||
}
|
||||
|
||||
a,
|
||||
a:hover,
|
||||
a:active,
|
||||
a:visited {
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
a:before {
|
||||
content: '⇒';
|
||||
color: #999;
|
||||
font-weight: bold;
|
||||
position: absolute;
|
||||
left: -1.25rem;
|
||||
}
|
||||
|
||||
a:has(img):before {
|
||||
content: '';
|
||||
}
|
||||
|
||||
pre {
|
||||
margin: 1.5rem -1rem 2rem;
|
||||
background-color: #eee;
|
||||
padding: 1rem;
|
||||
overflow-x: auto;
|
||||
}
|
||||
|
||||
article {
|
||||
line-height: 1.5rem;
|
||||
}
|
||||
|
||||
h1 {
|
||||
margin-top: 2.5rem;
|
||||
margin-bottom: 1.5px;
|
||||
font-size: 1.3rem;
|
||||
}
|
||||
|
||||
h2 {
|
||||
margin-top: 2.5rem;
|
||||
font-size: 1.2rem;
|
||||
}
|
||||
|
||||
h3 {
|
||||
font-size: 1.1rem;
|
||||
}
|
||||
|
||||
p {
|
||||
margin-bottom: 1.5rem;
|
||||
}
|
||||
|
||||
p:nth-last-of-type(2) {
|
||||
margin-top: 2.5rem;
|
||||
margin-bottom: 2.5rem;
|
||||
opacity: 0.6;
|
||||
}
|
||||
|
||||
p:has(a) {
|
||||
margin-top: 0rem;
|
||||
margin-bottom: 0.25rem;
|
||||
}
|
||||
|
||||
details:not([open]) summary,
|
||||
details:not([open]) summary a {
|
||||
color: gray;
|
||||
}
|
||||
|
||||
details summary a:before {
|
||||
display: none;
|
||||
}
|
||||
|
||||
dl dt {
|
||||
font-weight: bold;
|
||||
}
|
||||
|
||||
dl dt:not(:first-child) {
|
||||
margin-top: 0.5rem;
|
||||
}
|
||||
|
||||
@media (prefers-color-scheme: dark) {
|
||||
html {
|
||||
background-color: #111;
|
||||
color: #eee;
|
||||
}
|
||||
|
||||
blockquote {
|
||||
background-color: #000;
|
||||
}
|
||||
|
||||
pre {
|
||||
background-color: #222;
|
||||
}
|
||||
|
||||
a,
|
||||
a:hover,
|
||||
a:active {
|
||||
color: #0087bd;
|
||||
}
|
||||
|
||||
a:visited {
|
||||
color: #333399;
|
||||
}
|
||||
}
|
||||
|
||||
label {
|
||||
display: block;
|
||||
font-weight: bold;
|
||||
margin-bottom: 0.5rem;
|
||||
}
|
||||
|
||||
input {
|
||||
display: block;
|
||||
border: 1px solid #888;
|
||||
padding: 0.375rem;
|
||||
line-height: 1.25rem;
|
||||
transition: border-color 0.15s ease-in-out, box-shadow 0.15s ease-in-out;
|
||||
width: 100%;
|
||||
}
|
||||
|
||||
input:focus {
|
||||
outline: 0;
|
||||
border-color: #80bdff;
|
||||
box-shadow: 0 0 0 0.2rem rgba(0, 123, 255, 0.25);
|
||||
}
|
||||
|
|
@ -1,64 +0,0 @@
|
|||
# Test page
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi fermentum dolor ut diam efficitur, non pellentesque purus vulputate. Mauris imperdiet sapien at cursus ullamcorper. Donec viverra, purus a viverra varius, leo augue ullamcorper purus, vitae mattis ipsum velit at nibh. Maecenas iaculis aliquam tempor. Mauris sed convallis nunc, laoreet facilisis sem. Pellentesque ultrices, mi at euismod vehicula, turpis ante aliquet arcu, sit amet tincidunt lacus ligula non leo. Quisque fringilla faucibus quam id placerat.
|
||||
|
||||
=> test.svg Test SVG Image
|
||||
|
||||
## Mauris fermentum feugiat enim
|
||||
|
||||
Get maximus augue sagittis sed. Curabitur massa tellus, porttitor nec tellus in, consequat dignissim purus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nam non iaculis velit. Nulla at rutrum tellus. Ut iaculis nunc ac faucibus placerat. Duis viverra dictum diam. Donec eu auctor odio. Suspendisse eget massa condimentum lorem molestie maximus.
|
||||
|
||||
=> / Quisque nec nisi rutrum
|
||||
|
||||
Facilisis sapien ac, euismod risus. Nulla faucibus, felis nec pulvinar lacinia, nunc odio ultrices magna, porttitor dictum nisi eros vitae justo. Quisque vulputate, nisi sit amet dapibus fermentum, mi leo iaculis erat, vel tristique risus mi sit amet dui.
|
||||
|
||||
=> https://google.com Phasellus pretium neque nec ligula egestas
|
||||
|
||||
Eget porttitor nibh aliquam. Nulla facilisi. Suspendisse sollicitudin quam id tortor eleifend, in bibendum metus pulvinar. Sed ut nisi at augue ultricies tincidunt. Fusce risus diam, vulputate nec fringilla sit amet, scelerisque sed enim. Aliquam eget risus vitae urna pharetra pretium.
|
||||
|
||||
## Aliquam rutrum commodo quam
|
||||
|
||||
Get commodo justo consequat a. Morbi ornare justo sit amet ultrices congue. Ut ultrices blandit tempor. Curabitur et consequat sapien, eget lobortis metus. Vivamus pretium tellus et urna molestie commodo. Aenean vitae sapien vestibulum, hendrerit nibh sed, tempus leo. Mauris eleifend justo a felis pretium sodales.
|
||||
|
||||
> Cras auctor justo non elementum pharetra. Nulla ullamcorper quam nec velit aliquet convallis. Suspendisse elit nisi, euismod a nulla vitae, volutpat tempor felis. Duis urna orci, dapibus sit amet urna a, convallis ornare lorem. Donec varius vitae elit ac lobortis. Curabitur id hendrerit ipsum. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean ut dui in turpis efficitur rhoncus. In et lacinia lectus, ac molestie odio. Curabitur ultrices felis est, nec semper ante posuere eget. In vel elit lacus.
|
||||
|
||||
## Nam facilisis erat ex
|
||||
|
||||
* Ac ultricies eros tempus a
|
||||
* Phasellus fermentum lacus odio
|
||||
* Ac luctus diam cursus ac
|
||||
* Orci varius natoque penatibus et magnis dis parturient montes
|
||||
|
||||
### Ascetur ridiculus mus
|
||||
|
||||
Ut vitae sagittis tellus. Fusce tortor dui, interdum in risus eget, sollicitudin fringilla ligula. Duis vehicula hendrerit enim, eu fringilla nisi fermentum non. Pellentesque feugiat maximus dolor, ac pellentesque libero venenatis id. Suspendisse vestibulum justo quis magna sodales, et varius ante congue.
|
||||
|
||||
|
||||
```
|
||||
>>> import this
|
||||
The Zen of Python, by Tim Peters
|
||||
|
||||
Beautiful is better than ugly.
|
||||
Explicit is better than implicit.
|
||||
Simple is better than complex.
|
||||
Complex is better than complicated.
|
||||
Flat is better than nested.
|
||||
Sparse is better than dense.
|
||||
Readability counts.
|
||||
Special cases aren't special enough to break the rules.
|
||||
Although practicality beats purity.
|
||||
Errors should never pass silently.
|
||||
Unless explicitly silenced.
|
||||
In the face of ambiguity, refuse the temptation to guess.
|
||||
There should be one-- and preferably only one --obvious way to do it.
|
||||
Although that way may not be obvious at first unless you're Dutch.
|
||||
Now is better than never.
|
||||
Although never is often better than *right* now.
|
||||
If the implementation is hard to explain, it's a bad idea.
|
||||
If the implementation is easy to explain, it may be a good idea.
|
||||
Namespaces are one honking great idea -- let's do more of those!
|
||||
```
|
||||
|
||||
### Phasellus molestie in metus sit amet vestibulum
|
||||
|
||||
Nunc cursus nunc consectetur sapien aliquet eleifend. Sed facilisis ipsum iaculis egestas accumsan. Morbi congue ac lectus a sollicitudin. Pellentesque bibendum laoreet tortor quis interdum. In sed arcu odio. Pellentesque turpis orci, mattis vitae ligula nec, semper molestie tellus. Integer nunc risus, vehicula non felis eget, ultricies faucibus urna.
|
||||
|
|
@ -1 +0,0 @@
|
|||
<svg xmlns="http://www.w3.org/2000/svg" width="600" height="400" viewBox="0 0 600 400"><rect width="100%" height="100%" fill="#EEE"/><path fill="#31343C" d="m155.52 171.08-17.16 21-2 2.48q1.68-.84 3.62-1.3 1.94-.46 4.18-.46 3.28 0 6.38 1.08t5.46 3.26q2.36 2.18 3.8 5.42 1.44 3.24 1.44 7.56 0 4.04-1.48 7.58t-4.16 6.18q-2.68 2.64-6.46 4.16t-8.34 1.52q-4.64 0-8.32-1.48-3.68-1.48-6.28-4.14-2.6-2.66-3.98-6.4t-1.38-8.3q0-4.08 1.66-8.38 1.66-4.3 5.14-8.94l13.8-18.52q.72-.96 2.1-1.64 1.38-.68 3.18-.68h8.8Zm-14.92 50.4q2.36 0 4.34-.8t3.4-2.24q1.42-1.44 2.22-3.38.8-1.94.8-4.22 0-2.48-.76-4.46t-2.16-3.36q-1.4-1.38-3.36-2.1-1.96-.72-4.32-.72-2.36 0-4.28.8-1.92.8-3.28 2.22-1.36 1.42-2.12 3.36t-.76 4.18q0 2.4.66 4.38t1.96 3.38q1.3 1.4 3.22 2.18 1.92.78 4.44.78ZM208.28 200q0 7.56-1.62 13.14-1.62 5.58-4.48 9.22-2.86 3.64-6.76 5.42-3.9 1.78-8.42 1.78t-8.38-1.78q-3.86-1.78-6.7-5.42-2.84-3.64-4.44-9.22-1.6-5.58-1.6-13.14 0-7.6 1.6-13.16 1.6-5.56 4.44-9.2 2.84-3.64 6.7-5.42 3.86-1.78 8.38-1.78 4.52 0 8.42 1.78 3.9 1.78 6.76 5.42 2.86 3.64 4.48 9.2 1.62 5.56 1.62 13.16Zm-10.2 0q0-6.28-.92-10.4t-2.46-6.56q-1.54-2.44-3.54-3.42t-4.16-.98q-2.12 0-4.1.98-1.98.98-3.5 3.42t-2.42 6.56q-.9 4.12-.9 10.4t.9 10.4q.9 4.12 2.42 6.56 1.52 2.44 3.5 3.42t4.1.98q2.16 0 4.16-.98t3.54-3.42q1.54-2.44 2.46-6.56.92-4.12.92-10.4Zm56.6 0q0 7.56-1.62 13.14-1.62 5.58-4.48 9.22-2.86 3.64-6.76 5.42-3.9 1.78-8.42 1.78t-8.38-1.78q-3.86-1.78-6.7-5.42-2.84-3.64-4.44-9.22-1.6-5.58-1.6-13.14 0-7.6 1.6-13.16 1.6-5.56 4.44-9.2 2.84-3.64 6.7-5.42 3.86-1.78 8.38-1.78 4.52 0 8.42 1.78 3.9 1.78 6.76 5.42 2.86 3.64 4.48 9.2 1.62 5.56 1.62 13.16Zm-10.2 0q0-6.28-.92-10.4t-2.46-6.56q-1.54-2.44-3.54-3.42t-4.16-.98q-2.12 0-4.1.98-1.98.98-3.5 3.42t-2.42 6.56q-.9 4.12-.9 10.4t.9 10.4q.9 4.12 2.42 6.56 1.52 2.44 3.5 3.42t4.1.98q2.16 0 4.16-.98t3.54-3.42q1.54-2.44 2.46-6.56.92-4.12.92-10.4Zm73.72 15.68-5.24 5.16-13.56-13.56-13.68 13.64-5.24-5.16 13.68-13.72L281.12 189l5.2-5.2 13.04 13.04 12.96-12.96 5.28 5.2-13 13 13.6 13.6Zm34.64-8.56h17.6V188.2q0-2.68.36-5.92l-17.96 24.84Zm26.2 0h7.28v5.72q0 .8-.52 1.38-.52.58-1.48.58h-5.28v14.12h-8.6V214.8h-24.4q-1 0-1.76-.62t-.96-1.54l-1.04-5 27.4-36.6h9.36v36.08Zm53.72-7.12q0 7.56-1.62 13.14-1.62 5.58-4.48 9.22-2.86 3.64-6.76 5.42-3.9 1.78-8.42 1.78t-8.38-1.78q-3.86-1.78-6.7-5.42-2.84-3.64-4.44-9.22-1.6-5.58-1.6-13.14 0-7.6 1.6-13.16 1.6-5.56 4.44-9.2 2.84-3.64 6.7-5.42 3.86-1.78 8.38-1.78 4.52 0 8.42 1.78 3.9 1.78 6.76 5.42 2.86 3.64 4.48 9.2 1.62 5.56 1.62 13.16Zm-10.2 0q0-6.28-.92-10.4t-2.46-6.56q-1.54-2.44-3.54-3.42t-4.16-.98q-2.12 0-4.1.98-1.98.98-3.5 3.42t-2.42 6.56q-.9 4.12-.9 10.4t.9 10.4q.9 4.12 2.42 6.56 1.52 2.44 3.5 3.42t4.1.98q2.16 0 4.16-.98t3.54-3.42q1.54-2.44 2.46-6.56.92-4.12.92-10.4Zm56.6 0q0 7.56-1.62 13.14-1.62 5.58-4.48 9.22-2.86 3.64-6.76 5.42-3.9 1.78-8.42 1.78t-8.38-1.78q-3.86-1.78-6.7-5.42-2.84-3.64-4.44-9.22-1.6-5.58-1.6-13.14 0-7.6 1.6-13.16 1.6-5.56 4.44-9.2 2.84-3.64 6.7-5.42 3.86-1.78 8.38-1.78 4.52 0 8.42 1.78 3.9 1.78 6.76 5.42 2.86 3.64 4.48 9.2 1.62 5.56 1.62 13.16Zm-10.2 0q0-6.28-.92-10.4t-2.46-6.56q-1.54-2.44-3.54-3.42t-4.16-.98q-2.12 0-4.1.98-1.98.98-3.5 3.42t-2.42 6.56q-.9 4.12-.9 10.4t.9 10.4q.9 4.12 2.42 6.56 1.52 2.44 3.5 3.42t4.1.98q2.16 0 4.16-.98t3.54-3.42q1.54-2.44 2.46-6.56.92-4.12.92-10.4Z"/></svg>
|
||||
|
Before Width: | Height: | Size: 3.2 KiB |
111
styles.css
Normal file
111
styles.css
Normal file
|
|
@ -0,0 +1,111 @@
|
|||
:root {
|
||||
--opacity: 1;
|
||||
--margin: 20px;
|
||||
--margin-2x: calc(var(--margin) * 2);
|
||||
--max-width: 600px;
|
||||
--line-height: 1.5rem;
|
||||
--logo-size: 150px;
|
||||
|
||||
/* One ½ Light Color Scheme */
|
||||
/* https://github.com/sonph/onehalf */
|
||||
--color-black: #383a42;
|
||||
--color-red: #e45649;
|
||||
--color-green: #50a14f;
|
||||
--color-yellow: #c18401;
|
||||
--color-blue: #0184bc;
|
||||
--color-magenta: #a626a4;
|
||||
--color-cyan: #0997b3;
|
||||
--color-white: #fafafa;
|
||||
--color-foreground: #383a42;
|
||||
--color-background: #fafafa;
|
||||
}
|
||||
|
||||
html {
|
||||
box-sizing: border-box;
|
||||
}
|
||||
|
||||
*,
|
||||
*:before,
|
||||
*:after {
|
||||
box-sizing: inherit;
|
||||
}
|
||||
|
||||
@media (prefers-color-scheme: dark) {
|
||||
:root {
|
||||
/* One ½ Dark Color Scheme */
|
||||
/* https://github.com/sonph/onehalf */
|
||||
--color-black: #282c34;
|
||||
--color-red: #e06c75;
|
||||
--color-green: #98c379;
|
||||
--color-yellow: #e5c07b;
|
||||
--color-blue: #61afef;
|
||||
--color-magenta: #c678dd;
|
||||
--color-cyan: #56b6c2;
|
||||
--color-white: #dcdfe4;
|
||||
--color-foreground: #dcdfe4;
|
||||
--color-background: #282c34;
|
||||
}
|
||||
}
|
||||
|
||||
html,
|
||||
body {
|
||||
width: 100%;
|
||||
height: 100%;
|
||||
margin: auto;
|
||||
}
|
||||
|
||||
body {
|
||||
color: var(--color-foreground);
|
||||
background-color: var(--color-background);
|
||||
max-width: var(--max-width);
|
||||
font-family: sans-serif;
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
main {
|
||||
margin: var(--margin);
|
||||
opacity: var(--opacity);
|
||||
line-height: var(--line-height);
|
||||
}
|
||||
|
||||
header {
|
||||
margin-top: var(--margin-2x);
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.panda {
|
||||
width: var(--logo-size);
|
||||
height: var(--logo-size);
|
||||
border-radius: calc(var(--logo-size) / 2);
|
||||
}
|
||||
|
||||
nav {
|
||||
display: flex;
|
||||
flex-wrap: wrap;
|
||||
justify-content: center;
|
||||
margin: var(--margin-2x) 0;
|
||||
}
|
||||
|
||||
a {
|
||||
display: block;
|
||||
margin: 0 var(--margin);
|
||||
opacity: var(--opacity);
|
||||
color: var(--color-blue);
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
a:hover,
|
||||
a:active,
|
||||
a:focus {
|
||||
text-decoration: underline;
|
||||
}
|
||||
|
||||
footer {
|
||||
margin-top: var(--margin-2x);
|
||||
padding-bottom: var(--margin);
|
||||
opacity: calc(var(--opacity) / 2);
|
||||
}
|
||||
|
|
@ -1,19 +0,0 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<feed xmlns="http://www.w3.org/2005/Atom">
|
||||
<title>Erick Ruiz de Chavez</title>
|
||||
<id>gemini://erick.is/gemlog.gmi</id>
|
||||
<updated>{{ now.isoformat() }}</updated>
|
||||
<link href="gemini://erick.is/gemlog.gmi"></link>
|
||||
{% if stargem.posts -%}
|
||||
{% for post in (stargem.posts | sort(attribute='frontmatter.date', reverse=True)) -%}
|
||||
<entry>
|
||||
<title>{{ post.frontmatter.title }}</title>
|
||||
<updated>{{ post.frontmatter.date.isoformat() }}</updated>
|
||||
<id>gemini://erick.is{{ post.path }}</id>
|
||||
<link href="gemini://erick.is{{ post.path }}" rel="alternate"></link>
|
||||
<summary type="html"></summary>
|
||||
<author><name>Erick Ruiz de Chavez</name></author>
|
||||
</entry>
|
||||
{% endfor -%}
|
||||
{% endif -%}
|
||||
</feed>
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
## Links
|
||||
|
||||
=> https://gts.erick.sh/@erick Fediverse
|
||||
=> https://code.erick.sh/erick Source Code
|
||||
=> https://linkedin.com/in/erickruizdechavez LinkedIn
|
||||
=> https://github.com/eruizdechavez GitHub
|
||||
|
||||
|
||||
© {{ now.strftime('%Y') }} Erick Ruiz de Chavez
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
{% include "header.jinja" %}
|
||||
|
||||
=> / Front page
|
||||
|
||||
## Posts
|
||||
|
||||
{% if stargem.posts -%}
|
||||
{% for post in (stargem.posts | sort(attribute='frontmatter.date', reverse=True)) -%}
|
||||
=> {{ post.path }} {{ post.frontmatter.date.strftime('%F') }} {{ post.frontmatter.title }}
|
||||
{% endfor -%}
|
||||
{% endif -%}
|
||||
|
||||
{% if stargem.drafts %}
|
||||
## Drafts
|
||||
{% for draft in stargem.drafts -%}
|
||||
=> {{ draft.path }} {{ draft.frontmatter.title }}
|
||||
{% endfor -%}
|
||||
{% endif %}
|
||||
|
||||
{% include "footer.jinja" %}
|
||||
|
|
@ -1 +0,0 @@
|
|||
# Erick Ruiz de Chavez
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
{% include "header.jinja" %}
|
||||
{{ content }}
|
||||
|
||||
{% include "footer.jinja" -%}
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
{% include "header.jinja" %}
|
||||
{{ content }}
|
||||
|
||||
{% if stargem.posts -%}
|
||||
## Latests Posts
|
||||
{% for post in (stargem.posts | sort(attribute='frontmatter.date', reverse=True))[:5] -%}
|
||||
=> {{ post.path }} {{ post.frontmatter.date.strftime('%F') }} {{ post.frontmatter.title }}
|
||||
{% endfor %}
|
||||
{%- if stargem.posts | length > 5 %}
|
||||
=> gemlog.gmi All Posts
|
||||
{% endif -%}
|
||||
{% endif -%}
|
||||
|
||||
{% if stargem.drafts %}
|
||||
## Drafts
|
||||
{% for draft in stargem.drafts -%}
|
||||
=> {{ draft.path }} {{ draft.frontmatter.title }}
|
||||
{% endfor -%}
|
||||
{% endif %}
|
||||
|
||||
{% include "footer.jinja" %}
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
{% include "header.jinja" %}
|
||||
## {{ frontmatter.title }}
|
||||
|
||||
=> / Front page
|
||||
{%- if stargem.posts | length > 5 %}
|
||||
=> /gemlog.gmi All Posts
|
||||
{%- endif %}
|
||||
|
||||
{{ content }}
|
||||
|
||||
{% include "footer.jinja" %}
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
{% include "header.jinja" %}
|
||||
## {{ frontmatter.title }}
|
||||
|
||||
=> / Front page
|
||||
{%- if stargem.posts | length > 5 %}
|
||||
=> /gemlog.gmi All Posts
|
||||
{%- endif %}
|
||||
|
||||
> Published: {% if frontmatter.date %}{{ frontmatter.date.strftime('%F') }}{%else%}TBD{% endif %}
|
||||
|
||||
{{ content }}
|
||||
|
||||
{% include "footer.jinja" %}
|
||||
Loading…
Add table
Reference in a new issue