Do not show Category description twice

[nkuehn]

Adding a longer category description completely breaks the category page layout.

Steps to reproduce: Add a long description text. Reload.

Steps to fix:

• do not show the category description in the category header banner
• maybe do not show the category name twice at all, reserving the box above the products for the description

Bonus Points: properly handle HTML formatted content in the category view. HTML editor is the default in the platform, so people will write HTML by default. Either "clean" it or render it or both.

Source: Andreas Gottschalk doing a demo setup.

[lauraluiz]

@nkuehn actually it was never defined what was going into those two boxes (banner and jumbotron), so I filled it at some point with the category description to have something to show, but that's only App related.

@trangng is there any particular purpose to the upper banner? I can think of two possible usages:

• Put description of the parent (root) category, e.g. Women, Men, Accessoires. And leave the jumbotron below for the current subcategory, if any.
• Leave it as free CMS content, category unrelated (I would need some text for that).

[lauraluiz]

@nkuehn I've fixed the HTML issue from the bonus point in my development branch, so far as a basic rendered. Thanks for reporting it!

[lauraluiz]

@nkuehn I moved the description too long bug to another issue: #398

[lauraluiz]

@trangng I need some feedback about what to do with the upper banner:

• upper banner for root category and lower banner for the current category (if it's a root category then it's not shown), or
• upper banner for free category unrelated text from CMS and lower banner as it is

[trangng]

@lauraluiz I'd also go for option 1, but the problem is images I can not change in MC and the category images are always different for every categories.
Let's have the upper banner for root categories and for the rest the lower one as you suggested.

So actually the purpose for it was to leave it to the customer to choose btw. image or text banner.

So if someone uses the image banner it definitely needs to be in the CMS then

[nkuehn]

My two cents: Don't even bother about features that have no native support in CTP (i.e. work only with custom fields or abusing other things or implicit frontend-internal conventions) .

-> Just remove category image suport completely until it's a built-in feature?

[lauraluiz]

Let's just put the image as CMS (it's as easy as to hardcode it in the HTML and can be adapted for showcases, plus it's nicer) and the content of the root category. If we ever have images in categories, then we can easily change it.