Hi Marc,
Am 24.10.2015 um 23:43 schrieb Marc Paré:
Hi Andreas,
Le 2015-10-23 17:34, Andreas Mantke a écrit :
Hello,
I finished my work on a static version of the LibOCon2012 website. I got
everything into one folder with subfolders and works on my local
webserver directory.
I wonder to which subfolder I should upload my work. Should I create a
subfolder inside the Plone LibO conference directory and name it 2012
(later the 2013 could get to another subfolder: 2013)?
Regards,
Andreas
Would it make more sense to have it on the same server sub/folder as
the other LibOCons? At least they would all be on the same server.
I uploaded it to the same server in a new folder. If I'm not wrong, It
should be on the same server with the LibreOffice website.
The next step should be: test the static HTML output (and the rights
management on the server).
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: website+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/website/
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.