Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
T
typo3.org
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 8
    • Merge Requests 8
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • services
    • T
      t3o sites
  • typo3.org
  • typo3.org
  • Issues
  • #387

Closed
Open
Opened Feb 14, 2019 by Andreas Nedbal@pixeldesuContributor1 of 1 task completed1/1 task

HTML-based Feature Headers are broken

Summary

The feature headers implemented by the design team on pages like CMS and Features (+ subpages) have wrong styling or collide and overwrite the implemented definitions of the CSS.

These elements should be replaced with the actual content element (Feature Header) to prevent breaking of the layouts and in general sketchy looks for some of the entry/introductory pages of the CMS.

Steps to reproduce

Just visit one of these pages:

  • https://typo3.org/cms/ (most apparent)
  • https://typo3.org/cms/features/ (Breadcrumb overlaid)
    • This also happens on basically all of the feature subpages

What is the current bug behavior?

Wrong design / implementation. The current design on the website is having obscenely large negative margins and uses background images, the implemented content element uses responsive images in a picture-tag, without those margins.

What is the expected correct behavior?

What you should see is almost identical, just minus the negative margin that can slide into other elements/the navigation, the implementation as content element follows the CSS the design team wrote for the implementation currently present on the website.

Acceptence Criterias

  • As a Visitor of the page, I want to see the site in a fully working state, as broken design might not reflect quality of a CMS I would want to use.

Relevant logs and/or screenshots

Screenshot_2019-02-14_at_15.57.11

Possible fixes

Port HTML-based CE's for Feature Headers to the actual Features Header CE

Edited Feb 22, 2019 by Stefan Busemann
Assignee
Assign to
Sprint 1 (2019)
Milestone
Sprint 1 (2019) (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: services/t3o-sites/typo3.org/typo3.org#387