Michael Ehling's dashboard

Background
When working within bLADE Wiki, I often am jumping from one page to another to capture a thought, idea, to do, etc. even when I'm not necessarily complete on the original page. After a while, I notice I may forget to complete work on the original page.

How it works now
Of course, you might be saying, "Er...can't you just use the back button to return you to prior pages?" Yes, and I do. If I know I have a quick edit to do on another page I'll either use the "back" button or bookmarks (remembering to remove the bookmark ASAP).

It's for the times when "life gets in the way" after I jump or navigate away from unfinished work on a page that I get "lost." It could be a phone call, another idea or thought, or some other "shiny object" that puts more distance between me and that original page. And I end up either forgetting completely or having a gnawing feeling that I've forgotten something.

How it could work
Let's have a dockable (Ctrl-Alt-H) "History" panel that shows links to the pages visited in time sequence. Let's also have a button that lets us clear that history as needed.

This way, I could occasionally scan the list of pages to see what, if anything, needs completion. After completing any work on these pages, I'd clear the history.

Alternatives
If not implemented, I'd stick with my current "back-button-and-bookmarks" approach.

I request an ability to nest inner BACKLINK markups with the recursion limited by the "nested pages supported" preference.

Example, for a page called AllMyLists with this markup

[^Page A]
[^Page B]
[^Page C]

and when Page A, Page B, and Page C all have this markup:

[^$BACKLINKS]


let the AllMyLists page show a list of links to Page A, then Page B, then Page C.

Today, the output for such markup would create repeated copies of backlinks to AllMyLists.

Thanks!

What if there was a bladewiki markup command that generated a list of links to pages containing s specified string?

Something like

[^%TAGS%=search string]


would give us the ability to define a page or section of a page that, when displayed or printed, would dynamically show a list of related pages.

We could use this to, for instance, create a navigable "saved search". We could also use it to collect in one location a view of GTD-like next actions by context (or priority or project...).

Example:

[^%TAGS%='@email']


would insert a list of links to all pages that contain the string @email