On Tue, May 6, 2025 at 9:26 PM Joe Adams <[email protected]> wrote:
> I would be happy to help with this. While I don't do a ton of front-end > development work, I have built several Next.js sites including a static > site so I have some experience in this area. > Great to hear, I'll hit you up on Slack and then we can see what would make most sense! > Joe Adams > > On Tuesday, May 6, 2025 at 11:18:34 AM UTC-4 Julius Volz wrote: > >> Another update: I've spent the last couple of weeks evaluating a lot of >> JS-based static site building options, from Astro over Next.js to TanStack >> Start, and also had another close look at documentation-specific frameworks >> such as Docusaurus, fumadocs, Nextra, etc. I started a stub implementation >> in multiple of these to see how they would fare and quickly ran into >> various limitations given the specific needs we have for our docs site, or >> the maturity of the framework (like TanStack Start, which is probably going >> to be really nice, but is still too alpha to use). >> >> In the end, it looks like I'm going to go with a custom site built on top >> of Next.js. Reason being: >> >> * Next.js is the most popular React framework out there, so finding >> people who know it will be easier than for anything else. >> * Its router and static site export features suit the needs of the docs >> site well. >> * I can build any custom features around Markdown import / parsing / >> custom transformations, navigation rendering, etc. that I need. >> * I can use component frameworks like Mantine.dev, which wouldn't have >> been possible with something like Astro. >> >> Due to the fetching of docs from other repos and then integrating >> everything into a coherent whole, it'll probably still take a bit to finish >> this, but I'm feeling that I'm off to a decent start at least now. >> >> On Fri, Apr 25, 2025 at 2:27 PM Julius Volz <[email protected]> wrote: >> >>> Just an update on this website revamp idea and why I haven't moved >>> forward yet - of course after proposing it I started thinking about whether >>> it would be much nicer to just immediately go for a complete >>> reimplementation using a modern web stack. That brought up many issues to >>> solve, but the main one is the following: most JS docs site builders these >>> days expect MDX (Markdown with React-ish extensions) as an input format for >>> docs pages, whereas we have plain Markdown pages that not only come from >>> the current website repo, but also from historic branches of various >>> releases of Prometheus and the Alertmanager. A lot of Markdown parses fine >>> as MDX, but there are many constructs in our Markdowns that blow up the MDX >>> compiler in my experiments (like `<string>` and stuff like that). If we >>> only had current docs, that would be less of a problem (because we could >>> just adjust things there), but if we need to pull in old versions of docs >>> from other repos, then it's harder to solve. We'd either have to update the >>> docs in all the old release branches or do some kind of >>> pre-processing-patching on them to get rid of incompatibilities before >>> using them as MDX. It would still be super nice to get rid of the old >>> nanoc-based site at some point though. >>> >>> Anyway, I'm still thinking about this and how to best approach it :) >>> >>> On Fri, Sep 20, 2024 at 7:23 AM Julius Volz <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> The Prometheus homepage (prometheus.io) looks very dated by now, and I >>>> wouldn't be surprised if it turns off a lot of first-time visitors just by >>>> its looks. While I don't have the capacity to make this another major >>>> project at the moment, in lieu of a more extensive docs & homepage rework, >>>> what do people think about me just working to update the design of the >>>> landing page to make it look at least slightly more modern? I was thinking >>>> of this kind of direction (just a start): >>>> >>>> https://prometheus-new.netlify.app/ >>>> >>>> (user logos are blurry because many never provided us SVGs - this would >>>> have to be fixed) >>>> >>>> This would mainly change the landing page, although of course the fonts >>>> and a few styles would also have to be updated on other pages to make them >>>> consistent. But that should stay a minor change. >>>> >>>> I built the quick demo above using a more modern tech stack (Mantine, >>>> React + JSX, etc.) than our homepage, but I could try to backport the same >>>> styles to our old homepage framework with pure HTML + CSS. Eventually it >>>> would be really nice to port the homepage to a less medieval static site >>>> builder, but that's a much much larger project. >>>> >>>> Cheers, >>>> Julius >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "Prometheus Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/prometheus-developers/e7b603b1-43e1-4a9b-8bff-5fbfc6532fc9n%40googlegroups.com > <https://groups.google.com/d/msgid/prometheus-developers/e7b603b1-43e1-4a9b-8bff-5fbfc6532fc9n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6YoyNotfrS_EiBLaRpF4NPqt1sb29uXPiEZsn8JuxHaSnQQ%40mail.gmail.com.
