css

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 2.9% — this entity appeared in 82 of 2,852 analyzed posts/comments in the seven days ending that day (146 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-15 14:33 UTCComment

   HTML and CSS alone won't enumerate folders or pick up new files. A page opened directly from disk can link to specific files if you write each href by hand, but it can't scan a directory, so anything added later just won't appear until you edit the page again. For the whole-PC version, the practical approach is a small script that walks the directories you care about and generates the HTML, thumbnails, and embed tags. That also handles map-style layouts without dragging every item around manually.

2. 2026-10-15 14:20 UTCPost

   Offline uses for HTML (+ CSS)? - Crosspost from /r/HTML Last night, right before drifting into sleep, I got some crazy idea for some offline use case for HTML/CSS... But I can't remember exactly the idea that I had in mind. It had something to do with photos or maps? I guess it was some "interactive" html/css based interface or mindmap kind of thing, about all the variety of stuff I have on my computer. For example, if I'm writing something, this file is its own separate entity. A file in "my documents", with no relation to any other file. How about combining all of these files into this freeform "interface" by making an offline website that links into physical locations on my PC? I could organize my thoughts, my screenshots, my writings, my photos, my videos, my source materials, everything into a one personal use "platform" designed from the ground up to suit my workflow, that I could always expand. Files would not be separate instances hidden in the files, but rather a part of a bigger system. Their links could be highlighted, they could have visual cues to direct my attention, they could have thumbnails or explanatory notes, they could be inbedded videos. Has anyone ever done anything like this?

3. 2026-10-14 23:38 UTCComment

   I don't know your stack and setup, but is it possible your apps, or future apps, could be shifted to a more backend focused setup that HAPPENS to create a front end? Basically server side rendering, something like NiceGUI in Python so you don't even need to learn HTML/JS/CSS/React/Angular/Vue/whatever else

4. 2026-10-14 23:22 UTCComment

   Hey I'm a front end lead. I am assuming you're talking about web-apps. Skills in the order I would learn them, if I was you: Usability. If you have designers you don't have to deep dive, but a 101 course or the youtube equivalent will help a lot. It is mostly a lot of tips like "try to have no more than 7 menu items without grouping them, because human short term memory holds 5-9 things." It should give you a structure to think about what UIs do and why. Graphic design: read about layout grids. You have to understand spacing to be able to replicate a design properly. Things need to line up, be evenly spaced etc and we use grids to do that. On the web we have to think about fluidity and form factors too. Optionally you can get into visual hierarchy, colours, and fonts - but a designer would do that work for you. Accessibility. You can put accessibility testing including screen reader testing in your CI pipeline. Read a few articles so you avoid the main beartaps. Browser technology. Learn about modern HTML and CSS, it has a lot of features - you might not need JavaScript for more than you imagine. Brush up on stuff like HTTP cacheing, redirects, error codes. There's a ton of power in HTTP and REST and HTML. The book Every Layout changed how I think about CSS. Design systems. There are a few standards for how to structure a design system, which can be applied to CSS. It's just a format for organising and naming colours, fonts, spacings etc Typescript. It's quite like C#. The type system is a bit fiddly but very powerful. Your agents will be a lot more reliable if you start out with good types. For extra credit find a way to share over-the-wire types between front and backend. We tend to use functional patterns like map and reduce a lot. A framework and metaframework. Take your pick! Make sure you're doing server side rendering, it's 2026. React/NextJS is the most employable but I hate it. Whatever you're using, learn how it works. Try to avoid loading spinners whenever you can.

5. 2026-10-14 22:29 UTCComment

   As a backend guy who got pulled into frontend work the same way, the fastest jump in quality came from just copying patterns from sites I liked. Not the code, but the spacing, font sizes, button styles, how they handle empty states. You start to build an eye for what looks off. For code quality, pick a component library and stick to it instead of hand rolling everything. Keeps the JSX cleaner and saves you from the classic backend dev sin of writing a 200 line CSS file that fights itself. Also ask whoever does your design work for a style guide, even a rough one. Having tokens for colors and spacing upfront removes like half the ugly.