Yeah, this is known. It'll probably be addressed when the site structure is changed to have a homepage, docs pages, and a better way of navigating around everything.
Just tried this out and I like it a lot actually! There's a couple of nitpicks before we can show it to everyone.
This needs to be a lighter red for better contrast. Try #ff6561 I guess?
This link doesn't go anywhere. I assume the site is yet to be created?
Please create a class .homeserver-question and target that instead. Using IDs in CSS sounds fine but quickly turns into hell. I know this from experience.
1 MB bundle size is kind of ridiculous. We could simply not highlight code blocks, or we could maybe inline async import the module on demand when we actually need to do highlighting, so it's out of…
That's a really good prompt message.
I'd like to use a circled ? icon next to the "homeserver" label that responds to clicking, rather than hovering, or requiring the input box to be empty. Those…
Again here. I think a better way would be to have a base class like MembershipEvent, and then for each kind of membership we subclass it and only implement the canRender method on each.
Just going through a visual analysis of your code, I'll test it and give a full review in the future.
The original idea here was that we'd have a predicate for things like whether the method can be displayed as a message group, whether it should show a timestamp, or whatever other things could affect the display based on the class. I haven't actually put this method to any use yet.
Not sure how I feel about a function that creates classes. Can we inherit from a base class instead?