Apache Wicket VS zk

Sort of sounds like Apache Wicket (https://wicket.apache.org/). I used it for a few projects in the mid-late 2000s. I really liked it being server side and the concept of having object-oriented HTML (code paired with HTML snippets). I haven't had a need to use it since 2014, so haven't kept up with the project.

You can use Java for Backend and Frontend. A relative new kid on the block for Frontend is Qute. The general keyword you are searching for is Java Templating Engine. Specific examples would be Thymeleaf or FreeMarker. There are some framework, which offer a lot more than templating like Vaadin or Wicket. Some are just specifications like Jakarta Faces with some of their implementations MyFaces or Mojarra.

Perhaps, a good competitor for JSF is Apache Wicket.

I have used https://wicket.apache.org/ in the past and I think it matches your needs. It's a simple mvc that focuses on the actual java code writing and uses html only on the layout of your components in your page.

Is this the Wicket you're referring to? https://wicket.apache.org/

What's the best intro you know to how it's components work, and the benefits and tradeoffs over other approaches?

You should consider Apache Wicket. It is widely used for business apps.

I think Apache Wicket takes a similar approach for Java? https://wicket.apache.org/

I like the approach, and it's good to see more projects in this space.

I believe Wicket is somewhat similar (and still actively developed).

https://wicket.apache.org/

I use org-mode with the journal plugin, but I'm soon going to switch to zk[0]. My technique is called interstitional journaling[1], and I just keep track of my location (I travel a lot) and the date, which gets generated by org. You can set up an interstitional journal in anything though, Logseq[2] supports it out of the box.

[0] (https://github.com/mickael-menu/zk)

Personally, I'm using zk for now. What's nice about is that it aims to be a common-denominator between all the popular zettelkasten markdown formats out there. So the notes you write with it will be forward-compatible with many other note-taking apps like Obsidian.

If you want to go full terminal workspace - you could use Zk (https://github.com/mickael-menu/zk) + editor of your choice. It is just markdown under the hood, but it comes with quite a few good features that majority of the tools have now (tags, backlinks, front matter, templates, etc). I wrote a post about my setup literally yesterday (it was a bit more editor oriented though) https://www.reddit.com/r/HelixEditor/comments/144x6r3/escape_hatch_xd/

I selected Helix as it is phenomenally fast, I love out of the box feature set, key bindings are intuitive and it looks sick :) To manage my notes I found ZK - very cool CLI with extensibility in mind.

I use https://github.com/mickael-menu/zk

For now, with a couple aliases wrapping nb as I try it out. I'm also planning to give https://github.com/mickael-menu/zk a shot, it looks to be almost exactly what I'm looking for an offers a vim plugin to boot.

mds is grepping notes' names and items' names (links and code snippets). and also moving forward/backward along the graph. I used to use https://github.com/mickael-menu/zk, it was messing me up, giving too much info, each line of every file.

Big fan of zk and zk-nvim. The biggest drawback was that link insertion depended on cmp, but now there's work to add linking as a direct LSP command. I've been using that since it's been merged in, and it makes creating and linking notes on the fly a breeze!