Tagline

[Jack5079]

https://gitlab.gnome.org/GNOME/Initiatives/-/wikis/App-Metadata#summary

Do

• Keep it short (35 characters or less)
• Pique people's curiosity
• Use imperative if possible (e.g. "Browse the web" instead of "A web browser")
• Use sentence case

Don't

• Technical details (e.g. the toolkit or programming language)
• Structures like "GUI for X" or "Client for Y"
• Mentioning the target environment (e.g. "X for GNOME")
• Repeating the app's name
• Overly generic adjectives like "simple", "easy", "modern", "powerful", etc.
• Articles (e.g. "A ..." or "An ...")
• Punctuation (e.g. a period at the end)
• Title case (e.g. "Chat With Your Team")

Good examples

• Maps: "Find places around the world"
• Shortwave: "Listen to internet radio"
• Slack: "Chat with your team"

Bad examples

• Tau: "GTK frontend for the xi text editor"
• Contacts: "A contacts manager for GNOME"
• Devhelp: "A developer tool for browsing and searching API documentation"

[Jack5079]

I like "Go on tangents" but I don't think it describes anything, it does pique curiosity though "Libre remake of Arc for Linux" is declarative, uses an overly generic adjective (libre), the target platform, and mentions what it's an alternative of "Browse the web" is already used by GNOME Web

[Jack5079]

I like "Go on tangents" but I don't think it describes anything, it does pique curiosity though "Libre remake of Arc for Linux" is declarative, uses an overly generic adjective (libre), the target platform, and mentions what it's an alternative of "Browse the web" is already used by GNOME Web

Firefox uses "Fire starts here" so 🤷🏻

[Jack5079]

I think "Go on tangents" does actually describe what it does, it's designed for going on rabbit holes and such