From owner-freebsd-www Tue Sep 25 18:48: 9 2001 Delivered-To: freebsd-www@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 5B67B37B419; Tue, 25 Sep 2001 18:48:02 -0700 (PDT) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:290:27ff:fe98:c0b7]) by white.imgsrc.co.jp (Postfix) with ESMTP id AFF2324D22; Wed, 26 Sep 2001 10:48:00 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2:2d0:b7ff:fea0:d487]) by black.imgsrc.co.jp (Postfix) with ESMTP id C9AEAD1406; Wed, 26 Sep 2001 10:47:59 +0900 (JST) Date: Wed, 26 Sep 2001 10:47:58 +0900 Message-ID: <7m1ykud8oh.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: doc@freebsd.org Subject: Re: Branching www/ for XML development In-Reply-To: <20010925173240.F31744@clan.nothing-going-on.org> References: <20010921001517.N1162@clan.nothing-going-on.org> <20010922113521.W1162@clan.nothing-going-on.org> <20010925173240.F31744@clan.nothing-going-on.org> User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 4) (Artificial Intelligence) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-www@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At Tue, 25 Sep 2001 16:58:17 +0000 (UTC), nik wrote: > Separation of content and formatting > ------------------------------------ > > Where possible, I'd like the content that people author to be separated from > the formatting. We should provide; > > * A standard template for people to write new pages > * Stylesheets, and classes, for specific presentation effects > * No author should need to write "" in their document, or use > other formatting tricks like that. We either use CSS, or, if browser > support is poor, we use CSS in the documents, and let the XSL stylesheets > embed the browser specific formatting as necessary > * A library of reusable content that can be dropped in to the page > * Facilities to help ensure that internal links are correct Totally agreed in concept. > Page layout > ----------- Is this toppage layout, or standard template for each pages? If this is standard template, I think we should talk about whether we need left/right navigation. IMHO these navigations narrow body area and reduce readability of contents. > Page description language > ------------------------- > > To enforce the style guidelines, don't let authors write a complete HTML > page. Instead, give them a cut-down markup language suitable for what they > need to do, allowing us to enforce the look and feel. Do you think we can enforce our style guidelines to writers? Defining new schema may be overkill. My suggestion is using XHTML as base schema and adding extentions for our local use. # Of course, we can use XSLT to translate XHTML to XHTML. > Building the web site > --------------------- ... > This suggests to me that naming everything with .xml extension might not be > the best way to do it. If everything has a .xml extension, irrespective of > its schema, then we can't write Makefiles that use SUFFIX rules to > automatically convert documents to HTML. Yes, we should use (or create) proper filename suffix to express its schema. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message