Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Now that there is a separate Proposals site 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 Co...
#3: Post edited
by
trichoplax
·
2023-09-06T18:49:37Z (about 1 year ago)
Add `https://` to link as it was previously being treated as internal, giving a 404 error
Now that there is a separate [Proposals site](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/ .- 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.
- 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.
- 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/ .
- 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.
- 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.
#2: Post edited
by
Karl Knechtel
·
2023-09-05T22:14:41Z (about 1 year ago)
Now that there is a separate [Proposals site](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"?)Currently, the process is 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.- 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.
- Now that there is a separate [Proposals site](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/ .
- 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.
- 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.
#1: Initial revision
by
Karl Knechtel
·
2023-09-05T22:13:04Z (about 1 year ago)
Discoverability for the new Proposals site
Now that there is a separate [Proposals site](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"?) Currently, the process is 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. 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.