[MGNLSTK-965] STK must be in sync with static prototype changes for every minor and major release Created: 06/Jun/12  Updated: 19/Jul/12  Resolved: 19/Jul/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: concept, paragraphs, templates
Affects Version/s: 2.0.2, 2.0.3
Fix Version/s: 2.0.4

Type: Bug Priority: Neutral
Reporter: Christian Ringele Assignee: Milan Divilek
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLSTK-836 Resource not found issue Closed
is causing MGNLSTK-855 Layout issues on FAQ page Closed
is causing MGNLSTK-867 Image gallery: Top divider missing Closed
is causing MGNLSTK-862 Layout issues with registration page Closed
is causing MGNLSTK-864 Layout issues on login page Closed
dependency
depends upon MGNLSTK-860 Separator line missing above Opener? Closed
relation
is related to MGNLSTK-946 Update STK & Theme Pop with latest ch... Closed
is related to MGNLSTK-852 Latest News Teaser is not correctly d... Closed
supersession
supersedes MGNLSTK-878 STK Prototype: Update HTML structure ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

In between every minor release there could be changes within the html static prototype.
The static prototype get released together with the STK. There for the STK must always be aligned/in sync with the static prototype.
This is a repeating task for every minor&major version.

I'll link a issue, which just postponed to a later version. This should never happen:
STK 2.0.3 is not in sync with prototype 2.0.3

The process to do:

  • See if there were any check ins into the prototype
  • If so a divv whill show it that were css or html changes
    • css changes -> can just be copy & pasted into the theme module
    • html changes -> accordinf ftl must be found and change implemented

Be careful, right now all changes till prototype 2.0.1 must be taking in account.



 Comments   
Comment by Christian Ringele [ 06/Jun/12 ]

This is the issue, which just was moved to a future fix.
This is not possible, STK and prototype mus stay in sync.

Comment by Natascha Desmarais [ 19/Jul/12 ]

We can't really create such generic collections any more, otherwise these will be moved from release to release. Also, since we have a new standard on how to proceed with these prototype issues, I would prefer if we switch to it and keep a good overview with this.

Generated at Mon Feb 12 07:32:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.