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

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:

In which order should the brand name and article title appear in the page ?</a></li> </ul> <p>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.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/trichoplax"><img src="https://avatars.githubusercontent.com/u/6706597?v=4" />trichoplax</a> commented <strong> 2 months ago</strong> </div> <div class="markdown-body"> <p>There is some older discussion on Codidact Meta:</p> <ul> <li><a href="https://meta.codidact.com/posts/287743">Show question title before community name in browser tab</a></li> </ul> <p>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.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ws909"><img src="https://avatars.githubusercontent.com/u/37029098?v=4" />ws909</a> commented <strong> 2 months ago</strong> </div> <div class="markdown-body"> <p>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.</p> <p>In regards to my note in the post:</p> <blockquote> <p>Should potentially add "Codidact" to the title as well.</p> </blockquote> <p>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.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/cellio"><img src="https://avatars.githubusercontent.com/u/5557942?v=4" />cellio</a> commented <strong> 2 months ago</strong> </div> <div class="markdown-body"> <blockquote> <p>There is some older discussion on Codidact Meta:</p> <ul> <li><a href="https://meta.codidact.com/posts/287743">Show question title before community name in browser tab</a></li> </ul> </blockquote> <p>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.</p> <p>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.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/trichoplax"><img src="https://avatars.githubusercontent.com/u/6706597?v=4" />trichoplax</a> commented <strong> 2 months ago</strong> </div> <div class="markdown-body"> <p>"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.</p> <p>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?</p> <p>Then adding the instance name (such as Codidact) could wait for the larger change that involves configuration.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ws909"><img src="https://avatars.githubusercontent.com/u/37029098?v=4" />ws909</a> commented <strong> 2 months ago</strong> </div> <div class="markdown-body"> <p>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.</p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>

codidact / qpixel

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