UI functionality is scattered between OG UI and OG modules.

[ArchieDoe]

For example, group UI on node page (group tab) is rendered by OG module, when OG basic configs (like group type roles, permissions, etc.) are rendered by OG UI module.

Another reason is to avoid code duplication. For example, we have (or potentially have) 2 similar pages: roles overview on group type page and roles overview on specific group. To render this we basically need same code, but following current implementation it should be done in 2 separate places with different classes.

To me all UI (and adding routes) should not be accessible when UI module is disabled, as it happens with other modules, e.g. views UI or fields UI.

I suggest to move all UI related functionality, including OgAdminRoutesController and interface into OG UI module.

[ArchieDoe]

Also, decision on this part blocks me from finishing #196

[amitaibu]

Since in D8 code is better lazy loaded then D7 I wouldn't mind moving UI stuff to OG core.

[ArchieDoe]

Ok, so should we move OG UI into core then?

[amitaibu]

I think we can do that. @pfrenssen agree?

[ArchieDoe]

Yah, @amitaibu @pfrenssen, it might be a good idea to move it into main module.
For example this Gizra#231, which is also UI PR, done inside of main module

[amitaibu]

Lets have a dedicated PR to do that.

[pfrenssen]

Sounds good to me.

[MPParsley]

@pfrenssen this issue could use a new title: "Remove OG UI module"

I think merging OG & OG UI makes sense, since the UI isn't just for admin purposes like for example Field UI -- it's for the actual interaction of end users with the group functionality. I think, however it should be done in a separate PR, to keep this one from being too big.

[MPParsley]

See @amitaibu 's remark in Gizra#243 (comment)