Re: Layout graphic ideas

[Jon Parise <jon@xxxxxxxxxxxxx>]

On Tue, Feb 24, 2004 at 03:03:32AM +0000, Justin C. Sherrill wrote:

> > I think that looks swell.  My only suggestion is to apply more of a
> > heading style to the centered titles in the content section (the
> > "Dealing with Package Installation" text on the "packages" page, for
> > example).
> 
> I haven't touched that yet, just cause some of the body text could be
> cleaned up too.  If you really want to scratch the itch, though, a patch
> would be handy... 
 
Try the attached patch for starters.

-- 
Jon Parise (jon@xxxxxxxxxxxxx)  ::  "Scientia est Potentia"

Index: data/stylesheet.css
===================================================================
RCS file: /cvs/site/data/stylesheet.css,v
retrieving revision 1.8
diff -u -r1.8 stylesheet.css
--- data/stylesheet.css	25 Feb 2004 15:36:09 -0000	1.8
+++ data/stylesheet.css	29 Feb 2004 22:06:03 -0000
@@ -28,6 +28,7 @@
 H1 {
    font-size : 124%;
    color: #990000; 
+   text-align: center;
 }
    
 H2 {
Index: data/docs/index.cgi
===================================================================
RCS file: /cvs/site/data/docs/index.cgi,v
retrieving revision 1.7
diff -u -r1.7 index.cgi
--- data/docs/index.cgi	21 Feb 2004 02:34:50 -0000	1.7
+++ data/docs/index.cgi	29 Feb 2004 22:06:29 -0000
@@ -4,7 +4,7 @@
 
 $TITLE(The DragonFly BSD Project)
 
-<CENTER>Documentation</CENTER>
+<H1>Documentation</H1>
 <P>
 <TABLE>
 <TR>
Index: data/goals/caching.cgi
===================================================================
RCS file: /cvs/site/data/goals/caching.cgi,v
retrieving revision 1.2
diff -u -r1.2 caching.cgi
--- data/goals/caching.cgi	11 Aug 2003 02:24:47 -0000	1.2
+++ data/goals/caching.cgi	29 Feb 2004 22:06:40 -0000
@@ -4,7 +4,7 @@
 
 $TITLE(DragonFly - A Scaleable Caching Infrastructure)
 
-<CENTER>Caching Infrastructure Overview</CENTER>
+<H1>Caching Infrastructure Overview</H1>
 <P>
 Our goal is to create a flexible dual-purpose caching infrastructure which
 mimics the well known and mature MESI (Modified Exclusive Shared Invalid)
Index: data/goals/index.cgi
===================================================================
RCS file: /cvs/site/data/goals/index.cgi,v
retrieving revision 1.2
diff -u -r1.2 index.cgi
--- data/goals/index.cgi	11 Aug 2003 02:24:47 -0000	1.2
+++ data/goals/index.cgi	29 Feb 2004 22:07:04 -0000
@@ -4,7 +4,7 @@
 
 $TITLE(DragonFly - Extreme BSD Evolution, The Road to the Future)
 
-<CENTER>What is it?</CENTER>
+<H1>What is it?</H1>
 <P>
 DragonFly is going to be a multi-year project.  It will take a lot of groundwork
 to even approach the goals we outline here.  By clicking along the left
Index: data/goals/iomodel.cgi
===================================================================
RCS file: /cvs/site/data/goals/iomodel.cgi,v
retrieving revision 1.3
diff -u -r1.3 iomodel.cgi
--- data/goals/iomodel.cgi	20 Nov 2003 20:38:34 -0000	1.3
+++ data/goals/iomodel.cgi	29 Feb 2004 22:06:54 -0000
@@ -3,7 +3,7 @@
 # $DragonFly: site/data/goals/iomodel.cgi,v 1.3 2003/11/20 20:38:34 hmp Exp $
 
 $TITLE(DragonFly - I/O Device Operations)
-<CENTER>New I/O Device Model</CENTER>
+<H1>New I/O Device Model</H1>
 <P>
 I/O is considerably easier to fix then VFS owing to the fact that
 most devices operate asynchronously already, despite having a semi-synchronous
Index: data/goals/messaging.cgi
===================================================================
RCS file: /cvs/site/data/goals/messaging.cgi,v
retrieving revision 1.3
diff -u -r1.3 messaging.cgi
--- data/goals/messaging.cgi	1 Feb 2004 15:59:52 -0000	1.3
+++ data/goals/messaging.cgi	29 Feb 2004 22:07:14 -0000
@@ -3,7 +3,7 @@
 # $DragonFly: site/data/goals/messaging.cgi,v 1.3 2004/02/01 15:59:52 justin Exp $
 
 $TITLE(DragonFly - The Port/Messaging Model)
-<CENTER>The Port/Messaging Model</CENTER>
+<H1>The Port/Messaging Model</H1>
 <P>
 DragonFly will have a lightweight port/messaging API to go along with its
 lightweight kernel threads.  The port/messaging API is very simple
Index: data/goals/packages.cgi
===================================================================
RCS file: /cvs/site/data/goals/packages.cgi,v
retrieving revision 1.3
diff -u -r1.3 packages.cgi
--- data/goals/packages.cgi	6 Jan 2004 20:44:50 -0000	1.3
+++ data/goals/packages.cgi	29 Feb 2004 22:07:25 -0000
@@ -3,7 +3,7 @@
 # $DragonFly: site/data/goals/packages.cgi,v 1.3 2004/01/06 20:44:50 justin Exp $
 
 $TITLE(DragonFly - Packaging up the UserLand)
-<CENTER>Dealing with Package Installation</CENTER>
+<H1>Dealing with Package Installation</H1>
 <P>
 Applications are such a godawful mess these days that it is hard to come
 up with a packaging and installation system that can achieve seamless
Index: data/goals/threads.cgi
===================================================================
RCS file: /cvs/site/data/goals/threads.cgi,v
retrieving revision 1.6
diff -u -r1.6 threads.cgi
--- data/goals/threads.cgi	22 Feb 2004 15:34:35 -0000	1.6
+++ data/goals/threads.cgi	29 Feb 2004 22:07:54 -0000
@@ -3,7 +3,7 @@
 # $DragonFly: site/data/goals/threads.cgi,v 1.6 2004/02/22 15:34:35 justin Exp $
 
 $TITLE(DragonFly - Light Weight Kernel Threading Model)
-<CENTER>The Light Weight Kernel Threading Model</CENTER>
+<H1>The Light Weight Kernel Threading Model</H1>
 <P>
 DragonFly employs a light weight kernel threading (LWKT) model at its core.
 Each process in the system has an associated thread, and most kernel-only
@@ -62,7 +62,7 @@
 well, which will allow traditional hardclock() and statclock() distribution
 to operate across all cpus.
 <P>
-<CENTER>The IPI Messaging Subsystem</CENTER>
+<H1>The IPI Messaging Subsystem</H1>
 <P>
 The LWKT model implements an asynchronous messaging system for communication
 between cpus.  Basically you simply make a call providing the target cpu with
@@ -77,7 +77,7 @@
 are not allowed to block in any manner whatsoever.  IPI messages are used
 to do things like schedule threads and free memory belonging to other cpus.
 <P>
-<CENTER>The IPI-based CPU Synchronization Subsystem</CENTER>
+<H1>The IPI-based CPU Synchronization Subsystem</H1>
 <P>
 The LWKT model implements a generalized, machine independant cpu
 synchronization API.  The API may be used to place target cpu(s) into a 
@@ -101,8 +101,7 @@
 back functions tend to work just like the callback functions used in the
 IPI messaging subsystem.
 <P>
-<CENTER>Serializing Tokens</CENTER>
-
+<H1>Serializing Tokens</H1>
 <P>
 A serializing token may be held by any number of threads simultaneously.
 A thread holding a token is guaranteed that no other thread also
Index: data/goals/userapi.cgi
===================================================================
RCS file: /cvs/site/data/goals/userapi.cgi,v
retrieving revision 1.4
diff -u -r1.4 userapi.cgi
--- data/goals/userapi.cgi	6 Jan 2004 21:11:05 -0000	1.4
+++ data/goals/userapi.cgi	29 Feb 2004 22:08:02 -0000
@@ -3,7 +3,7 @@
 # $DragonFly: site/data/goals/userapi.cgi,v 1.4 2004/01/06 21:11:05 justin Exp $
 
 $TITLE(DragonFly - User API)
-<CENTER>Creating a Portable User API</CENTER>
+<H1>Creating a Portable User API</H1>
 <P>
 Most standard UNIX systems employ a system call table through which many types
 of data, including raw structures, are passed back and forth.   The biggest
Index: data/goals/vfsmodel.cgi
===================================================================
RCS file: /cvs/site/data/goals/vfsmodel.cgi,v
retrieving revision 1.2
diff -u -r1.2 vfsmodel.cgi
--- data/goals/vfsmodel.cgi	11 Aug 2003 02:24:47 -0000	1.2
+++ data/goals/vfsmodel.cgi	29 Feb 2004 22:08:12 -0000
@@ -3,7 +3,7 @@
 # $DragonFly: site/data/goals/vfsmodel.cgi,v 1.2 2003/08/11 02:24:47 dillon Exp $
 
 $TITLE(DragonFly - VFS/filesystem Device Operations)
-<CENTER>The New VFS Model</CENTER>
+<H1>The New VFS Model</H1>
 <P>
 Fixing the VFS subsystem is probably the single largest piece of work
 we will be doing.  VFS has two serious issues which will require a lot
Index: data/main/download.cgi
===================================================================
RCS file: /cvs/site/data/main/download.cgi,v
retrieving revision 1.18
diff -u -r1.18 download.cgi
--- data/main/download.cgi	26 Feb 2004 18:50:42 -0000	1.18
+++ data/main/download.cgi	29 Feb 2004 22:08:52 -0000
@@ -4,7 +4,7 @@
 
 $TITLE(DragonFly - Download)
 <P>
-<CENTER><H2>Obtaining DragonFly for your system</H2></CENTER>
+<H1>Obtaining DragonFly for your system</H1>
 There are several ways to install DragonFly on your computer.  
 Some of these methods require prior BSD experience with tools like 
 disklabel or boot0cfg, and we have no completed installation 
Index: data/main/index.cgi
===================================================================
RCS file: /cvs/site/data/main/index.cgi,v
retrieving revision 1.4
diff -u -r1.4 index.cgi
--- data/main/index.cgi	16 Feb 2004 05:16:40 -0000	1.4
+++ data/main/index.cgi	29 Feb 2004 22:09:03 -0000
@@ -4,7 +4,7 @@
 
 $TITLE(The DragonFly BSD Project)
 
-<CENTER>What is it?</CENTER>
+<H1>What is it?</H1>
 <P>
 DragonFly is an operating system and environment designed to be the logical
 continuation of the FreeBSD-4.x OS series.  These operating systems belong