Infrastructure

Hi Florian,

I have no access to main site's silverstripe admin console, and local sites has old templates. So i cannot see that it is a manually edited page or a template generated page.

May be Charles and others can see and comment.

Christian should be able to help out here :-)

I don't see how this is relevant for proposing a different way to present the portable version.

In both cases you would have to provide some content to add to the page.

Whether that will be added automatically or entered manually into one of the entry-boxes in the backend doesn't really matter and can be changed to be either way.

But to answer nevertheless: The main part on the left on the newdesign downloadpage all comes from the template, the related links in the sidebar are added in the backend manually.

But again: how it is created should not matter for proposing how it should look/work.

For manually created way one can also use a mix of auto-created stuff and manual placements, either using $Variable replacements or more sophisticated replacements using shortcodes like [shortcodename,option=foo]some conente[/shortcodename] or similar.

I know I repeat myself: How the page is currently created doesn't matter. The hard part is fitting it into the design, not having the html generated..

As always when it comes to proposals to change design or similar: Just create an offline copy of the page (use your browser to save the page and linked assets/css locally), then modify that until it is what you want it to be.

Hi Christian,

I think i cannot express the issue clearly. The problem is having up-to date Portable links automatically like LibreOffice installer's download.

If installer was updated manually by local website admins, there will be lots of local sites serving 3.6 series instead of current release.

Variables or anything similar can be easy for us to maintain.

Best regards,
Zeki

What I propose:
We keep the distinction main download page and portable page as is right now. This has proven to be working quite well, and the more variants we offer on the download page, the more cluttered it will be.

However, for the portable download page at http://www.libreoffice.org/download/portable-versions/ we should get the version number(s) out of a macro/variable, i.e. automatically created, so local site maintainers don't have to update it manually.

Does that sound acceptible?