diff options
Diffstat (limited to 'posts')
| -rw-r--r-- | posts/Please_Make_Your_Table_Headings_Sticky.md | 16 | ||||
| -rw-r--r-- | posts/heif.md | 4 | ||||
| -rw-r--r-- | posts/luba.md | 14 | ||||
| -rw-r--r-- | posts/macos-convert-to-html.md | 45 | ||||
| -rw-r--r-- | posts/mail.md | 14 | ||||
| -rw-r--r-- | posts/tables.md | 6 |
6 files changed, 38 insertions, 61 deletions
diff --git a/posts/Please_Make_Your_Table_Headings_Sticky.md b/posts/Please_Make_Your_Table_Headings_Sticky.md index ef2e810..249066a 100644 --- a/posts/Please_Make_Your_Table_Headings_Sticky.md +++ b/posts/Please_Make_Your_Table_Headings_Sticky.md @@ -4,12 +4,7 @@ I often stumble upon large data sets or table layouts across the web. When these tables contain hundreds of rows of content, things become problematic once you start to scroll... - -<video width="100%" controls> -<source src="https://btxx.org/posts/Please_Make_Your_Table_Headings_Sticky/not-fixed-header-tables.mp4" type="video/mp4"> -Your browser does not support the video tag. -</video> - +[Click here to see standard table headers video](/public/videos/not-fixed-header-tables.mp4) <h2>This should be a header</h2> @@ -19,12 +14,7 @@ Look at that table header disappear! Now, if I scroll all the way down to item # Check it out: - -<video width="100%" controls> -<source src="https://btxx.org/ikiwiki/git/fixed-header-tables.mp4" type="video/mp4"> -Your browser does not support the video tag. -</video> - +[Click here to see "fixed" table headers video](/public/videos/fixed-header-tables.mp4) Pretty awesome, right? It might look like magic but it's actually very easy to implement. You only need to add 2 CSS properties on your `thead`: @@ -35,4 +25,4 @@ That's it! Best of all, `sticky` has [~96% global support](https://caniuse.com/? You can view a live demo of this table on the [CodePen example pen](https://codepen.io/bradleytaunt/pen/bGZyJBj). -If you found this interesting, feel free to check out my other table-focused post: [Making Tables Responsive With Minimal CSS](https://btxx.org/posts/tables/) +If you found this interesting, feel free to check out my other table-focused post: [Making Tables Responsive With Minimal CSS](/posts/tables/) diff --git a/posts/heif.md b/posts/heif.md index dc747b4..f0d645a 100644 --- a/posts/heif.md +++ b/posts/heif.md @@ -39,5 +39,5 @@ Simple as that. Happy converting! If you're interested, I also have some other Automator scripts available: -- [Batch Converting Images to webp with macOS Automator](/batch-webp-conversion/) -- [Convert Files to HTML with macOS Automator Quick Actions](/macos-convert-to-html/) +- [Batch Converting Images to webp with macOS Automator](/posts/batch-webp-conversion/) +- [Convert Files to HTML with macOS Automator Quick Actions](/posts/macos-convert-to-html/) diff --git a/posts/luba.md b/posts/luba.md index 6e43eca..08dc7be 100644 --- a/posts/luba.md +++ b/posts/luba.md @@ -6,10 +6,9 @@ I'm no stranger to robotic lawnmowers. When my wife and I moved into our rural home just over five years ago, we picked up the Husqvarna 450X Automower since I was far too lazy to manually mow my property and the cost was equal to that of a standard riding mower. It was a no-brainer. -<figure> - <img src="/public/images/mower-1.jpeg" alt="The Husqvarna 450X"> - <figcaption>The Husqvarna 450X (not mine but same model)</figcaption> -</figure> + + +*The Husqvarna 450X (not mine but same model)* Fast-forward five years. Everything is still going great with the Automower. Some minor repairs were needed but that was mostly my fault since I was allowing the mower into places it shouldn't have been (ie. root systems and dirt "craters"). Then lightning struck our backyard at the beginning of April this year. The mower was fine, since we stow it away inside for the winter but the charging station, charging brick and perimeter wire we *not* so lucky... @@ -42,10 +41,9 @@ So I contacted my local dealer again about these specific units. I came away wit While researching "wireless" automowers, I came across the [Luba Series 5000](https://mammotion.com/?ref=bpjfzw7s) (referral link) and kept it in my "maybe" pile to follow-up on if needed. So follow-up I did. -<figure> - <img src="/public/images/mower-2.webp" alt="The Luba Series 5000"> - <figcaption>The Luba Series 5000 AWD (not mine but same model)</figcaption> -</figure> + + +*The Luba Series 5000 AWD (not mine but same model)* This mower seemed to check all my boxes: diff --git a/posts/macos-convert-to-html.md b/posts/macos-convert-to-html.md index 78cc3d3..3349354 100644 --- a/posts/macos-convert-to-html.md +++ b/posts/macos-convert-to-html.md @@ -2,7 +2,7 @@ 2022-01-28 -Since a few people have reached out and thanked me for my previous post [Batch Converting Images to webp with macOS Automator](/batch-webp-conversion), I thought I would continue to share more of my own custom Automator Quick Actions. Today's post will cover the ability to convert *any* text-based document into pure HTML. +Since a few people have reached out and thanked me for my previous post [Batch Converting Images to webp with macOS Automator](/posts/batch-webp-conversion), I thought I would continue to share more of my own custom Automator Quick Actions. Today's post will cover the ability to convert *any* text-based document into pure HTML. I know - there are over 6 billion conversion apps that do this very same thing. But our way of doing it is *cooler*. Our conversion tool: @@ -48,18 +48,17 @@ Wait for everything to finish and you're done! Next you'll want to open the macOS Automator app and create a new "Quick Action" when given the prompt to do so. -<figure> - <img src="/public/images/new-automator.png" alt="Toggle prompt for new automation in macOS Automator"> - <figcaption>After opening Automator, select "Quick Action" from the menu (<a href="/public/images/new-automator.webp">link to hi-res image</a>)</figcaption> -</figure> + + +*After opening Automator, select "Quick Action" from the menu* Now do the following (reference the image further below to make sure your parameters match): -1. Set "Workflow receives current" to <strong>documents</strong> in <strong>any application</strong> +1. Set "Workflow receives current" to **documents** in **any application** 2. In the search bar type in "Run Shell Script" 3. Drag-and-drop the "Run Shell Script" from the left pane into the right pane -4. Set the "Shell" parameter to <strong>/bin/bash</strong> -5. Set "Pass input" as <strong>as arguments</strong> +4. Set the "Shell" parameter to **/bin/bash** +5. Set "Pass input" as **as arguments** Once all that is done, simply paste the following in the open text field within the "Run Shell Script" item: @@ -72,10 +71,7 @@ Once all that is done, simply paste the following in the open text field within If you've done everything correctly it should look something like this: -<figure> - <img src="/public/images/new-automator-2.png" alt="Automator quick action details for converting to HTML"> - <figcaption>This is what your finished Automator quick action should look like (<a href="/public/images/new-automator-2.webp">link to hi-res image</a>)</figcaption> -</figure> + Save this new Quick Action (Name is something like "Convert to HTML" to keep things simple). That's it! Amazing, right? @@ -83,28 +79,25 @@ Save this new Quick Action (Name is something like "Convert to HTML" to keep thi Now it is finally time to see our Quick Action is *action*! Navigate to any document file in a Finder window and follow along. -1. First, right-click on the file you wish to convert. ([Figure 1](#fig-1)) +1. First, right-click on the file you wish to convert. See Fig.1) 2. In the pop-up container, scroll down and hover over `Quick Actions`. -3. A secondary pop-out will appear. Look for the action `Convert File to HTML` and click it. ([Figure 2](#fig-2)) +3. A secondary pop-out will appear. Look for the action `Convert File to HTML` and click it. See Fig.2) + + -<figure id="fig-1"> - <img src="/public/images/macos-convert-1.png" alt="A markdown file in macOS Finder"> - <figcaption><strong>Figure 1:</strong> Finding and right-clicking on your desired file (<a href="/public/images/macos-convert-1.webp">link to hi-res image</a>)</figcaption> -</figure> +*Fig 1: Finding and right-clicking on your desired file* -<figure id="fig-2"> - <img src="/public/images/macos-convert-2.png" alt="Convert to HTML action selection"> - <figcaption><strong>Figure 2:</strong> From the "Quick Actions" menu, select "Convert to HTML" (<a href="/public/images/macos-convert-2.webp">link to hi-res image</a>)</figcaption> -</figure> + + +*Fig 2: From the "Quick Actions" menu, select "Convert to HTML"* If everything was set up properly (and depending on the size of the file) you should see your converted HTML file show up right next to your existing document. Time to celebrate! Don't forget - you can also *batch* convert multiple files and multiple file *types* at once. The possibilities are endless! -<figure> - <img src="/public/images/macos-convert-3.png" alt="Finder window showing a Markdown file and an HTML file"> - <figcaption>Our converted document is now available in HTML. Absolutely glorious. (<a href="/public/images/macos-convert-3.webp">link to hi-res image</a>)</figcaption> -</figure> + + +*Our converted document is now available in HTML. Absolutely glorious.* ## No Limits diff --git a/posts/mail.md b/posts/mail.md index 9a58f8e..d50e5a5 100644 --- a/posts/mail.md +++ b/posts/mail.md @@ -10,10 +10,9 @@ I recently covered how to [work with git email patches in Evolution on Linux](/g The first thing you'll need to do is make a new `Patches` mailbox folder inside your existing mail account. Once done, your default Mail sidebar should look similar to the following: -<figure> - <img src="/public/images/apple-mail-1.png" alt="The Apple Mail sidebar with the Patches folder present"> - <figcaption>The Apple Mail sidebar with the "Patches" folder present</figcaption> -</figure> + + +*The Apple Mail sidebar with the "Patches" folder present* ## Applying Patches @@ -21,10 +20,9 @@ Now navigate to the email message containing a `git` patch. Right-click and sele Inside this folder you should see something similar to the following structure: -<figure> - <img src="/public/images/apple-mail-2.png" alt="The contents of the saved Patches mailbox folder"> - <figcaption>The contents of the saved Patches mailbox folder</figcaption> -</figure> + + +*The contents of the saved Patches mailbox folder* Once saved, open your terminal, navigate to the project you wish to apply this new patch to: diff --git a/posts/tables.md b/posts/tables.md index 31bec8d..787daed 100644 --- a/posts/tables.md +++ b/posts/tables.md @@ -2,15 +2,13 @@ 2019-06-11 -<div class="update-box"> - <strong>Update (Oct 2019):</strong> <a href="https://twitter.com/aardrian">@aardrian</a> wrote a previous post about how changing the <code>display</code> properties on tables can impact screen readers. I highly recommend his excellent article <a href="https://adrianroselli.com/2018/02/tables-css-display-properties-and-aria.html">Tables, CSS Display Properties, and ARIA</a> -</div> +**Update (Oct 2019):** @aardrian wrote a previous post about how changing the `display` properties on tables can impact screen readers. I highly recommend his excellent article [Tables, CSS Display Properties, and ARIA](https://adrianroselli.com/2018/02/tables-css-display-properties-and-aria.html) --- I find that the need to create responsive table layouts pops up far more often than most developers would expect. The gut reaction might to be implement some sort of custom grid-system or pull in a pre-built library. Don't do this - just use tables and some simple CSS. -My recent article, [Write HTML Like It's 1999](/html-like-1999), received far more attention than I ever expected on HackerNews. With this attention came a few comments mentioning how `table` elements don't play nice with mobile devices or that it's not possible to have a useable layout on smaller screens. *This simply isn't true*. +My recent article, [Write HTML Like It's 1999](/posts/html-like-1999), received far more attention than I ever expected on HackerNews. With this attention came a few comments mentioning how `table` elements don't play nice with mobile devices or that it's not possible to have a useable layout on smaller screens. *This simply isn't true*. Included below are two separate demos showing how to optimize `table` HTML for mobile devices using only a minimal amount of CSS. These implementations may not be perfect, but they are far superior to injecting a bunch of custom `div` elements to *look* like tables. |