@kalman thanks for your response to me!
Could you let me know, in particular, if these two requests are on your radar as far as improvements to references:
Show in Reference Highlights Referenced Entity more clearly
and
Ability to quote text across Fibery like in Discourse
This second one is such a natural extension of your existing iteration in Fibery that it would really be too bad if something like this doesn’t come into existence. With the way references are structured already, my team extensively uses #-tagging to point out other entities when writing and commenting around Fibery. We are missing however the ability to simply quote some text somewhere, and then reference that in a continued dialogue. Instead, we have to either screen shot the quoted text and past it, or use the primitive existing quotation capability, which has one huge flaw in that if you are trying to write text with a “soft” return - using “shift” + “return” in order to maintain the reference itself, the quotes won’t work because you’ll quote the entire set of text.
Here’s an example: I am commenting in an entity and I want to write a few references. I have to write like this, using “shift” + “Return” in the breaks here, or I lose the reference (because if I do a “hard” return hitting just “Return” the reference doesn’t pick up the text above the hard return):
Let’s imagine I’m commenting in an entity that is a project:
During the meeting that took place of FIRST REFERENCED ENTITY, we said:
(now I have to use a soft return or I lose the reference above to the meeting)
THIS PROJECT (the entity I’m commenting in) is going to be late 2 weeks. This is due to the issue raised in NOW THIS IS ANOTHER ENTITY, LET’S CALL IT AN “INCIDENT” ENTITY by user x…AND NOW HERE I’D LIKE TO QUOTE THE COMMENT IN THAT OTHER ENTITY I JUST MENTIONED
if I want to actually put the quote from the other entity here with Fibery quotes, I’ll wind up quoting everything above, unless I do a hard return. But if I do the hard return, the above references are lost
I hope I’ve explained this right and I’m eager to get your response, thanks again!