I wanted to finally make a proper thread for general site improvements. So below is my current roadmap for Inyouchuuverse in the near future! I will gradually update this as these things get implemented, and add anything I've forgotten.

Any feedback is absolutely welcome from all of you, whether feature requests or bug reports. If this list gets too long to manage, I'll make a fresh thread later. Thank you all for your patience as we make this web community happen!

Major Features Planned:

• Fully integrated wiki with universal info panels and page links from forum. I want the wiki experience to seamlessly coexist with the forum without feeling like you're on a whole different website. This means rendering straight on a forum page in the same style, using your existing logged-in session.
  One thing I would like to do is parse forum pages for exact names of wiki pages, for example "Kikuka Tsukishiro," and turn those into links to the pages with hover tips briefly summarizing the entry. A relatively unobtrusive way to promote our future all-encompassing lore reference.
  Another feature is the info panel. Lots of wikis have summary panels, and I think if I put all commonly-used attributes into the wiki page database, then users could easily search wiki pages by anything from game release dates to character hair colors.

• User Creations submission. A dedicated section, highlighted on the front page much like the news box in the beta theme, where users can submit fanart, fics, etc.
  Submissions can track likes/upvotes/kudos, and could use auto-generated hidden threads to effectively have a full comments section. Multiple pages/images/scenes would also be supported, with each having their own settings for marking NSFW or limiting to registered users only for more privacy.

• Reader for VN-style scripts. The idea here is to offer story browsing in a similar format to browsing posts in a thread, with character names/portraits and dialogue. Scenes or chapters can be separated automatically into different pages, with branching choices being possible for multiple endings. Each scene can also have its own comments section as well.
  This will eventually be one way of experiencing the upcoming fan translations, and I could add the ability for users to submit their own fanfics in VN-inspired script format.

• Optionally displaying posts as a feed. I had this idea not too long ago but I think some of you might appreciate this. An alternate display option for the main page, which instead of displaying forum categories, displays actual posts along with the last comment (or first unread comment if applicable). This would include general forum threads as well as user creations, making a layout that may be more familiar if you're used to modern social platforms. It would, of course, always be left to your choice whether to view the forum in classic category view or as a feed.

Bugs/QoL/minor edits:

• Theme integration improvements such as better dividers between threads and categories. Ongoing

• Spoiler and NSFW text block tags, with message composer buttons to add them automatically. NSFW does not show to unconfirmed guests. NSFW images should not have nested warnings, i.e. if you click open a NSFW text block, then any images within it should just get shown instead of having to click them too. Spoiler blocks will redact individual lines of text that you can mouse-over to reveal, unless the spoiler contains multiple lines or images in which case it'll get a click-to-reveal block. Spoilers are fully implemented now, NSFW still needs further implementation.

• Aojiru-themed smileys. It should also be easy enough to adapt the New Reply smileys selection box into the Quick Reply composer to make them more intuitively available in casual conversation. There are a few of them available in the extended smiley box, but this still needs to be finished and made more cohesive.

Completed Tasks:

• {DONE} Go live with the new theme! Anyone can access the beta theme now, via the dropdown in the site footer, but it's still unfinished and needs some pages worked on before I'll consider it fully usable. Once the main user experience is under the new theme and fully compatible with both desktop and tablet, I'll call it done enough to switch all users and guests over. We have officially switched over! This does mean that my bad habit of testing changes on the live site has to be with a bit more care now, but in general I think it's become a much better experience for new guests.

• {DONE} Deleted post placeholder is shifted weirdly with user info still hanging off the side. This might only be noticeable to admins, but it irritates me. Fixed! The placeholder is styled correctly and the actual post is fully hidden now.

• {DONE} Quick Reply box doesn't clear after posting. An annoying quirk I'm seeing in non-Default styles that still needs fixing. As featured in an early post below, this was a surprisingly convoluted fix that had to address two separate issues at once, but it seems to be all good now.

• {DONE} Just saw an issue where the chat Edit feature didn't populate the input box, so I overwrote my old message with a new one I tried to send. The default functionality of the RTChat plugin expects the message entry box to exist on the same scope level as the rest of the form, whereas the new theme throws it into a styled "itemborder" box. Interestingly, the plugin did not fail in this way when sending messages, only when editing, so the fix was easy to figure out.

