Better Homepage title?

[rgaudin]

For a very long time, Dashboard title (HTML page title, appearing in Tab) has been the name of the Hotspot's domain. It looks unpleasant to the demo user (see https://github.com/offspot/imager-service/issues/409) as in this example the Hotpost is named kiwix (which is arguably a poor name for this).

Using this is practical in that the identifying information is directly there and consistent with the Network name but it looks unprofessional on the browser's title/tab bar.

At the moment, we have no such per-hotspot information to replace it with. We have another name in DB that's clearly specified as not used and thus not applicable.

Modifying case is usually a bad idea as this is a free text that may look bad. domain can be an accronym or several words together, etc. Eg: orangefoundation is subpar but OK. Orangefoundation is worst.

[rgaudin]

@kelson42 @Popolechien WDYT ?

[Popolechien]

@rgaudin I'm sorry but I don't understand your problem statement.

[rgaudin]

The Page title is the SSID (kiwix here). We have no other name to use from the configuration.

Possibilities:

• Use a title that's not just the SSID. Could be “Kiwix Hotspot: kiwix”. Disadvantage is that it's less readable since those tabs are usually reduced and the meaningful info is not at the beggining (be we still have the favicon)
• Ask for a different Name in the configuration. We can imagine asking just one and convert it to an SSID-compatible one (displaying it so user can adjust).
• Transform what we have (the SSID) like capitalizing the first letter

[Popolechien]

Well in a way having it here would answer the question in offspot/dashboard#5, no? It's short, visible yet discreet and rebrands to Kiwix.

I certainly would not ask users for a specific name for this field that not everyone pays attention to. Why not use the configuration name, as more often than not it'll be close to the SSID (or more likely to be capitalized / include spaces)?

[rgaudin]

Why not use the configuration name, as more often than not it'll be close to the SSID (or more likely to be capitalized / include spaces)?

Because we explicitly told them it used used only on the imager and is thus often used properly: to identify a Configuration for the Imager user, not at all how a Hotspot user wants to identify it.

[Popolechien]

Well since it only appears on the tab where the full configuration is displayed I reckon this is a very legitimate use of said config name.

[rgaudin]

Well since it only appears on the tab where the full configuration is displayed

Doesn't matter where it appears and it is not limited to this page. That's the name that appears in the config list.

I reckon this is a very legitimate use of said config name.

Yes, a config name, not a Hotspot Display Name for Hotspot user. We cannot promise we wont use it on the Hotspot and then do it without asking. That's wrong.

@kelson42 this issue is yours and is about changing an existing behavior. Please contribute.

[Popolechien]

it is not limited to this page

Where else then?

We cannot promise we wont use it on the Hotspot

I was suggesting the following conceptual breakthrough: stop promising we won't use it (which was a self-imposed limitation to start with). The current text below the Config name field is Used only within the Imager. If we remove this, then the config name becomes the de facto dashboard name.

[kelson42]

Let's try to bring clarity (hopefully I get it right), we have 4 different things:

• The config name "Kiwix Demo"
• The SSID "KIWIX_HOTSPOT_DEMO"
• The domain name "kiwix"
• The device name (title of the dashboard): "Kiwix Demo"

This is a lot of different things and specifying seems legitimate, but we should provide default values to allow move forward quickly to people want to save time and hassle with configuring all these details

[rgaudin]

Not exactly.

We have only one source data for the Hotsot. We call is Hotspot Name. It is used as SSID and hostname. Usage is clearly exposed IMO. It can contain uppercase but no space and is somewhat limited.

We also have a Config Name which usage is less defined. We only say it is “only used within imager”.

---

There no dedicated SSID or Hotsname nor there is a Device Name.

In the past the Hotspot Name was displayed prominently on homepage and that was removed by @Popolechien because it was “not actionable”. Since (that was years ago) we've had the Hotspot Name only visible in the Browser bar (<title />).

I think there are two issues here:

• short-term one, for this ticket which is in the to-be-closed project: Do we change the Title (with the data at hand: Hotspot Name) or not ?
• longer-term: Do we need a less-technical/display-oriented Name for the Hotspot? If yes, we can discuss the strategies to get it in a way that's user-friendly and doesn't break expectations silently.

[kelson42]

Having a technical name (with heavy constraints) used at the same time for a human friendly label (freestyle) can not be satisfying on the longer term.

First thing to do is to uncouple this at the project configuration level first. Then is left the question of what can be configured by the user and how it looks like in the imager.

short-term one, for this ticket which is in the to-be-closed project: Do we change the Title (with the data at hand: Hotspot Name) or not ?

Hardly better IMHO

longer-term: Do we need a less-technical/display-oriented Name for the Hotspot? If yes, we can discuss the strategies to get it in a way that's user-friendly and doesn't break expectations silently.

Definitly and not complexifying too much the UI is the challenge. I woukd propose something like this:

• „Free text“ Hospot name is requested to user
• Based on it we compute other technical ids (SSID, domain, machine name, …)
• We propose (in an overlay) the user for validation these names which he can change (form) if needed /wanted.
• This naming configuration overlay is available any time via an „advance“ or „details“ configuration button beside the „hotspot name“ button. We could also thing about an „advanced“ configuration tab with all these unmandatory details.