roadmap.sh is a very nice place to get a top level overview and maybe dig down into one or two things that you might be interested in. (I'm not affiliated, I just think it's a cool project)

Maybe :has can work here?

developer.mozilla.org/en-US/docs/W...

I guess it depends on how things look in the html but it's worth checking out.

very, very cool! Love the slider. Congrats! 🎉

Rough idea but something along the lines of:

As the user types the title for their, do an actual search based on the words they use and show them the results.

They might see some previous discussion that matches what they're looking for

These are tiny things the tech can do to make things easier

They can easily be linked to and that means less effort is wasted answering the same questions over and over.

I get that your point is not about questions per se, but I feel the same thing applies for community "events"

That's just one part though. There's a few other ideas to explore

You click on one and... magic... it gets linked in your reply.

Of course this requires a bit of content hygiene where you have those "wiki" like posts that cover a specific topic.

Still, having the editor thing as an option would encourage community owners to create said wikis because...

For now I'm very much sold on the idea of making it as easy as possible for members to point to "previous discussions"

What I mean is... the editor thinggy you use to create a reply should have a search icon that lets you type a word or two and it lists previous discussions that you can pick from

Very few projects graduate to the next stage where you have a hackable, resilient codebase for a mature project where adding (or removing) features is fun.

This is something I really want to keep in mind going forward because like you said... being able to move with your users is a great thing.

Most projects have a ton of flexibility at the MVP stage and things are really exciting, then they graduate to this "production grade" hell that takes all of the joy out of coding because you're constantly worried about breaking things and backwards compatibility and so on.

You know, I've been kind of thinking about this. What you highlighted is the main reason for "clean code"

We've kind glorified clean code for its own sake and mostly forgot why it matters in the first place. It allows you to make changes very quickly without the whole thing collapsing.

I actually love that idea! If something starts as a "forum thread" but the conversation is too heated or too quick, the software should magically have a "lock this thread and create a chat channel" thinggy.

This also relates to the other point you made about manual work, which I dislike.

Thank you!

I don't want to hear what @BigDogFreedom69 from Asshat, Nebraska has to say

why did we accept a model where his opinion is given the same weight as my best friend's by default?

I want a door i can lock

Is that too much to ask for?

we know how to build doors. We just stopped prioritizing them.

For example, you can just add a valid client id and secret for Github login and simply you adding those means "Login with Github" is now enabled.

Setting grouping is already built but I haven't add the UI for that and I wanted to get an update out with the current state.

What does this unlock? A searchable and intuitive place for the vast majority of the config. Settings can be accessed on the client and on the server.

private settings (I control that flag) are very tightly locked and will never be served to the client. This can be used for server / db stuff.

I added support for text/bool/json/number and file (upload) settings

Settings can be public (client) or private (secret stuff)

The settings are saved in the db. I seed the settings from a JSON file (that you never interact with)

I can add or remove settings and a small boot script syncs your db