Your site is preparing to East
Domestic users can click east.xjtu.app or the ❯ at the top of the site to try it out be test
Domestic users can click east.xjtu.app or the ❯ at the top of the site to try it out be test

Added reply functionality
The interface is too ugly
Developed for 12 hours and only this much content, is this
The prototype is available, feel free to test.
The page does not refresh after replying
The editor that expands when clicking the restore button on the bottom post is off-screen, requiring manual scrolling down.
Nighttime development feels great, but I still have to work tomorrow, damn.
I feel I’m getting a bit addicted to doing this
Sleeping at work
Tech Drug ![]()
GitHub is unregistered, suspected of illegal activity, exercise caution.
You were born to break the law
Once I have the online count, I’ll know who’s talking trash. I’ll write it down for you.
Is it written in the small notebook?
Updated again today, mainly includes:

Things to do tomorrow:
Show list
Show syntax highlighting via highlight.js
Turns out you can’t tick the admin’s to‑do event ![]()
When using the manager alias user identity, you can only edit manager alias posts.
Today I completed yesterday’s plan, and
No plans for tomorrow; as usual I’ll go out on the weekend, staying at home is easy yu yu.
Today added a small feature: on the topic page, clicking the top ❯ navigates to the topic corresponding to East, and on East clicking 〈 navigates to the West topic.
Recently encountered some setbacks, feel like I can’t solve them, so I created a branch for others / future handling.
Discourse will initially convert a post’s markdown to HTML, the result is called cooked. In my code I directly display it using Svelte’s {@render children()}. To support the following features, I need to do post‑processing after all components have mounted, but I haven’t found where to write the post‑processing code yet.
When visiting a topic, etc., my <Post> recursively mounts all replies. Mermaid’s render() is an async function; while debugging I found that mermaid code blocks were rendered multiple times, resulting in the render output not being an SVG
.
I convert cooked to a DOM, manipulate it with domutils, convert it back to HTML, then use Svelte’s render(). Then in the post‑processing code I modify the <iframe>.
Branch:
https://github.com/fokx/svelte-forum/tree/support-mermaid-and-embed-pdf