Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
I think this is going to require more thought, because we need to do something that works for all instances, not just ours. Our browser titles have several elements: favicon (this is configura...
Answer
#2: Post edited
by
Monica Cellio
·
2023-07-05T02:54:51Z (over 1 year ago)
typo
- I think this is going to require more thought, because we need to do something that works for all instances, not just ours.
- Our browser titles have several elements:
- - favicon (this is configurable today)
- - network name ("Codidact"; I don't know where that's set)
- - community name (dynamic)
- - more specific content (question title, user name for a profile, category name, etc) -- I'll call this "context" in the following discussion
If you're running QPixel inside your company or school, you probably want the format to match your other tools, whatever they are. Your users might think of your lone internal Q&A site as just "Codidact", the same way my coworkers think of our wiki as "Confluence" (not "MyCompany Wiki") and our bug tracker as "Jira". On the other hand, if you have multiple sites, like our network of communities, then the site identity might be more important than the name of the "service" and your might users expect to see something like "Engineering Codidact" or "Sales Codidact" or, in our case, "Code Golf Codidact". (Or might not; people are complicated. :-) )- It seems to me that, to satisfy all common use cases, we need the name pattern to be configurable -- I'm thinking global settings, not site settings, so a network is self-consistent. I'm imagining a setting like "Browser Title Pattern" where you can enter a string like `$site - $context ($network)` or `$network $site - $context` (this latter is what we have, e.g. "Codidact Meta - Q&A"). *Then*, when we have something like this, we can switch around the elements on `codidact.com` without changing things out from under other networks.
- It is also possible that I am over-thinking this. I would like feedback on this approach.
- I think this is going to require more thought, because we need to do something that works for all instances, not just ours.
- Our browser titles have several elements:
- - favicon (this is configurable today)
- - network name ("Codidact"; I don't know where that's set)
- - community name (dynamic)
- - more specific content (question title, user name for a profile, category name, etc) -- I'll call this "context" in the following discussion
- If you're running QPixel inside your company or school, you probably want the format to match your other tools, whatever they are. Your users might think of your lone internal Q&A site as just "Codidact", the same way my coworkers think of our wiki as "Confluence" (not "MyCompany Wiki") and our bug tracker as "Jira". On the other hand, if you have multiple sites, like our network of communities, then the site identity might be more important than the name of the "service" and your users might expect to see something like "Engineering Codidact" or "Sales Codidact" or, in our case, "Code Golf Codidact". (Or might not; people are complicated. :-) )
- It seems to me that, to satisfy all common use cases, we need the name pattern to be configurable -- I'm thinking global settings, not site settings, so a network is self-consistent. I'm imagining a setting like "Browser Title Pattern" where you can enter a string like `$site - $context ($network)` or `$network $site - $context` (this latter is what we have, e.g. "Codidact Meta - Q&A"). *Then*, when we have something like this, we can switch around the elements on `codidact.com` without changing things out from under other networks.
- It is also possible that I am over-thinking this. I would like feedback on this approach.
#1: Initial revision
by
Monica Cellio
·
2023-07-05T01:54:58Z (over 1 year ago)
I think this is going to require more thought, because we need to do something that works for all instances, not just ours.
Our browser titles have several elements:
- favicon (this is configurable today)
- network name ("Codidact"; I don't know where that's set)
- community name (dynamic)
- more specific content (question title, user name for a profile, category name, etc) -- I'll call this "context" in the following discussion
If you're running QPixel inside your company or school, you probably want the format to match your other tools, whatever they are. Your users might think of your lone internal Q&A site as just "Codidact", the same way my coworkers think of our wiki as "Confluence" (not "MyCompany Wiki") and our bug tracker as "Jira". On the other hand, if you have multiple sites, like our network of communities, then the site identity might be more important than the name of the "service" and your might users expect to see something like "Engineering Codidact" or "Sales Codidact" or, in our case, "Code Golf Codidact". (Or might not; people are complicated. :-) )
It seems to me that, to satisfy all common use cases, we need the name pattern to be configurable -- I'm thinking global settings, not site settings, so a network is self-consistent. I'm imagining a setting like "Browser Title Pattern" where you can enter a string like `$site - $context ($network)` or `$network $site - $context` (this latter is what we have, e.g. "Codidact Meta - Q&A"). *Then*, when we have something like this, we can switch around the elements on `codidact.com` without changing things out from under other networks.
It is also possible that I am over-thinking this. I would like feedback on this approach.