Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML page titles should move the Codidact community name to the end #1392

Open
ws909 opened this issue Sep 6, 2024 · 5 comments
Open

HTML page titles should move the Codidact community name to the end #1392

ws909 opened this issue Sep 6, 2024 · 5 comments
Labels
area: html/css/js Changes to front-end code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: change request New feature or request

Comments

@ws909
Copy link
Contributor

ws909 commented Sep 6, 2024

Page titles are currently prefixed with the Codidact community name. This is a mistake; it should be moved to the end.

For example, for https://software.codidact.com/posts/292128, the title is currently:

<title>
  Software Development - Prevent anonymously subclassing 
</title>

It should be:

<title>Prevent anonymously subclassing - Software Development</title>

Should potentially add "Codidact" to the title as well.

See:

Additionally, as the screenshot in the Codidact post shows, browser tabs for different posts in the same community all show the exact same title. This has been annoying me for a very long time.

@ws909 ws909 changed the title HTML page titles include should move the Codidact community name to the end HTML page titles should move the Codidact community name to the end Sep 6, 2024
@cellio cellio added area: html/css/js Changes to front-end code type: change request New feature or request priority: medium complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Sep 6, 2024
@trichoplax
Copy link
Contributor

There is some older discussion on Codidact Meta:

An answer there mentions some potential customisation that may need to be available for other QPixel instances, so it's probably worth some discussion here of how much of that is required before putting work into this.

@ws909
Copy link
Contributor Author

ws909 commented Sep 6, 2024

I'm not going to comment on how one would implement configuration settings for the page title. However, that is outside of the scope here. This should be a one line change, and is important for UX and SEO. Configuration settings can be done later.

In regards to my note in the post:

Should potentially add "Codidact" to the title as well.

Make a blanket change for that now, adding it to the title part, or simply ignore it, and handle it later, when adding configuration settings.

@cellio
Copy link
Member

cellio commented Sep 6, 2024

There is some older discussion on Codidact Meta:

Oh, good catch. I did say in that answer that perhaps I am overthinking it, and we didn't yet have the We bmasters question. It's ok with me if we flip it around now and look into configuration later. The favicon should indicate the service, and anecdotally, when I had a bunch of Jira or Confluence tabs lined up at work, I used the favicon and then the title to find the tab I wanted. If this helps with SEO and doesn't do harm, I'm inclined to do it.

If "Codidact" is baked into the title now then moving it doesn't make things worse. Ideally, the name of the network would be a configuration parameter so that companies, universities, etc can name their servers whatever they like. Not a blocker here IMO.

@trichoplax
Copy link
Contributor

trichoplax commented Sep 6, 2024

"Codidact" is only currently present where it is part of the community name, such as in "Codidact Meta". In most communities "Codidact" is not part of the community name and therefore not part of the page title.

If this is to be considered the least important part of the title anyway (placed in last position), is there any disadvantage to just sticking with what we currently have for now (community name and post name), but with the order switched as suggested?

Then adding the instance name (such as Codidact) could wait for the larger change that involves configuration.

@ws909
Copy link
Contributor Author

ws909 commented Sep 6, 2024

Ah, I did not give the fact that "Codidact" already exists in some community names, a thought. I suggest just leaving that be, and only change the order, then. That's easily done, and should not risk causing any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: html/css/js Changes to front-end code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: change request New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants