Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hi Cor,

Am 10.01.2016 um 17:43 schrieb Cor Nouws:
Hi Andreas,

Andreas Mantke wrote on 12-12-15 19:16:

Due to some issues with the usability of the current website I decided
to work on two new add-ons for the website to solve this issues a time
ago. I worked on that add-ons a lot in my  spare time and finished a
version for Plone 4.3 around the LibreOffice conference in Aarhus. This
add-on versions used five.grok. But this add-on package will not be
actively supported with the current version of Plone, Plone 5.0. Thus I
decided to review my add-ons and drop the five.grok dependency. This
made it necessary to create a lot of changes to the add-ons and nearly
start from scratch. I got a new beta-version of them out now (after some
weeks of work during my spare time).
Looking at these issues, and the fact that you repeatedly emphasize that
you do the work in your free time, I would suggest you to ask the board
to support the work, so that the most can be done in a project by
someone having normal time to do it. And that your, of course fully
understandable limited availability, is no longer a bottle neck. The
site is important enough for such a move, IMO.

the development of the add-ons for the new site (in the revision) is
nearly finished. I had to fix some smaller issues.

But there are some further steps, that had to be done by payed developer:

-- design of the new site
-- content transfer from the current site to the new one
-- adaption of one or two  important external add-ons for Plone 5


I created a new test website, that runs on a new shiny Plone 5.0:
http://vm141.documentfoundation.org:9103/loexttem5/en/extensions
Thanks for that, of course :)
Few remarks:
1) I was thinking about advantage when the split
    Home | Extensions | Templates
is removed. Extensions are the landing page, for what the very vast
majority comes to the site.
A clear Instructions somewhere will be OK for people.
I have not created a default view (page) for the home of the new site.
If we want to go with a website with translated content, I fear that the
home had to stay (with a default page [translated] with some information
for users).


2) The search top-right is fine, but it is not clear that that is the
way to search for an extension.
This Plone live search will be disabled in the productive state. I have
not done this in the test site yet.

Every part of the site (extensions and templates) will have a search
form for products: extensions or templates. That is already implemented.
You will see the form once you click on one of the entries in by category.

3) Nearly two years ago we made a functional design for some pages.
Can you give an update (wiki?) on the status of the current work in
relation to that design?
Could you provide a link to that page. Maybe I lost track.

Regards,
Andreas

-- 
## Developer LibreOffice
## Freie Office-Suite für Linux, Mac, Windows
## http://LibreOffice.org
## Support the Document Foundation (http://documentfoundation.org)
## Meine Seite: http://www.amantke.de 


-- 
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.