[98244] in tlhIngan-Hol
Re: [Tlhingan-hol] KLI Website
daemon@ATHENA.MIT.EDU (qurgh lungqIj)
Tue Mar 25 11:46:39 2014
In-Reply-To: <20140325083205.a41e5a76f06d90ef255b5a241771595e.a03955e68a.wbe@email01.secureserver.net>
From: qurgh lungqIj <qurgh@wizage.net>
Date: Tue, 25 Mar 2014 11:46:01 -0400
To: SuStel <sustel@trimboli.name>
Cc: "tlhingan-hol@stodi.digitalkingdom.org"
<tlhingan-hol@stodi.digitalkingdom.org>
Errors-To: tlhingan-hol-bounces@kli.org
--===============5221985138835162285==
Content-Type: multipart/alternative; boundary=bcaec5468c51f421b704f57040d1
--bcaec5468c51f421b704f57040d1
Content-Type: text/plain; charset=UTF-8
On Tue, Mar 25, 2014 at 11:32 AM, SuStel <sustel@trimboli.name> wrote:
> From: qurgh lungqIj <qurgh@wizage.net>
> > If there is a style guide and standardized CSS there won't be any issues
> > with this, as long as people are using standard HTML5. If a theme is
> > defined, then everyone can use the same building blocks to construct
> their
> > parts of the site. If the site uses some kind of CMS, then it's even
> easier
> > to keep things looking the same.
>
> I'm confused: are we talking about kli.org just pointing to other sites
> people build themselves, or are we talking about multiple sites hosted
> by the KLI and administered by volunteers? I was under the impression it
> was the latter, which would allow the use of a common content management
> system for uniformity. As a site administrator, I wouldn't choose HTML
> and CSS versions, for instance; I would use whatever tools and templates
> the KLI provided me, and just manage the content.
>
I was under the impression that the question you asked was still open and
neither option has been chosen yet.
Personally I've recommended that everything be hosted on the KLI site,
using some kind of central CMS (like WordPress). That would allow us to
manage most of the content, with some large pieces requiring their own
software (KLI Wiki, KLI Mailing list). CSS/HTML would be needed to develop
a theme for the CMS, but those styles can be easily be carried over to a
KLI Wiki sub-site or KLI Mailing List software (if it doesn't have a plugin
that works with the CMS package). There may be parts of the site that have
to be developed from scratch, and it's for those parts that a style guide
would be useful.
qurgh
--bcaec5468c51f421b704f57040d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Mar 25, 2014 at 11:32 AM, SuStel <span dir=3D"ltr"><<a h=
ref=3D"mailto:sustel@trimboli.name" target=3D"_blank">sustel@trimboli.name<=
/a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">From: qurgh lungqIj <<a href=3D"mailto:qu=
rgh@wizage.net">qurgh@wizage.net</a>><br>
<div class=3D"">> If there is a style guide and standardized CSS there w=
on't be any issues<br>
> with this, as long as people are using standard HTML5. If a theme is<b=
r>
> defined, then everyone can use the same building blocks to construct t=
heir<br>
> parts of the site. If the site uses some kind of CMS, then it's ev=
en easier<br>
> to keep things looking the same.<br>
<br>
</div>I'm confused: are we talking about <a href=3D"http://kli.org" tar=
get=3D"_blank">kli.org</a> just pointing to other sites<br>
people build themselves, or are we talking about multiple sites hosted<br>
by the KLI and administered by volunteers? I was under the impression it<br=
>
was the latter, which would allow the use of a common content management<br=
>
system for uniformity. As a site administrator, I wouldn't choose HTML<=
br>
and CSS versions, for instance; I would use whatever tools and templates<br=
>
the KLI provided me, and just manage the content.<br></blockquote><div><br>=
I was under the impression that the question you asked was still open and n=
either option has been chosen yet.=C2=A0<br><br>Personally I've recomme=
nded that everything be hosted on the KLI site, using some kind of central =
CMS (like WordPress). That would allow us to manage most of the content, wi=
th some large pieces requiring their own software (KLI Wiki, KLI Mailing li=
st). CSS/HTML would be needed to develop a theme for the CMS, but those sty=
les can be easily be carried over to a KLI Wiki sub-site or KLI Mailing Lis=
t software (if it doesn't have a plugin that works with the CMS package=
). There may be parts of the site that have to be developed from scratch, a=
nd it's for those parts that a style guide would be useful.<br>
<br>=C2=A0qurgh</div></div></div></div>
--bcaec5468c51f421b704f57040d1--
--===============5221985138835162285==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Tlhingan-hol mailing list
Tlhingan-hol@kli.org
http://mail.kli.org/mailman/listinfo/tlhingan-hol
--===============5221985138835162285==--
