Skip to main content
tdro

Another wandering soul screaming into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

tdro micro.thedroneely.com view Markdown Plaintext Embed Permalink Feb 14 2023 01:31 UTC 23 sec 69/50 words

Messing around with a statically generated site can easily lead into a web/browser spec rabbit hole. And.. that’s when I remember exactly why everything ends up written outside the browser’s framework into a framework. I think Firefox is still the only browser that allows easily setting image fallback styling completely with just ?

Fallback image styling in Firefox
Making this happen in other browsers demands a magical rain dance
Index: Cache · Source
#webdev
tdro

Another wandering soul screaming into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

tdro micro.thedroneely.com (edited) view Markdown Plaintext Embed Permalink Feb 6 2023 18:23 UTC 4 sec 11/50 words
tdro

Another wandering soul screaming into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

tdro micro.thedroneely.com view Markdown Plaintext Embed Permalink Jan 24 2023 16:40 UTC 23 sec 70/50 words

The Enhance Framework looks compelling. Personally, web components and more particularly the shadow DOM are not very appealing but… the template structure looks clean for drawing up components/layouts super fast while still being primitive enough to not lose transposability between different environments.

It seems like there’s an uptick in discussions online around web components but maybe that’s just the typical developer marketing/advocating. Web components have been around for a bit.

#webdev
tdro

Another wandering soul screaming into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

tdro micro.thedroneely.com view Markdown Plaintext Embed Permalink Dec 29 2022 23:03 UTC 30 sec 90/50 words

I’ve since realized that Hugo’s architecture provides a variety of template optimization strategies. Hugo builds pages concurrently, so it might be hard to see on a modern device but before partialCaches or module mount trickery — there’s still the implicit complexity of the output/lookup model.

Generally the complexity cost of the default output formats are: page > term > taxonomy > section > home. Keeping expensive calls inside a section and/or a home template is usually optimal. and maybe memory should be the only problems with lots of pages.

#webdev

Authors

Gallery

Following (6)

Web Ring