Re: Time for an updated CCG website?

Apologies, forgot to attach this.

On Mon, Jul 7, 2025, 05:05 Will Abramson <will@legreq.com> wrote:

> Hey Manu,
>
> Thanks for this, I agree the website is definitely an improvement.
>
> Not reviewed it in depth but a couple of minor things:
>
> The drop-down burger menu is wonky on mobile. See attached
>
> Might be good to put the CCG call time in CET and Pacific as well.
>
> Finally, and this could be later. One of the hardest parts of any website
> is not creating it, but maintaining it over time. And doing so in a way
> that does not place the burden on the person who created it.
>
> One thing we could explore is statically generated content from markdown
> files in a GitHub repo. Thinking this might be especially useful for things
> like having a page for each work item currently active.
>
> The main content is probably fine as just inline html. Hopefully this
> doesn't need to change much.
>
> Thanks again,
> Will review more deeply once I'm back home,
> Will
>
>
>
> On Sat, Jul 5, 2025, 18:48 Manu Sporny <msporny@digitalbazaar.com> wrote:
>
>> Hey folks,
>>
>> Our website is looking a bit long in the tooth these days... much of
>> the information is out of date and that's never a good thing for a
>> vibrant community such as ours to communicate to the outside world.
>>
>> Completely unrelated, but in parallel, tech CEOs selling AI are very
>> excited about this whole "vibe coding" thing and firing the very
>> people that helped build their companies for them. While I don't
>> expect that sentiment to age well, I'm also excited by the prospect
>> that I might be able to fire myself from the more mundane parts of the
>> job... like creating content explaining exactly what we do here, but
>> then spending hours fighting with CSS. :P
>>
>> Putting those two things together, I tried vibe coding a new
>> minimalist CCG website. As you can probably imagine, it was an awful
>> experience... 15 minutes to generate the website, and then four hours
>> to undo many of the small but terrible things the AI did... but maybe
>> that's better than the two days it might have taken to pick the
>> appropriate set of modern technologies, write the content, fight with
>> CSS (kidding, fighting CSS would've taken four days for that alone),
>> and get the site published. One of the requirements is maintainability
>> (simple enough for someone to edit a file in HTML and then have the
>> system build/publish the new website).
>>
>> I'm not shooting for "great" here... just "better than what we have".
>> Circulating this before it's ready to see if we should keep going...
>> the content could be better, some of the links are broken, it's more
>> minimal than we probably want in time, but it probably has the basics
>> (how to join, when we meet, link to our calendar, and github
>> repository, etc.). It's at a temporary link for now:
>>
>> https://msporny.github.io/w3c-ccg-website/
>>
>> compare that to our current website:
>>
>> https://w3c-ccg.github.io/
>>
>> ... which one would people prefer? If the new one is good enough for
>> now, I can clean it up, move it over to CCG, and publish it. We can
>> improve over the coming weeks. In time, we can have links to the list
>> of global standards we've created together, as well as the list of
>> work items being incubated.
>>
>> -- manu
>>
>> --
>> Manu Sporny - https://www.linkedin.com/in/manusporny/
>> Founder/CEO - Digital Bazaar, Inc.
>> https://www.digitalbazaar.com/
>>
>>