# Org-roam major redesign **URL:** \ **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:** 58
**Author:** ![jethro](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jethro](https://org-roam.discourse.group/u/jethro)\ **Post date:** [February 13, 2021, 5:47am UTC](https://org-roam.discourse.group/t/org-roam-major-redesign/1198/58 "2021-02-13T05:47:46Z")
> [@agibragimov](#): > > Do we have updated instructions somewhere for recommended shapes for `org-roam-capture-templates` , `org-roam-capture-ref-templates` , and `org-roam-dailies-capture-templates` so they work nicely with v2? Will get this right before releasing v2. Might use a self-written version of org-capture. > [@agibragimov](#): > > As I understand, those who get Org-roam from MELPA automatically start using v2, right? Yes. > [@agibragimov](#): > > How would the re-design affect org-roam-server? Does it mean that the links to headlines would also be displayed in the graph? Queries will need to be rewritten to match the new schema. Links to headlines WITH IDS (nodes) can be displayed in the graph. > [@agibragimov](#): > > How can we (non-maintainers) help? Do you think getting Org-roam from `v2` branch directly would help flushing out the bugs early, or it’s expected that many things would break there and staying pointed to `master` is safer? You’re free to try the V2 branch, which should work with knowledge bases that already use UUIDs. At this time I think the backlinks buffer is much more functional already. But there aren’t any docs yet, so it might be a bit difficult to get started. I’ll send a note here when I think it’s ready for public testing. --- _[View the full topic](https://org-roam.discourse.group/t/org-roam-major-redesign/1198)._