addorai

6 ms·

1. 1.▲
   by addorai 5y ago

   Thanks! We forked this version of ProseMirror built by the Outline team which was the closest to what we wanted for our product https://github.com/outline/rich-markdown-editor
2. 2.▲
   by addorai 5y ago

   The workflow that many teams use (myself included) is to iterate on detailed requirements in a doc, often in a table. They do this so that they can iterate on them in a more collaborative place vs Jira/Linear. It's also more acces
3. 3.▲
   by addorai 5y ago

   This is a great point. It's particularly useful to have that context into how the thinking evolved when you're looking back at a feature built months or years ago, to help you avoid doing something that was skipped in good reason
4. 4.▲
   by addorai 5y ago

   Sorry, I should have been more clear. In Confluence you can highlight content and create a ticket - it just prefills the title of the ticket to be the highlighted content. You still have to fill in the description. Then after pushing it to
5. 5.▲
   by addorai 5y ago

   Thanks! We're exploring additional integrations with tools like Asana, ClickUp, and also Github to track features thru code complete.
6. 6.▲
   by addorai 5y ago

   Interestingly, Confluence doesn't have a 2 way sync with Jira. You can embed Jira tickets but you can't push content from Confluence to Jira and automatically create tickets. Aside from that, we've designed Fable to be cust
7. 7.▲
   by addorai 5y ago

   Our team is across several time zones and we're all well versed in the product of course :)
8. 8.▲
   by addorai 5y ago

   Haha yes, it was quite the challenge! Most of the time it just works, but in rare situations we'll ask the user to pick b/w the Fable version and the version on their issue tracker.
9. 9.▲
   by addorai 5y ago

   Productboard does a great job helping prioritize features based on customer feedback. Fable comes in when you want to define how that feature should work. We let teams collaborate on rich product specs for those features, then sync it ove
10. 10.▲
    Launch HN: Fable (YC W21) – Collaborate on product specs, sync to issue trackers

    58 points by addorai 5y ago|21 comments
11. 11.▲
    by addorai 5y ago

    Thanks for the feedback! We're excited about the 2 way sync as well since we want to prevent divergent sources of truth. We've used Confluence in the past. We're designing Fable specifically for the use cases that product tea
12. 12.▲
    Show HN: Fable – sync product docs with Jira(loom.com)

    3 points by addorai 5y ago|2 comments
13. 13.▲
    by addorai 6y ago

    Thanks! That's a great suggestion, we'll keep it in mind.
14. 14.▲
    by addorai 6y ago

    We'd love to hear your feedback on how we can make the Fable add on better - it syncs user stories in your Google Doc spec with Jira. You can check it out here: https://www.tryfable.com/docs-add-on
15. 15.▲
    by addorai 6y ago

    We'd love to hear your feedback on how we can make our add on better - it syncs user stories in your Google Doc spec with Jira. You can check it out here: https://www.tryfable.com/docs-add-on
16. 16.▲
    Show HN: Fable – Spec as the Source of Truth

    2 points by addorai 6y ago|1 comments
17. 17.▲
    Launch HN: Fable (YC W21) - Spec as the Source of Truth

    3 points by addorai 6y ago|3 comments