Remove Twitter links (#1696)

astro.config.ts

@@ -26,12 +26,12 @@ const plugins = [
 			conaclos: {
 				name: "Victorien Elvinger",
 				picture: "https://avatars.githubusercontent.com/u/2358560?s=96&v=4",
-				url: "https://twitter.com/Conaclos",
+				url: "https://bsky.app/profile/conaclos.bsky.social",
 			},
 			ema: {
 				name: "Emanuele Stoppa",
 				picture: "https://avatars.githubusercontent.com/u/602478?v=4",
-				url: "https://twitter.com/ematipico",
+				url: "https://bsky.app/profile/ematipico.xyz",
 			},
 			team: {
 				name: "Biome Core Team, Biome Maintainers",
@@ -551,7 +551,6 @@ export default defineConfig({
 			social: {
 				discord: "https://biomejs.dev/chat",
 				github: "https://github.com/biomejs/biome",
-				"x.com": "https://twitter.com/biomejs",
 				mastodon: "https://fosstodon.org/@biomejs",
 				openCollective: "https://opencollective.com/biome",
 				youtube: "https://youtube.com/@Biomejs",

src/content/docs/blog/annoucing-biome.mdx

@@ -24,7 +24,6 @@ Biome is **led and maintained** by the same people that maintained Rome so far.
 - [Github organization](https://github.com/biomejs)
 - [Official repository](https://github.com/biomejs/biome)
 - [Official discord server](https://biomejs.dev/chat)
-- [Official twitter account](https://twitter.com/biomejs)
 
 ## Background
 

src/content/docs/blog/biome-v1-7.md

@@ -270,4 +270,4 @@ _GraphQL_](https://github.com/biomejs/biome/issues/1927) and [YAML](https://gith
 
 If Biome is valuable to you or your company, consider donating monthly to our [Open Collective](https://opencollective.com/biome). You can also [sponsor us on GitHub](https://github.com/sponsors/biomejs). This is important for the sustainability of the project.
 
-Follow us on [our Twitter](https://twitter.com/home) and join [our Discord community](https://biomejs.dev/chat).
+Follow us on [our BlueSky](https://bsky.app/profile/biomejs.dev) and join [our Discord community](https://biomejs.dev/chat).

src/content/docs/blog/biome-v1-9.md

@@ -34,7 +34,7 @@ We gained sponsorship, notably [Shiguredo](https://shiguredo.jp/), [l2BEAT](http
 
 We also gained many new contributors. Contributors who have made a significant contribution are regularly invited to join the Biome team. We started with a team of 5 core contributors, and we are now a team of [8 core contributors and 10 maintainers](https://github.com/biomejs/biome/blob/main/CONTRIBUTING.md#current-members).
 
-In June 2024, Biome won the [JSNation's productivity booster Open Source Award](https://x.com/thejsnation/status/1805561129915060248).
+In June 2024, Biome won the [JSNation's productivity booster Open Source Award](https://osawards.com/javascript/2024).
 
 ## Biome v1.9
 

src/content/docs/blog/biome-wins-prettier-challenge.md

@@ -31,7 +31,7 @@ yarn upgrade --exact @biomejs/[email protected]
 Biome formatter has now **over 96% in terms of compatibility
 ** against [Prettier](https://prettier.io/)! This score is computed for JavaScript, TypeScript, and JSX formatting.
 
-Merit of challenge that was launched by [Christopher Chedeau](https://twitter.com/Vjeux/status/1722733472522142022), one of the Prettier's creators.
+Merit of challenge that was launched by [Christopher Chedeau](http://blog.vjeux.com/), one of the Prettier's creators.
 
 The challenge attracted the attention of many people, and some of them decided to contribute to Biome to claim part of the bounty. I did see something amazing: contributors had an amazing coordination, they took ownership of the tasks and delivered the solution in a matter of hours.
 

src/content/docs/formatter/option-philosophy.md

@@ -25,7 +25,7 @@ Leaning on the [Prettier Option Philosophy](https://prettier.io/docs/en/option-p
 
 > …[these] are not the type of options we’re happy to have. They cause a lot of bike-shedding in teams, and we’re sorry for that. Difficult to remove now, these options exist as a historical artifact and should not motivate adding more options (“If *those* options exist, why can’t this one?”).
 
-However, when the [Prettier Challenge was announced](https://twitter.com/Vjeux/status/1722733472522142022), Biome decided to accept the challenge, which required implementing all of the configuration options that Prettier had to achieve full compatibility.
+However, when the [Prettier Challenge](https://console.algora.io/challenges/prettier) was announced, Biome decided to accept the challenge, which required implementing all of the configuration options that Prettier had to achieve full compatibility.
 
 Biome still shares Prettier's philosophy about these options and considers them a legacy feature for compatibility rather than a baseline feature set. Their existence does not indicate that more options will be added, nor should they be used as a rationale to support the existence of other options in the future.
 
@@ -35,4 +35,4 @@ Much like Prettier, Biome believes the current set of options is stable, suffici
 
 That said, even as Biome has established itself as a capable and robust formatting tool, it is also still relatively new, meaning there is plenty of opportunity to pave the way for new advancements and ideas that may not seem feasible otherwise.
 
-The formatting style of Biome is also considered relatively stable, continuing to match Prettier as much as possible, with [few intentional deviations](https://github.com/biomejs/biome/issues/739). Changes to the style of Biome may be considered and implemented. Still, these are also unlikely to become configurable options and would instead be applied universally for all future versions of Biome.
+The formatting style of Biome is also considered relatively stable, continuing to match Prettier as much as possible, with [few intentional deviations](https://github.com/biomejs/biome/issues/739). Changes to the style of Biome may be considered and implemented. Still, these are also unlikely to become configurable options and would instead be applied universally for all future versions of Biome.

src/content/docs/fr/index.mdx

@@ -198,9 +198,9 @@ import NumberOfRules from "@/components/generated/NumberOfRules.astro";
         <Icon name="github" />
         <p>GitHub</p>
       </a>
-      <a href="https://twitter.com/biomejs" class="x">
-        <Icon name="x.com" />
-        <p>Twitter</p>
+      <a href="https://bsky.app/profile/biomejs.dev" class="blueSky">
+          <Icon name="blueSky" />
+          <p>BlueSky</p>
       </a>
       <a href="https://fosstodon.org/@biomejs" class="mastodon">
         <Icon name="mastodon" />

src/content/docs/index.mdx

@@ -210,18 +210,14 @@ import AwardBanner from "@/components/AwardBanner.astro"
                 <Icon name="github"/>
                 <p>GitHub</p>
             </a>
-            <a href="https://twitter.com/biomejs" class="x">
-                <Icon name="x.com"/>
-                <p>Twitter</p>
+            <a href="https://bsky.app/profile/biomejs.dev" class="blueSky">
+                <Icon name="blueSky" />
+                <p>BlueSky</p>
             </a>
             <a href="https://fosstodon.org/@biomejs" class="mastodon">
                 <Icon name="mastodon"/>
                 <p>Mastodon</p>
             </a>
-            <a href="https://bsky.app/profile/biomejs.dev" class="blueSky">
-                <Icon name="blueSky"/>
-                <p>BlueSky</p>
-            </a>
         </div>
     </div>
     <div class="connect">

src/content/docs/ja/formatter/option-philosophy.md

@@ -21,11 +21,11 @@ BiomeはPrettierとの高い互換性を誇り、ユーザーの移行プロセ
 
 Biomeは、最初はJavaScriptエコシステムで最も一般的で議論の的になっているスタイルガイドラインをターゲットにした設定オプションからスタートしました：インデントスタイル（タブ対スペース）、インデント幅（タブに等しい2スペース、または4スペース？）、セミコロンの強制。これらの点に対するオプションを追加することは、ほとんどの人々のニーズに十分対応すると考えられ、他のオプションを追加することは強く検討されませんでした。
 
-[Prettierのオプションに対する考え方](https://twitter.com/Vjeux/status/1722733472522142022)に基づき、Biomeは新たなスタートを切るチャンスがあり、Prettierが `--bracket-same-line` や `--arrow-parens` などの既存のオプションで陥った落とし穴を避けることができました：
+[Prettierのオプションに対する考え方](https://console.algora.io/challenges/prettier)に基づき、Biomeは新たなスタートを切るチャンスがあり、Prettierが `--bracket-same-line` や `--arrow-parens` などの既存のオプションで陥った落とし穴を避けることができました：
 
 > ...これらのオプションについては、私たちは保持していることを望んでいません。チーム内で多くの議論を引き起こしており、それを申し訳なく思っています。今では削除するのが難しいため、これらのオプションは歴史的な成果物として存在しており、他のオプションを追加するための動機付けにはなりません（「これらのオプションが存在するなら、なぜこのオプションはダメなのか？」といったような）。
 
-しかし、[Prettier Challengeが発表](https://twitter.com/Vjeux/status/1722733472522142022)された際、Biomeはこのチャレンジを受け入れることにし、Prettierが持つ全ての設定オプションを実装して完全な互換性を達成する必要がありました。
+しかし、[Prettier Challengeが発表](https://console.algora.io/challenges/prettier)された際、Biomeはこのチャレンジを受け入れることにし、Prettierが持つ全ての設定オプションを実装して完全な互換性を達成する必要がありました。
 
 ただ、BiomeはPrettierと同じ考え方を共有しており、これらのオプションは互換性のためのレガシー機能として考えています。これらのオプションは、さらに多くのオプションが追加されることを示すものではなく、将来的な他のオプションの存在を裏付ける根拠として使用されるべきではありません。
 

src/content/docs/ja/index.mdx

@@ -198,9 +198,9 @@ import AwardBanner from "@/components/AwardBanner.astro"
         <Icon name="github" />
         <p>Github</p>
       </a>
-      <a href="https://twitter.com/biomejs" class="x">
-        <Icon name="x.com" />
-        <p>Twitter</p>
+      <a href="https://bsky.app/profile/biomejs.dev" class="blueSky">
+          <Icon name="blueSky" />
+          <p>BlueSky</p>
       </a>
       <a href="https://fosstodon.org/@biomejs" class="mastodon">
         <Icon name="mastodon" />

src/content/docs/pt-BR/formatter/option-philosophy.md

@@ -25,7 +25,7 @@ Tomando por base [a filosofia de opções do Prettier](https://prettier.io/docs/
 
 > …[essas] não são opções que gostamos de oferecer. Elas causam muitas discussões inúteis nas equipes, e lamentamos por isso. Difíceis de remover agora, essas opções existem como um artefato histórico e não devem motivar a adição de mais opções ("Se *essas* opções existem, por que esta não pode existir também?").
 
-No entanto, quando o [Desafio do Prettier foi anunciado](https://twitter.com/Vjeux/status/1722733472522142022), o Biome decidiu aceitar o desafio, o que exigia a implementação de todas as opções de configuração que o Prettier já oferecia para obter compatibilidade total.
+No entanto, quando o [Desafio do Prettier foi anunciado](https://console.algora.io/challenges/prettier), o Biome decidiu aceitar o desafio, o que exigia a implementação de todas as opções de configuração que o Prettier já oferecia para obter compatibilidade total.
 
 O Biome ainda compartilha a filosofia do Prettier sobre essas opções e as considera um recurso legado para compatibilidade, em vez de um conjunto de recursos de primeira classe. Sua existência não indica que mais opções serão adicionadas, nem devem ser usadas como justificativa para apoiar a existência de outras opções no futuro.
 
@@ -35,4 +35,4 @@ Assim como o Prettier, o Biome acredita que o conjunto atual de opções é est
 
 Dito isso, mesmo que o Biome tenha se estabelecido como uma ferramenta de formatação capaz e robusta, ele ainda é relativamente novo, o que significa que há muitas oportunidades para abrir caminho para novos avanços e ideias que podem não parecer viáveis de outra forma.
 
-O estilo de formatação do Biome também é considerado relativamente estável, continuando a corresponder ao Prettier tanto quanto possível, com [poucos desvios intencionais](https://github.com/biomejs/biome/issues/739). Alterações no estilo do Biome podem ser consideradas e implementadas. Ainda assim, também é improvável que elas se tornem opções configuráveis e, em vez disso, seriam aplicadas universalmente a todas as versões futuras do Biome.
+O estilo de formatação do Biome também é considerado relativamente estável, continuando a corresponder ao Prettier tanto quanto possível, com [poucos desvios intencionais](https://github.com/biomejs/biome/issues/739). Alterações no estilo do Biome podem ser consideradas e implementadas. Ainda assim, também é improvável que elas se tornem opções configuráveis e, em vez disso, seriam aplicadas universalmente a todas as versões futuras do Biome.

src/content/docs/pt-BR/index.mdx

@@ -199,9 +199,9 @@ import AwardBanner from "@/components/AwardBanner.astro"
         <Icon name="github" />
         <p>GitHub</p>
       </a>
-      <a href="https://twitter.com/biomejs" class="x">
-        <Icon name="x.com" />
-        <p>Twitter</p>
+      <a href="https://bsky.app/profile/biomejs.dev" class="blueSky">
+          <Icon name="blueSky" />
+          <p>BlueSky</p>
       </a>
       <a href="https://fosstodon.org/@biomejs" class="mastodon">
         <Icon name="mastodon" />

src/content/docs/zh-CN/formatter/option-philosophy.md

@@ -25,7 +25,7 @@ Biome 从严格的配置选项子集开始，针对 JavaScript 生态系统中
 
 > ...[这些]并不是我们乐见的选择类型。它们在团队中造成了大量的自行车损耗，我们对此深表遗憾。这些选项现在很难取消，但它们是历史遗留问题，不应成为增加更多选项的动力（"既然有这些选项，为什么这个不能？）
 
-然而，当 [Prettier 挑战赛宣布](https://twitter.com/Vjeux/status/1722733472522142022)后，Biome 决定接受挑战，这就需要实施 Prettier 的所有配置选项，以实现完全兼容。
+然而，当 [Prettier 挑战赛宣布](https://console.algora.io/challenges/prettier)后，Biome 决定接受挑战，这就需要实施 Prettier 的所有配置选项，以实现完全兼容。
 
 Biome 仍赞同 Prettier 关于这些选项的理念，并认为它们是用于兼容性的传统功能，而不是基准功能集。这些选项的存在并不表明将添加更多选项，也不应作为支持未来存在其他选项的理由。
 

src/content/docs/zh-CN/index.mdx

@@ -191,9 +191,9 @@ import AwardBanner from "@/components/AwardBanner.astro"
         <Icon name="github" />
         <p>Github</p>
       </a>
-      <a href="https://twitter.com/biomejs" class="x">
-        <Icon name="x.com" />
-        <p>Twitter</p>
+      <a href="https://bsky.app/profile/biomejs.dev" class="blueSky">
+          <Icon name="blueSky" />
+          <p>BlueSky</p>
       </a>
       <a href="https://fosstodon.org/@biomejs" class="mastodon">
         <Icon name="mastodon" />