Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
T
t3olayout
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 3
    • Merge Requests 3
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • services
    • T
      t3o sites
  • common
  • t3olayout
  • Issues
  • #620

Closed
Open
Opened Nov 20, 2019 by Thomas Löffler@tomalo.stuttgartOwner0 of 2 tasks completed0/2 tasks

Restructure and separate templates/partials/layouts from page and content elements

Summary

Look for all Fluid files which are used by pages and content elements. Then put all files into the folders they belong to.

Currently the file Layouts/Default.html is used by content elements and pages.

Steps to reproduce

Put HTML code to Layouts/Default.html (which should handle pages only). The HTML code appears on every content element as well.

Example URL

(Add an Url where we can see the issue)

What is the current bug behavior?

One layout file used by page and content elements

What is the expected correct behavior?

Separate layout files and make it more clear which file is used for what.

Acceptence Criterias

  • Clear structure for page templates
  • Clear structure for content element templates

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Assignee
Assign to
_Ready for sprint
Milestone
_Ready for sprint
Assign milestone
Time tracking
None
Due date
None
Reference: services/t3o-sites/common/t3olayout#620