Hi David, *,
On Tue, Dec 21, 2010 at 1:05 AM, David Nelson <commerce@traduction.biz> wrote:
On Tue, Dec 21, 2010 at 05:38, Bernhard Dippold
<bernhard@familie-dippold.at> wrote:
Twitter and blog in
the "scrolling area" are ok, but I think a "news" area is more important
than those tow.
Christian, is there a dedicated news/blogging module for SilverStripe?
Well - there is a blog module, yes (meant for providing blogs
yourself), and regarding news: You can of course add a news section as
well. Similar to how the FAQ-items are automatically collected, one
can collect news items.
And you can create a area on the page that shows the X latest news entries.
The basics on how to do it are laid out in the basic tutorials of silverstripe
http://doc.silverstripe.org/tutorial:2-extending-a-basic-site
If it is just about providing an RSS feed: You can turn pretty much
everything into a RSS feed with silverstripe...
The real questions is: Do we want to add news via the CMS or not.
ciao
Christian
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/website/
*** All posts to this list are publicly archived for eternity ***
Context
- Re: [steering-discuss] Re: [libreoffice-website] Website status (continued)
Re: [libreoffice-website] Website status · Bernhard Dippold
Re: [libreoffice-website] Website status · David Nelson
[libreoffice-website] Re: [steering-discuss] Website status · Cor Nouws
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.