Project

General

Profile

Actions

Task #2937

closed

change the carousel on the front page

Added by Florian Effenberger about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Team - Q1/2020
Start date:
Due date:
% Done:

0%


Description

As discussed during the Munich in-person meeting, we want to change the carousel on the front page.


Related issues

Related to DE - Task #2877: Bilder für Landing PageRejectedMike Saunders

Actions
Actions #1

Updated by Mike Saunders almost 3 years ago

  • Status changed from New to In Progress

So I've been looking into this. In themes/libreofficenew/templates/Includes/slider.ss, the carousel text and buttons are defined like so:

           <div class="carousel-caption">
              <h1>$HomepageTitle2</h1>
              <p class="lead margin-40"><em>$HomepageText2</em></p>
              <a class="btn-home" href="$DownloadPageLink"><i class="icon-chevron-right"></i><%t Homepage.DownloadNow "Download Now" %></a>
            </div>

I can change the text for a specific slide in the SilverStripe admin interface (thereby updating $HomepageText2), but it looks like I have to manually change the link in this slider.ss. The problem here is, if I change the link, it will affect all language versions of the site.

For instance, I change the second slide to talk about our blog, and update the link accordingly. But then in all language versions of the site, the second button will go to the blog. This won't make sense unless all other sites update the text for that slide at the same time.

So not sure how to resolve this -- it might just be a technical limitation. If we can somehow change the buttons per language, that would be a solution, but I don't know if that's possible. I'll talk to Cloph...

Actions #2

Updated by Florian Effenberger almost 3 years ago

So not sure how to resolve this -- it might just be a technical limitation. If we can somehow change the buttons per language, that would be a solution, but I don't know if that's possible. I'll talk to Cloph...

Any feedback already, how can we address this? :)

Actions #3

Updated by Mike Saunders almost 3 years ago

Florian Effenberger wrote:

So not sure how to resolve this -- it might just be a technical limitation. If we can somehow change the buttons per language, that would be a solution, but I don't know if that's possible. I'll talk to Cloph...

Any feedback already, how can we address this? :)

Didn't hear back, but I pinged Cloph again. It may be a technical limit with the current site that we should overcome with the new design.

Actions #4

Updated by Florian Effenberger almost 3 years ago

  • Target version changed from Q3/2019 to Q4/2019
Actions #5

Updated by Florian Effenberger almost 3 years ago

  • Related to Task #2877: Bilder für Landing Page added
Actions #6

Updated by Mike Saunders over 2 years ago

So I think this is simply a technical limitation with the current website. As mentioned, if I change the "Download now" button, it changes for all language versions of the website; it appears to be hard-coded. We can change the background pictures, put changing the button for each picture with a language-specific link appears to be impossible.

I would suggest putting this as a suggestion for the website redesign, closing this one for now, and focusing on the things we can implement (such as #2876, the language selector).

Actions #7

Updated by Mike Saunders over 2 years ago

So as mentioned, I'm not sure if this is even technically possible without changing all language websites at the same time, which would introduce many problems. In any case, it won't be possible in Q4 and without help from Cloph (or another SilverStripe) expert. I'd suggest rejecting this and making it a goal for the website redesign...

Actions #8

Updated by Florian Effenberger over 2 years ago

  • Target version changed from Q4/2019 to Q1/2020
Actions #9

Updated by Mike Saunders over 2 years ago

Shall we reject this? I don't believe it's technically possible without changing for all languages at the same time, and it'd break many things. Also, with a new website coming up, I'm not sure if it's worth putting a lot of effort in to trying to fix/overcome it...

Actions #10

Updated by Florian Effenberger over 2 years ago

  • Status changed from In Progress to Closed

Agreed, let's close it for the moment

Actions

Also available in: Atom PDF