# Journal Plugin

**URL:** https://meta.discourse.org/t/journal-plugin/317785
**Category:** Plugin
**Tags:** pavilion, broken, experimental
**Created:** [July 23, 2024, 9:04am UTC](https://meta.discourse.org/t/journal-plugin/317785 "2024-07-23T09:04:50Z")
**Posts on this page:** 1
**Showing post:** 49

<div class="post-metadata">

### Author: ![jrgong](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@jrgong](https://meta.discourse.org/u/jrgong)
#### Post date: [November 9, 2025, 4:06am UTC](https://meta.discourse.org/t/journal-plugin/317785/49 "2025-11-09T04:06:58Z")

</div>

Here is the repo.  
It’s all been done via LLM coding and uses a lot of workarounds and hacky methods, and in general, it might be a cleaner implementation to do it as a plugin. But as a proof of concept, it gets the job done so far (some edge cases not fixed yet, like toggle button state persistence after some user actions).

[https://github.com/jrgong420/log-view](https://github.com/jrgong420/log-view)

What’s really missing here so far and only possible via plugin:

- Remove topic owner posts which are replies to other posts from PostStream
- Disable for topic owner to create a-reply posts (and for all other users, disable creating non-reply posts)
- Adjust “has new post(s) state” of topics so that only topic-owner non-reply posts (aka journal entries) trigger notifications, etc
- Allow multiple journal authors (on a per-user base) for a single topic
- Auto expand X embedded posts (aka replies)

Other ideas for further development:

- Create and autom. update a TOC/Index in first post for all journal entries

---

_[View the full topic](https://meta.discourse.org/t/journal-plugin/317785)._