I wanted to post some more examples of how I think this could work. I’ve communicated directly with the Fibery team on these, and I’d be curious to hear what the rest of the community thinks about these ideas:
First, there is some great handling of this feature right here in the app that hosts the community, Discourse. Here are some of the specifics I really like:
It renders an excerpt of the related post inline, so you can see a lot of the context. This is much more useful than just a link all by itself.
There is a drop down arrow that will allow the user to expand further that preview to see the entire embedded view, without having to leave the current post. That is a real boost to navigating and speed in the app.
- At the bottom of a post, there is a list of all related posts. Again very useful to see this summary.
Another source of some good ideas and approach is a new app for note-taking called Roam that is getting a lot of press roamresearch.com. The premise is to approach note-taking from a “systems” point of view, and not just a flat hierarchy of “folder” and “note.” The main feature is every note consists of a “block” of text, that can can be related to any other block or page, and also “built out” by later isolating the block and adding to it.
For example, you’d write some notes, which might include:
Plan for Customer Ramp Up:
- build out some drip Email campaigns
- Ask for $50 commitment from each lead.
These bullet points act as “blocks,” and easily get referenced into the originating doc, but later can be manipulated and built out. So you can quickly write up the concepts in an outline, and then later grab them and expand into full projects, etc.
I think this would be a great evolution of what Fibery already has in Rich Text, as each bullet is also a block. But for now we can’t do anything aside from convert into an entity - itself a nice feature - but the full referential context is still missing. Any entity now that currently gets created from these blocks has no context back to the originating block, the larger doc that contained the block, related entities created at the time. All that info is stuff I am really hoping to see around my items in Fibery as I build them out, so I can get the very best sense of importance, priority and context around work my team goes.
Thanks guys and hope you find this useful!