[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-www
Subject: Re: I am willing to sort out Kde.org
From: "Mr Bulldog" <bulldogsay () gmail ! com>
Date: 2006-04-18 13:54:57
Message-ID: bbdc67730604180654ifc3244es53da7771aa7f5d88 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
so the negative points are to consider speed and security. Fair enough if w=
e
can design a good system, that is unique, easy for people to use. It can
just be as good and we can probably just use html file for the main body of
the page like the current system but neater.
Alright, I'll start coming up with a solution, as i'd rather people say, we
don't want a common cms because it is not safe and slow. than just we might
consider it.
thanks for your reasoning
Luke Parry
On 18/04/06, Adam Tulinius <adam@hackersbay.org> wrote:
>
> On Tuesday 18 April 2006 15:30, Mr Bulldog wrote:
> > Having a content management system would be a lot better, I'll rasie
> some
> > points.
> >
> >
> > - Easier to manage pages, smaller websites
> > - Can use a WYISWYG editor, make it easier for people who might not
> > want to use web programs such as quanta or nvu
> people access the pages with svn. i don't think they need quanta or
> anything
> like that.
> > - Better link and system navigation
> > - Better News and Feed usage
>
> > - Can have modules on pages, that extend functionaility much further
> > without needing more development
> > - Can have registered users if needs be.
> > - Can use databases, to store data, instead of having seperate pages
> > - Very modular and tidy infastrcture which will have security
> > updates.
>
> yes, but the system will be more vulnerable than now. a site using a
> CMS-system is more likely to be hacked/cracked, than one that uses it's
> own
> software.
>
> > +We have got a system that can be easily hacked for our needs, and once
> set
> > up can easily be applied to smaller sub sites. Spreadkde uses drupal,
> > oxygen uses wordpress. Even if it is a simple on it would help a lot.
> >
> > Having a cms run, a large website is quite important, as how many
> sections
> > are there for kde related stuff. Compare it to gnome.org, they hardly
> have
> > as much, fair enough having custom made pages or system is suited for
> them.
>
> Yes, but a CMS will be slower than more or less static pages. that has to
> be
> taken into custody too - it could result in the need of a faster server.
>
> > Can you think on about this?
> >
> > Luke Parry
>
>
> Adam Tulinius
> _______________________________________________
> kde-www mailing list
> kde-www@kde.org
> https://mail.kde.org/mailman/listinfo/kde-www
>
[Attachment #5 (text/html)]
so the negative points are to consider speed and security. Fair enough if we can \
design a good system, that is unique, easy for people to use. It can just be as good \
and we can probably just use html file for the main body of the page like the current \
system but neater. <br><br>Alright, I'll start coming up with a solution, as i'd \
rather people say, we don't want a common cms because it is not safe and slow. than \
just we might consider it.<br><br>thanks for your reasoning<br><br>Luke Parry \
<br><br><div><span class="gmail_quote">On 18/04/06, <b class="gmail_sendername">Adam \
Tulinius</b> <<a href="mailto:adam@hackersbay.org">adam@hackersbay.org</a>> \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Tuesday 18 April 2006 \
15:30, Mr Bulldog wrote:<br>> Having a content management system would be a lot \
better, I'll rasie some<br>> \
points.<br>><br>><br>> - Easier to manage pages, \
smaller websites<br> > - Can use a WYISWYG editor, make it \
easier for people who might not<br>> want to use web \
programs such as quanta or nvu<br>people access the pages with svn. i don't think \
they need quanta or anything<br>like that. <br>> - Better \
link and system navigation<br>> - Better News and Feed \
usage<br><br>> - Can have modules on pages, that extend \
functionaility much further<br>> without needing more \
development<br>> - Can have registered users if needs be. \
<br>> - Can use databases, to store data, instead of having \
seperate pages<br>> - Very modular and tidy \
infastrcture which will have \
security<br>> updates.<br><br>yes, but the system will be \
more vulnerable than now. a site using a <br>CMS-system is more likely to be \
hacked/cracked, than one that uses it's own<br>software.<br><br>> +We have got a \
system that can be easily hacked for our needs, and once set<br>> up can easily be \
applied to smaller sub sites. Spreadkde uses drupal, <br>> oxygen uses \
wordpress. Even if it is a simple on it would help a lot.<br>><br>> Having a \
cms run, a large website is quite important, as how many sections<br>> are there \
for kde related stuff. Compare it to <a href="http://gnome.org">gnome.org</a>, they \
hardly have<br>> as much, fair enough having custom made pages or system is suited \
for them.<br><br>Yes, but a CMS will be slower than more or less static pages. that \
has to be <br>taken into custody too - it could result in the need of a faster \
server.<br><br>> Can you think on about this?<br>><br>> Luke \
Parry<br><br><br>Adam Tulinius<br>_______________________________________________<br> \
kde-www mailing list<br><a href="mailto:kde-www@kde.org">kde-www@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-www">https://mail.kde.org/mailman/listinfo/kde-www</a><br></blockquote></div><br>
_______________________________________________
kde-www mailing list
kde-www@kde.org
https://mail.kde.org/mailman/listinfo/kde-www
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic