← Back to context

Comment by taintlord223

4 hours ago

The UI of that page is so nice, should build a github competitor.

The user profile / contributions and PR UX is pretty much the entire "hub" product since git is a fully separate offline app.

> The UI of that page is so nice

Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with.

I think most of us who've tried using LLMs for web-design can recognize that style and design at this point, regardless of model actually used.

  • Oh wow, I'm in the position to be able to give a peek behind the curtain of something (validly!!) critiqued as AI slop! Exciting.

    I originally made the core data functionality of this site for myself because I was curious what the uptime stats for each service were (I build something that heavily depends on GitHub), and to viz the distribution/severity of those incidents, again per-service, over time.

    It involved a lot of back-and-forth, and is not a one-shotter; maybe closer to 40-50 shots over maybe ~10 hours of human time. A couple memorable things that made it complicated, irrespective of the UI: sneaky bugs around double-counting time for overlapping incidents, no GitHub API for incidents so you need to puppeteer-scrape the backlog of incidents to get historical data. Although, you all are right to call out that the CSS was three shots, though, and it shows :) I thought it looked so cool in ~January 2026 and now it gives me the ick, too!

    For people who are curious about how much direction went into the information architecture/presentation, it was fairly substantial. I wanted a contribution graph style viz and it took many turns to get it working the way I wanted. The swimlane viz for selected-day-incident visualization was also me, because I love swimlane graphs.

    I ended up sharing it with some folks and they wanted to reference it, so I put it on a website. So it's jokey for sure, but I take my jokes seriously! I'm grateful that people have feedback on how it can better functionally and visually :)

  • Compared to near unusable pages that large organizations produce, yes this page is highly effective at conveying information. Who cares how it was produced?

    • > Who cares how it was produced?

      Well, we're at least two people who care, since we were conversing about how good/bad the webdesign is, then you jumped in here :) If you don't care, why bother to reply to people who seemingly do care? What kind of conversation are you expecting here, "Yeah, do tooo"? :|

    • > this page is highly effective at conveying information

      Is it though? If the page is near unreadable?

      * Almost pure-black background rendering every not-pure-white colour barely readable

      * Dark-grey and low saturation colours used almost everywhere, for both fonts and other coloured elements (the orange cells in the calendar are the most readable thing)

      * Thin fonts - coupled with the dark grey colours this just adds to the readability issues

      * Yet another incredibly long info-dump of a page

      And then as far as actual information:

      * Vanity metrics as the main information, that is a lot of things with no context or historical information

      * A lot of aggregates and rollups that aren't that useful

      No, I haven't tried Reader Mode.

      It's a good demo for UI state syncing though, I'll give it that.

  • What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.

    • Here is a provocative thought - maybe these are the so-called "better designs" from LLMs? It's not like writing English sentences is some huge secret you are sitting on that no one else knows.

      1 reply →

    • Outside design systems I rarely get good CSS from LLMs.

      3D type stuff too, it's useless outside boilerplate.

      Very little spatial reasoning training, no end-user subjective reasoning inference (Google is starting to though even in unrelated chats), so it's no surprise the LLM doesn't know what you want.

      Since I don't even know what I want half the time until I saw it, the subjective reasoning piece is key - that is, being able to predict what I'll want to pretty good accuracy. Then you have your agents etc.

    • as someone who doesn't know how to get better design out of LLMs, can you elaborate?

I’m actively working on an alternative Frontend for Forgejo at the moment, completely self hostable, free, and open source.

Moving everything from GitHub to Forgejo and Tangled for now. These outages haven’t effected me for the past month because of this.

  • Can you elaborate on how your Forgejo frontend will be different than the default one? I'm asking because I've only ever used GitHub, GitLab and Forgejo for longer periods and Forgejo was the fastest and easiest to use for me.

>"The UI of that page is so nice"

Most part screen is taken by picture. Contrast ratio is really low. Hard to read Should they remove that useless banner, current status which is the most interesting part coud've been made visible right away.

I would call this whole thing highly un-ergonomic