Change X/Twitter links to Bluesky

[shurup]

Description

This PR is heavily based on #49546 (all credits to @rikatz) to replace the Kubernetes community X/Twitter link with the one on Bluesky.

It's different from the original PR because:

• all translation-related changes are removed (they should be implemented in separate PRs and approved by relevant localisation teams);
• similar changes are brought to the Community page where X was mentioned as well;
• the footer layout is slightly modified since, after adding one more social link (via Footer Social Icons #49594), 5 icons could not fit into the left column.

P.S. I'm not sure whether we're ready to merge it right now due to this comment (Bluesky accounts are not in Buffer yet).

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	a2d8173
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/679c7e8a0683350008089044
😎 Deploy Preview	https://deploy-preview-49606--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sftim]

Thanks for the PR.

This doesn't look right though. Why has package-lock.json changed but not package.json?

[rikatz]

Because package.json does not have any reference to font awesome :) the update was made with npm upgrade and the package.lock saved

The change is correct :)

(Also sorry for delays answering, day work has been really busy)

Explanation provided

[sftim]

/lgtm

[mfahlandt]

Sorry to go in here again - didn't we agree in slack to deprioritize in this discussion https://kubernetes.slack.com/archives/CPNFRNLTS/p1737720949945399

In my Opinion, we should still list all of our Platforms at least in the listing site. Also proposed in the previous thread

The current decision is to still put out Content to X as it has the largest End User Audience and is growing still.
We are basically following also the decision of the CNCF there: cncf/foundation#893 (comment)

Comms created a specific rules for X https://github.com/kubernetes/community/blob/master/communication/kubernetesio-x-guidelines.md

Also as mentioned, we are still waiting for funding to automate BluSky to bufffer.

/hold

[shurup]

@mfahlandt thanks for your clarifications! Personally, I'm all in for leaving the Bluesky links only, but I'm totally fine to put the X links wherever it's needed — if that's what we need now. Thus, we're expecting the final guidance (from the Steering Committee and/or ContribEx?) here on what should be left on the website.

P.S. I guess hold did not work here, so let me do it:
/hold

[sftim]

AIUI Bluesky accounts are now in Buffer.

/committee steering
Let's confirm this is the change we want to make, at project level.

[jberkus]

Ideally, we should list everything we regularly post to, which would include BlueSky, Mastodon, X, and LinkedIn.

However, that would require some reformatting of the site footer, which doesn't currently have space for 4 icons in place of one. Particularly since we also display StackExchange, Discuss, and YouTube. At some point, we really just need to direct folks to a page listing everything.

BTW, right now the site is displaying LinkedIn in the footer.

[BenTheElder]

This was formally raised to steering today, but we have not yet had time for consensus.

---

Personally I have been in touch with the comms team fsince this topic was first raised and I think a split between "here is a complete listing" and "here are some in the footer etc that we're prioritizing" makes sense. I think in the spirit of openness we should fully list all accounts controlled by the project somewhere if not everywhere (to avoid clutter, to prioritize preferred platforms, etc)

I also think contribex comms should have discretion here (e.g. previously bluesky got less attention due to lack of buffer support, that's a detail that should be managed by the team owning/working on this). I don't think it's pragmatic to otherwise dictate this.

This does not, however, necessarily represent the steering committee at large.

---

I'll make sure to follow up when we have consensus.

[sftim]

I think in the spirit of openness we should fully list all accounts controlled by the project somewhere if not everywhere (to avoid clutter, to prioritize preferred platforms, etc)

I suggest: https://www.k8s.io/community/

[shurup]

which doesn't currently have space for 4 icons in place of one

Actually, this PR modifies the footer layout already, allowing 12 (6x2) social links in the footer (instead of 8 we have right now).

I suggest: https://www.k8s.io/community/

That's a good place where all social links reside now indeed. If we want to promote some priority and not list everything everywhere, we can also consider adding a "see more" link leading to the Community page in the shorter lists (e.g. footer).

[BenTheElder]

Steering has a majority consensus to support the comms team's decision here (that would be @kubernetes/contributor-comms, including @mfahlandt above).

For now then, please retain a full listing on the community page as suggested above, but we can rotate in bluesky in the footer and other places.

---

My suggestion: We can also iterate further in the future, with the input from @kubernetes/contributor-comms. I suggest updating with the proposed change to retain the community page, and going ahead with that. That way we can not block further on adding bluesky now that comms has those accounts in buffer, and to address the original request. We can additionally revisit how we manage the footer etc in future PRs.

---

Thanks all!

[sftim]

From SIG Docs, this is OK for contributor comms to unhold whenever you'd like to.

/approve
for SIG Docs. Leave the hold in place until we're ready to merge this.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sftim]
• content/en/OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[reylejano]

I agree that we should list all the socials the Kubernetes project officially posts to and is active but I support any decision that Contributor Comms makes
/lgtm
Contributor Comms can unhold if ready to merge or make any other suggestions, comments, or requests for change

[mfahlandt]

Also please remove the twitter widget from the bottom of the community page

[mfahlandt]

Suggested change

	other = "YouTube"
	other = "YouTube"
	[community_twitter_name]
	other = "X (formerly Twitter)"
	# Also cover [community_using] if localizing this site
	[community_x_name]
	other = "X (formerly Twitter)"

[mfahlandt]

Suggested change

	<div id="twitter" class="community-resource">
	<div id="blusky" class="community-resource">

[mfahlandt]

can we add this blog of twitter to the bottom of the list

[mfahlandt]

Same re add Twitter to list as last option

[sftim]

Given #49606 (comment) and similar comments:
/lgtm cancel

Given #49606 (comment)
/hold cancel

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.