• {DONE} Robots.txt settings against AI scrapers. Obviously this is not foolproof, since AI bros flagrantly disregard the consent of others (like demons on girls, but more tasteless), but it's at least something. Complete, we'll see how it goes.

• {DONE} Disable user registration until 18+ form is passed. It just makes sense, and since most sites don't require clicking a specific form button before registering, this will continue to be a nice hurdle for spambots. Aaaand done. Registration only works on the new theme now, so uh... I think it might be time to switch.

• {DONE} Option for vertical site layout on wide desktop. Shrinking the window or viewing on mobile forces a vertically-stacked layout for all elements, but I will also add an option to force this on wider screens for those who prefer it that way. This is now officially an option in your Edit Settings section. I may add more layout customization in the future though.

Fantastic work so far. It's like you've won a 10 year contract with a new client! Above and beyond haha.

The spoiler and NSFW buttons will be great. Now I'm not sure if this is too complicated, but I wonder if an additional spoiler "text" (only) tag is possible? Like here I will spoil

Spoiler

this

EDIT: Oh and the spoiler text is black, hard to see in the Inyouchuu custom theme.
The spacing between paragraphs looks a bit tight too? As always I'm on desktop though...

The quick post still seems a tad odd. I guess it doesn't refresh the whole thread/page though, like I think I've seen other forums do. It'll post but the quick post textbox still retains all the post right below, it throws me off a tad haha. Maybe not a big deal though since it does post and work fine in that way.

I wonder if those official Inyouchuu emoticons from the gacha game would look cute shrunken down? I know JAST has some of them on their Discord. But we added a lot more in my Inyouchuu Discord, they look cute.

Thank you! I'm so glad it's shaping up to be an enjoyable hangout zone.

Yep, I'm going to add those on the main list, as both of those concerns are things I agree with. I have a template and basic functionality for inline spoilers, basically just redacted blocks that show the text when you hover them, and just need to implement it. I think the way I want to do spoilers is put spoiled content between pipe characters like this, then have the forum software determine whether it's a single line (so just black out the text) or multiline/images (so put it under a clickable header).

100% agree on the quick reply form. I am still trying to figure out why the text does not get cleared once the reply is posted. I actually notice this same problem with blue-dark, and I think it was only clearing properly in the original default theme. Probably some tiny little element ID or scope not matching up, likely the same type of issue that's currently breaking the edit feature in the chat.

Will have to add some of those emoticons soon! I might put a few together myself from screencaps and such too.

The reader for VN-style scripts sounds like a really cool feature, looking forward to that!

Testing a thing...
...done.

Holy crap. That was a ton of trial and (multiple) errors... but the quick reply is fixed. And at least I learned a few things about the backend in the process.

The entire problem could've traced back to The Spinning Loading Circle, as it turns out. In the Default theme, there is briefly a loading spinner when you quick reply, which disappears as soon as your new post shows up. However, in several of the themes I tried including blue-dark, the spinner stayed there perpetually, even after the new post appeared. This, once I finally did some digging, is because the posting process is supposed to increment a value called visible_replies... which is defined in the templates of the default Show Thread page, and was accidentally left out of blue-dark by that subtheme's original creator. The post function hits that invalid variable, crashes and burns, and never finishes the rest of its task, which is to adjust the inline moderation ID's and blank out the Quick Reply message field.

Except... that didn't solve the problem. It took me waaaay too long - and I still don't fully understand the reason why it was like this - to realize that in the new Inyouchuu theme specifically, which uses the OverType composer, the page script actually cannot erase the OverType text area on its own. You have to call editor.setValue(''); to make it happen. So I added that, and amazingly that solved it. Now, granted, it'll hit an internal script error on blue-dark because there is no "editor" object on that one, but everything will otherwise still work as intended.

TL;DR: The Quick Reply field finally works the way it was always supposed to!

And what's the latest thing I took care of tonight? Why, inline spoilers, of course!

There is no button for it yet (in Quick Reply or the full composer), but it works the same as in Discord, that being you place two pipe characters | on each side of the desired spoiler text. Next spoiler-related improvement will be adding the full block when images or newlines occur in it.

Very cool!

Wanted to take care of

So posting this ahead of time to see the results!

Well I didn't see it in a spoiler when I first looked, but then I reloaded the page a minute ago and it was working then!

Yep, that's me executing a terrible decision to do all my experimenting on the live site!