# Advice needed for tailoring Discourse to my organisation

**URL:** <https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571>\
**Category:** Support\
**Created:** [2017年十月22日 17:04 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571 "2017-10-22T17:04:59Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Alexander\_Wright](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander_wright/32/119518_2.png) [@Alexander\_Wright](https://meta.discourse.org/u/Alexander_Wright)\
**Post date:** [2017年十月24日 12:51 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571/21 "2017-10-24T12:51:23Z")

</div>

> [@codinghorror](#):
>
> Hundreds of categories (particularly low-hundreds) isn’t ideal but it is possible and should perform reasonably. It’s when you get to thousands of categories that it starts being a Very Bad Idea.

We’re running on an AWS instance, and happy to move to a larger one as required.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2017年十月28日 06:32 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571/22 "2017-10-28T06:32:37Z")

</div>

A larger aws instance will not resolve the fairly severe client implications

We send json for every category a client has access to on initial payload, categories page can get very painful, hamburger menu, category selector when creating topics and so on

---

<div class="post-metadata">

**Author:** ![Alexander\_Wright](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander_wright/32/119518_2.png) [@Alexander\_Wright](https://meta.discourse.org/u/Alexander_Wright)\
**Post date:** [2017年十月29日 07:59 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571/23 "2017-10-29T07:59:19Z")

</div>

Hmm, interesting.

Since the vast majority of people will only have access to one branch and region, it’s the moderators who will pay this penalty.

Time to fire up a test site, and determine the extent of the problem. A good opportunity to validate our backup procedure too 😄

---

<div class="post-metadata">

**Author:** ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)\
**Post date:** [2018年九月25日 05:23 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571/24 "2018-09-25T05:23:02Z")

</div>

(not?) Sorry to bump revive this: how is this endeavor working for you? Is the perf bad?

---

<div class="post-metadata">

**Author:** ![Alexander\_Wright](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander_wright/32/119518_2.png) [@Alexander\_Wright](https://meta.discourse.org/u/Alexander_Wright)\
**Post date:** [2018年十月8日 13:53 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571/25 "2018-10-08T13:53:02Z")

</div>

I’m afraid that due to illness, I’ve not progressed this beyond a dozen branches at the moment.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [2021年六月25日 17:42 UTC](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571/26 "2021-06-25T17:42:42Z")

</div>



[上一頁](https://meta.discourse.org/t/advice-needed-for-tailoring-discourse-to-my-organisation/72571.md?page=1)