[Apps Scope] App Summary appears to be part of Description

[Michael Spencer]

The tagline in app descriptions looks like it is part of the main description, without any spacing or difference in font, which makes it hard to read. Is it possible to make the tagline bold or separated in some way?

Desired solution
---------
Separate out tagline from rest of info and place directly below screenshots - see attached design including the tagline / strapline

[Michael Spencer (ibelieve)]

As an example, see the screenshot in this Google+ post: https://plus.google.com/+pabloseminario/posts/TueiGXWn1ko

[Michał Sawicz (saviq)]

There's actually no separate space for the tagline in the dash design, only quick thing we could do would be to put another newline between it and the description.

[dobey (dobey)]

Please file bugs as bugs, and not suggestions/tasks. Describing the problem (what you see) is much more useful in a bug report, than describing what you think the solution should be.

[dobey (dobey)]

Also, does this really affect the click scope? It seems that perhaps the solution is to simply have the dash provide a bit of dead space around widgets (at least around text widgets), so that multiple text widgets that are next to each other, do not appear to be part of the same text.

[Andrea Cimitan (cimi)]

afaics this was fixed with new scopes

[dobey (dobey)]

Actually, it seems the first line "summary" is part of the description text itself, and not a separate field. So perhaps this needs to be resolved in click and on the server, and we could then have them be in separate text widgets in the preview?

[James Tait (jamestait)]

Added SCA to the affected projects, as that's what's currently prepending the tagline to the description for backward compatibility (with what?) and would need to be updated to pass the tagline to CPI as a separate field.

[dobey (dobey)]

Can we just get rid of the "tagline" in the devportal UI, and strip it out of all the app descriptions in the database? I think that's probably a better solution, as in many cases it's just duplicated, and it doesn't provide any improved experience to users, as anything important should just be in the description or changelog entries anyway.

[James Tait (jamestait)]

I have no objection to removing the tagline field. I don't think anything else uses it, because the ClickPackage model is distinct from the legacy Package model now, and CPI consumes from the feed, where the tagline is already prepended to the description.

It looks like it'd just be work in SCA:

 - create a migration to remove the field (optionally prepend tagline to description)
 - remove tagline from the ClickPackage model, form and templates
 - tweak pkgme to not require tagline for Click packages

[dobey (dobey)]

Awesome. Let's do that! Hopefully Martin will be feeling better on Monday and can approve someone doing the needed work on the server to get rid of it. :)

[Natalia Bidart (nataliabidart)]

Given that there are existing clients using the package index metadata and some may rely on the description field being the concatenation of the summary and the actual description, we will not change this for the click packages.

Instead, we are exposing a new field "summary" and we are going to drop the summary from the description for all snap packages.

[dobey (dobey)]

@Natalia Can you specify what existing clients would rely on the description field having the first line being something other than the description itself?

[John Lenton (chipaca)]

@rodney ooh, I can answer that one!
Existing 15.04 snappy core devices.