# Org-roam major redesign

**URL:** <https://org-roam.discourse.group/t/org-roam-major-redesign/1198>\
**Category:** Development\
**Created:** [January 23, 2021, 1:17pm UTC](https://org-roam.discourse.group/t/org-roam-major-redesign/1198 "2021-01-23T13:17:57Z")\
**Posts on this page:** 1\
**Showing post:** 191

<div class="post-metadata">

**Author:** ![bruce](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@bruce](https://org-roam.discourse.group/u/bruce)\
**Post date:** [March 31, 2021, 10:45am UTC](https://org-roam.discourse.group/t/org-roam-major-redesign/1198/191 "2021-03-31T10:45:41Z")

</div>

I broke off another separate thread, to talk about UI/UX and annotation/affixation.

> [@Find node UI possibilities for v2](https://org-roam.discourse.group/t/find-ui-possibilities-for-v2/1422):
>
> Introduction Theoretically, the number of candidates could increase a fair bit with sub-file nodes, but the current search UI only allows you to search on, and see, titles, and to see tags in the annotations. How should this UI ideally work? Completing-read and annotation/affixation possibilties I’ve been working on a [project](https://github.com/bdarcus/bibtex-actions) to adapt bibtex-completion for completing-read, and so have been deep in the details of that, some of which might relate to org-roam v2. The use case there is you have o…

---

_[View the full topic](https://org-roam.discourse.group/t/org-roam-major-redesign/1198)._
