# Een lay-out voor gemeenschapsprojecten

**URL:** <https://meta.discourse.org/t/a-layout-for-community-projects/170000>\
**Category:** Community Building\
**Created:** [13 november 2020 om 03:09 UTC](https://meta.discourse.org/t/a-layout-for-community-projects/170000 "2020-11-13T03:09:26Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manuel/32/468169_2.png) [@manuel](https://meta.discourse.org/u/manuel)\
**Post date:** [20 november 2020 om 11:19 UTC](https://meta.discourse.org/t/a-layout-for-community-projects/170000/6 "2020-11-20T11:19:04Z")

</div>

> [@angus](#):
>
> I’m curious why you chose not to use the mobile layouts view?

I’m actually just happy with the mobile view as it is. I also find it useful not to get too fancy with adaptions. So the basic navigation through the site works with the standard navigation menu.

I now looked at it and, as feedback, had some difficulties understanding how it’s supposed to work. It sounds like it’s another hard-coded html menu. I’d try to avoid that as well.

> [@angus](#):
>
> Or if you’re using the `excluded_categories` setting? I considered added an `included_categories` setting

Yes, I excluded some categories from the widget settings. And I think to include them would be more intuitive, as that’s how most settings work. Could probably populate that list with all existing categories when you first enable the widget?

Overall, I really love the discourse\_layouts plugin 🤩 and left more feedback on it’s widgets here:  
[https://thepavilion.io/t/improving-discourse-layout-widgets/3698](https://thepavilion.io/t/improving-discourse-layout-widgets/3698)

---

_[View the full topic](https://meta.discourse.org/t/a-layout-for-community-projects/170000)._
