If you guys move forward on this, I would find these aspects in particular useful:
Some time ago we looked at an Atlassian guide on how to use Confluence as a public-facing User Guide and it looked intriguing.
However, and I’m probably in the minority, I’d much rather see you guys prioritize some other stuff, much of which I’d call the “rough edges” of Fibery, before doing work on publishing a Fibery space to the web. My team uses Fibery for work management, and could really use some simple improvements that would avoid the daily frustrations in Fibery, before we have the ability to publish to the web, which won’t help our daily quality of life:
- Improved commenting and Notifications - discussed in various areas here already
- Fix of multitude of formatting bugs: Odd key combos, such as trying to paste in comments commits them; trying to add referenced entities when doing a soft return “shift” + “Return” puts the reference on another line, and a host of others
- Inability to create an inline entity 100% using the keyboard when typing “#”. The last few steps you can do when creating a new entity straight from the “ctrl” + “K” command with the keyboard do not work when creating inline
- Can’t see closed entities in search, but you can see them when referenced around Fibery with the strikethrough, and you can see them grayed out in Collections when typing in those fields. So it’s odd that you can’t see them in the search dialog. Request is here: Seeing “Closed” Entities grayed out in Search Dialog
- Would much rather see Bi-directional integrations/sync before pushing data to the web. Without this, I don’t really think the Fibery integrations are true “integrations,” but rather API connections that are custom built for user ease-of-use
- Dashboards - This is a feature all of my team looks for, because they expect it, but it doesn’t exist.
- Ability to create a Context View and see multiple locations of the same Entity in the cards. Context views are a very useful feature (I’m talking about filtered views that adjust for each entity in an App based on the filter). Example of this: I have a Sprint DB. I have stories connected to it. The stories have tasks. However, in each sprint I want to do some one-off tasks that don’t belong in a Story. I can set up a board that will update with each new Sprint via these Context Views. However, I can only see one “type” of the Tasks due to this limitation: Either the ones directly related to the Sprint, or the ones in Stories that are in the Sprint via lookup. This is a limitation that hurts us in various areas of Fibery, and would also be solved with Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type that also would be something I’d like too see completed before pushing the Fibery Space to the Web
- Whiteboards do not yet represent real relations. I have stopped using them for over a year waiting for this feature, as they are not useful without this. Without better integration with Fibery entities, the Whiteboard are more or less just a way to diagram within Fibery, but you can do this more elegantly with other apps, some free, and just embed into Fibery. I really hope you guys realize the potential of integrating Whiteboards with Fibery Entities. One of my favorite features of Fibery is actually the self-created “map” in the Workspace Map. Even if something like that could self-create inside apps it would be a hugely helpful feature.
I hope you guys don’t come down on me as in the past when I posted feedback, but you are asking these questions:
So I’m trying to answer all three of those!
Cheers and keep working hard to get Fibery complete (and I know most of what I mentioned above you will deliver at some point!)