3 replaced http://meta.movies.stackexchange.com/ with https://movies.meta.stackexchange.com/
source | link

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, NicaelNicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anywayuncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, Nicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, Nicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?

2 Corrected link target
source | link

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, Nicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anywayuncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, Nicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, Nicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?

1
source | link

We already have two topics discussing it on M&TV, which is the appropriate place for this.

First, in February 2015, Nicael asked that they be uncapped and the overwhelming response was "NTY, we like them in caps":

Then, in April 2015, they were uncapped anyway, "by design". The answer from Kurtis reads:

Along with the new profile, we've been been converting sites across the Stack Exchange network to a new CSS framework. As we have been doing this there is an ongoing critical rethinking of which site elements should be custom per site vs. which should be standard across all sites. The community bulletin is one of those items that we felt wasn't necessary to customize—this makes it more of a global network feature and more recognizable to users who visit more than one of the SE sites. Plus it makes it easier to launch new features around the bulletin in the future. I apologize for the lack of communication around the change, it was not intentional.

I'm not certain why the rest of them were not similarly reduced to mixed case but, certainly this should be an issue brought up on M&TV Meta, not on Meta.SE?