Post History

> Now that there is a separate [Proposals site](https://proposals.codidact.com) with its own Meta and other categories, that would seem to qualify as a separate "Codidact Community" which should be listed among the "Other Codidact Communities" in the standard page footer. (Since this footer also always lists the *current* community, maybe it should just say "Codidact Communities"?) But it doesn't. It also doesn't appear on the main list of communities on https://codidact.com/ . 

I agree. The following three places should show the same list of communities:
- The "Communities" drop down panel at the top right of each page.
- The "Other Codidact Communities" list in the page footer.
- The "Communities" page at [codidact.com](https://codidact.com).

Personally, I would also like the list to be consistent in the [dashboard](https://meta.codidact.com/dashboard) (available from the 3 by 3 block of squares icon at the top right of each page, or the [hamburger menu](https://en.wikipedia.org/wiki/Hamburger_button "An icon with three stacked horizontal lines, looking vaguely like a hamburger") on mobile). However, there is a separate discussion about whether to include Collab in the other lists (it is present on the dashboard):
- [Codidact Collab - should it be listed?](https://meta.codidact.com/posts/287378)

The new Proposals community is already present on the dashboard.

> This makes the process less discoverable than it should be; people will come to the Meta community and see a "Site Proposals" category, only to be directed somewhere else.

Once the new Proposals community is sufficiently discoverable, I would expect the old "Site Proposals" category to be removed. I'm not sure if there is a plan for this. Depending on how smooth the transition needs to be, the process may be non-trivial, so I've posted a separate Meta question for discussion of [How should we phase out the Site Proposals category?](https://meta.codidact.com/posts/289626).

> Aside from that, clicking the button labelled "Not here (use new site)"... doesn't lead to the new site; it brings up an error message instead (which just says "You don't have a high enough trust level to post in the Site Proposals category."). This seems like not the best possible UX. If this button can receive custom text, it should be possible to give it a custom URL as well.

The text of the button is customisable so that it can reflect the type of post that will be created:
- "Create Post" in Meta's Blog category.
- "Post Recipe" in Cooking's Recipes category.
- "Post Challenge" in Code Golf's Challenges category.

However, the action of the button is not customisable - it is always creating a post of some kind.

Since this is the only time I can imagine a use for customising the button action, it doesn't seem worth changing the code. Once the "Site Proposals" category is phased out, the button problem will be gone, and there will never be a need for such a category again, thanks to the new Proposals community.

The renaming of the button is a temporary workaround as a hint to people who may be confused at not being permitted to post in the "Site Proposals" category anymore. I agree it is far from ideal, but I'd prefer to see effort focused on phasing out the category rather than improving the temporary workaround. That is, I'd prefer a solution rather than a better compromise.