Hi *,
It's too much detail to answer everything, thus I focus on the techy
stuff only :-)
On Tue, Jan 18, 2011 at 1:15 PM, Michael Meeks <michael.meeks@novell.com> wrote:
On Fri, 2011-01-14 at 22:55 +0100, Christoph Noack wrote:
[...]
Ultimately I think you're going to have jumpy tabs if you use explicit
web-style links to other pages, and also force readers to read
lower-down too: perhaps not what we want. Potentially we could put the
content in two places [ not sure silverstripe will like that though -
may be very manual ].
Silverstripe knows the concept of "Virtual pages" that act as if the
content would be duplicated at the corresponding place (the current
Developer tab however is a "Redirector" page)
So yes, you could have content duplicated in multiple places, but the
context-information (left-hand menu) is of course dependent on where
the page resides. (If Developer would be a virtual page, you won't get
the second-level menu with QA, Designers, Documenters, Donors - you'd
only get the Developer's page as it would behave as a page on its own
in toplevel)
ciao
Christian
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***
Context
Re: [libreoffice-website] Re: new features page ... · Michael Meeks
Re: [libreoffice-website] new features page ... · Andras Timar
Re: [libreoffice-website] new features page ... · Andras Timar
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.