ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <angerweit@gmx.net>
Subject: Re: [NTG-context] Context manuals
Date: Sun, 20 Oct 2002 19:48:36 +0200	[thread overview]
Message-ID: <200210201948.36535.angerweit@gmx.net> (raw)
In-Reply-To: <20021018224445.0e446ade.morawski@gmx.net>

Am Freitag, 18. Oktober 2002 22:44 schrieb Jens-Uwe Morawski:
> > While nobody seems to be interested in helping to expand this FAQ
> > database, I'm thinking about replacing it with a CMS like PostNuke.
> Hmm, wonder what this is. But, hey, i'm interested in your FAQ.

Thank you for volunteering!

What a CMS is? "Content Management System", a portal frame etc.
PostNuke is based on PHPNuke, written in PHP (what I can use on "my" server).

> - i don't want to enter those many FAQs via the web-interface

I would take SQL or something other, too.

> - IMO a FAQ should support different topics/sections (maybe also sub... )

You are right, and that's the reason why I will change the actual structure.

But at a first glance I found that such a CMS (or at least PostNuke) is not 
what we need here:
-- I look for one CMS for all of my different pages, therefore it must be 
multilingual: most is only interesting in german, but this FAQ will stay 
english etc. (PN *is* multilingual, but not in the needed way)
-- It must be possible to mirror the whole system in an easy way between the 
public web server and my local (dial-up) LAN. (Unsure if the several database 
tables of PN will survive dumping, copying etc.)
-- Not only you but me too should be able to prepare entries offline (that's 
one reason for mirroring); CMS seem to be shrinked to the web interface.
-- We need a simple user management. The CMS would provide that; what I do at 
the moment is too complicated for more than a few users -- I use "htaccess" 
files, that is, users must be added in a users and a group file for access 
and additionally in the database for information like homepage that the user 
himself may change. I don't know how to write a secure user accounting 
myself.

> - the KEYWORD field should be replaced by a drop-down menu,
>   since the user cannot know what key-words are available

No, I don't think so. Some structure should/will be given fixed,
but authors should enter keywords themselves -- keywords are searched and 
should be found with an other than the visible question.

Structure/hierarchy is needed for an complete ConTeXt/PDF output, that 
shouldn't be totally chaotic...

Grüßlis vom Hraban!
-- 
Henning Hraban Ramm
Minervaweg 2
CH-8280 Kreuzlingen
Telefon +41-71-6712494
---
http://www.angerweit.de
http://www.fiee.net
http://www.ramm.ch
---
_______________________________________________
ntg-context mailing list
ntg-context@ref.ntg.nl
http://ref.ntg.nl/mailman/listinfo/ntg-context


  parent reply	other threads:[~2002-10-20 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18  2:32 John Culleton
2002-10-18 18:48 ` Henning Hraban Ramm
2002-10-18 20:44   ` Jens-Uwe Morawski
2002-10-20 16:56     ` Hans Hagen
2002-10-20 17:48     ` Henning Hraban Ramm [this message]
2002-10-20 18:42       ` Hans Hagen
2002-10-21 12:00       ` Jens-Uwe Morawski
2002-10-21 18:15         ` [NTG-context] FAQ structure (was: Context manuals) Henning Hraban Ramm
2002-10-21 21:22           ` [NTG-context] FAQ structure Jens-Uwe Morawski
2002-10-22  8:59         ` [NTG-context] Context manuals Hans Hagen
2002-10-22 19:34           ` Henning Hraban Ramm
2002-10-22 23:23             ` Hans Hagen
2002-10-23 19:15               ` Henning Hraban Ramm
2002-10-23 22:00                 ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200210201948.36535.angerweit@gmx.net \
    --to=angerweit@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).