cvs commit: www/test/style advanced.css

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Tue Sep 2 15:27:56 PDT 2003


jeroen      03/09/02 16:27:56

  Modified:    test     website-bottom.html website-top.html
               test/style advanced.css
  Log:
  Removed the website's roadmap and updated the website information page.
  
  Revision  Changes    Path
  1.18      +16 -38    www/test/website-bottom.html
  
  Index: website-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/website-bottom.html,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- website-bottom.html	1 Sep 2003 21:33:00 -0000	1.17
  +++ website-bottom.html	2 Sep 2003 22:27:56 -0000	1.18
  @@ -2,56 +2,34 @@
   		<p><a href="#header">Back to the top.</a></p>
   
   	<h3 id="todo">Todo</h3>
  -	<h4>Roadmap:</h4>
  -	<ol>
  -		<li>Finish the todo list (still in progress...)</li>
  -		<li>Call for testers; collect bug reports</li>
  -		<li>Fix bugs</li>
  -		<li>Adjust server setup and</li>
  -		<li>launch the site, celebrate (hopefully, beginning of September)</li>
  -	</ol>
   
   	<h4>Dynamic newspages</h4>
  -		<p>The goal is to make each section's news page reflect the most current state of development. The result would be an extract of {b}lfs-book and {b}lfs-dev which is useful as a development overview and reference point. In order to reach that goal, we need some scripts which feed development messages into the website. We can automate Bugzilla and CVS, while interesting e-mails can be added manually (this is currently done on <a href="lfs/news.html">the LFS news page</a> and the <a href="blfs/news.html">BLFS news page</a>).</p>
  -		<p>To achieve this we need two scripts.</p>
  -		<h5>CVS script</h5>
  -		<p><em>Status: <strong>done (except for news archiving)</strong>. See <a href="http://www.linuxfromscratch.org/pipermail/website/2003-August/000374.html">Anderson Lizardo's perl script</a>.</em></p>
  +		<p>Each section of lfs, blfs, hints and alfs have a news page. These should reflect the most current state of development which includes Bugzilla status, CVS commit logs and important maillinglist discssions. The result is useful as a development overview and reference point, both for the LFS team and for outside users. Currently the only thing missing are the Bugzilla messages:</p>
   		<h5>Bugzilla script</h5>
   		<p>Write a script which feeds Bugzilla messages into the project's newspages. The information which needs to be extracted is the same (who, when and what bug is reported). Additionally, it should contain a link to the bug page. This script should be triggered whenever Bugzilla changes (a bug is added, resolved, commented etc.). This way, active LFS'ers can read the website daily, be aware of the current state of LFS and be able to directly comment on bugs. </p>
  -		<p>Got some usefull replies from the Bugzilla developers; it seems that <a href="http://bugzilla.mozilla.org/attachment.cgi?id=109161&action=view">fine_whine.pll</a> is usually used for this (described in <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=185090">bug 185090</a>). This script should at least be edited so it spits out content which we can use, similar to the solution we've devised for cvs2cl.pl.</p>
  -		<p><em>Status: <strong>no solution yet</strong>. Please <a href="http://linuxfromscratch.org/mailman/listinfo/website">e-mail the website list</a> if you're able to help customize the above script.</em></p>
  +		<p>Got some usefull replies from the Bugzilla developers; it seems that <a href="http://bugzilla.mozilla.org/attachment.cgi?id=109161&action=view">fine_whine.pl</a> is usually used for this (described in <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=185090">bug 185090</a>). This script should at least be edited so it spits out content which we can use, similar to the solution we've devised for cvs2cl.pl.</p>
  +		<p><em class="highlight">Status: <strong>no solution yet</strong>. Please <a href="http://linuxfromscratch.org/mailman/listinfo/website">e-mail the website list</a> if you're able to help customize the above script.</em></p>
   		<h5>News archives</h5>
  -		<p>Figure out a way to automatically archive news pages each month. This would have the advantage that no news is lost and that the news pages are bookmarkable. Therefore, it should be a symlink to news/year/month.html (where year and month are numerical values of course). This can be done from a crontab. The old news pages are kept on archives.linuxfromscratch.org so there's no additional burden for the mirrors.</p>
  -		<p>Refer to <a href="http://linuxfromscratch.org/pipermail/website/2003-August/000472.html">this message</a>, <a href="http://linuxfromscratch.org/pipermail/website/2003-August/000469.html">this message</a> and <a href="http://linuxfromscratch.org/pipermail/website/2003-August/000471.html">this message</a>.</p>
  -		<p>News should be kept separate from the html files and added to them via a script. Each section gets their own news file, called news-YYYY.txt, where YYYY is the current year. All news from a project will be added to this file and a new file will be used for each year. The current newsfile will be parsed by the newsarchiving script. This script should fulfill the following functions:</p>
  -		<ol>
  -			<li>Create a newspage with the five last news entries from the project-specific and general news resources (these will form the project front pages - <a href="lfs/news.html">example</a>. This function should also create bookmarkable links to the news archive with each newsitem. The current newspage (for example lfs/news.html) is actually a symlink to the archives (news/lfs/YYYY/MM.html). This symlink should be recreated each month by the script.</li>
  -			<li>Generate the news archive. It should (1) convert relative links to absolute links (for example: ../lfs/stable.html should become http://linuxfromscratch.org/lfs/stable.html) and (2) split news in the following URL: linuxfromscratch.org/news/YYYY/MM.html for general news and linuxfromscratch.org/news/PROJECT/YYYY/MM.html for project-specific news. </li>
  -		</ol>
  -		<p><em>Status: <strong>in progress</strong>.  Anderson Lizardo is working on a perl script which intends to achieve this.</em></p>
  +		<p><em>Status: <strong>done</strong>. See <a href="http://www.linuxfromscratch.org/pipermail/website/2003-September/000609.html">Anderson Lizardo's script</a>.</em></p>
   	<h4>Convert hard-coded pages</h4>
  -		<p>Next to the scripts there are a couple of pages which need to be converted to using the new design's layout. These are:</p>
  -		<ul>
  -			<li><a href="http://search.linuxfromscratch.org">The default search interface</a>. We should use <a href="search.html">this page</a>. which is a matter of copying it to the search domain directory and symlinking some stuff. We need more search options, mainly the ability to search specific mailing lists and a way to specify a date range. <br />
  -				<em>Status: <strong>in progress</strong>. Gerard is working on this. The final page will become the default page on search.linuxfromscratch.org.</em></li>
  -			<li>The search results page. Currently it looks butt-ugly and out-of-synch even with the old website. <br />
  -				<em>Status: <strong>done</strong>.<a href="http://www.linuxfromscratch.org/~jeroen/test/TemplateDefault.pm">test template</a> available. Untested.</em></li>
  -			<li><a href="http://linuxfromscratch.org/cgi-bin/lfscounter.cgi">The LFS counter</a>.<br />
  -				<em>Status: <strong>done</strong>. <a href="http://linuxfromscratch.org/cgi-bin/lfscounter.cgi">Available for testing.</a></em></li>
  -			<li><a href="http://linuxfromscratch.org/mailman/listinfo/lfs-chat">The mailinglist information pages</a>. <br />
  -				<em>Status: <strong>mostly done</strong>. <a href="http://www.linuxfromscratch.org/~jeroen/mailman">test templates</a> available. Untested.</em></li>
  -			<li><a href="http://bugs.linuxfromscratch.org/">The bugzilla pages</a>. Would be alot of work to get these to validate against xhtml-1.1. <br />
  -				<em>Status: <strong>mostly done</strong>. Untested though.</em></li>
  -		</ul>
  +		<p>Next to the scripts there are a couple of pages which need to be converted to using the new design's layout. This is work in progress and not a showstopper for site launch.</p>
  +		<dl>
  +			<dt><a href="http://search.linuxfromscratch.org">The default search interface</a></dt>
  +				<dd>We should use <a href="search.html">this page</a>. which is a matter of copying it to the search domain directory and symlinking some stuff. We need more search options, mainly the ability to search specific mailing lists and a way to specify a date range.
  +				<em>Status: <strong>in progress</strong>. Gerard is working on this. The final page will become the default page on search.linuxfromscratch.org.</em></dd>
  +			<dt>The mailinglist information pages</dt>
  +				<dd><em>Status: <strong>in progress</strong>. <a href="http://linuxfromscratch.org/mailman/listinfo/mailman-test">Current work online</a></em></dd>
  +			<dt><a href="http://bugs.linuxfromscratch.org/">The bugzilla pages</a>.</dt>
  +				<dd>It's a lot of work to get these to validate against xhtml-1.1.
  +				<em>Status: <strong>in progress</strong></em></dd>
  +		</dl>
   	<h4>Make the hints and patches lists dynamically generated</h4>
   		<p>Perhaps via a database, perhaps via scripts which parse the files.<br />
  -		<em>Status: <strong>mostly done</strong>. Untested though.</em></p>
  +		<em class="highlight">Status: <strong>not started yet</strong></em></p>
   	<h4>Adjust server setup</h4>
   		<p>Replace the current subdomains (/home/httpd/{beyond,automated,hints,patches,archives,bugs,downloads,search,cvs}) with symlinks to the original location in /home/httpd/linuxfromscratch.org/{blfs,alfs,hints,patches}. This way the subdomains keep working transparantly.</p>
   		<p>We should also update the rsync scripts so that mirrors only mirror the content. Perhaps we should also host the LFS and BLFS online books only on belgarath (this shaves off another 8.4Mb for the mirrors). Else we'd have to up the diskspace requirements for mirrors to 10-20Mb instead of 5-10Mb.</p>
   		<p>See <a href="http://linuxfromscratch.org/pipermail/website/2003-August/000424.html">discussion</a></p>
  -	<h4>User testing</h4>
  -		<p>Finally, if most of the above is done (especially once the templates are implemented), we should call for as many LFS'ers as we can for testing the site so we can hammer out all remaining bugs and add them to the <a href="#browsers">browsers table</a>.</p>
   
   <h3 id="thanks">Acknowledgements</h3>
   	<p>The following people and organisations have been more than a great help while creating this website:</p>
  
  
  
  1.8       +7 -10     www/test/website-top.html
  
  Index: website-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/website-top.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- website-top.html	26 Aug 2003 07:43:06 -0000	1.7
  +++ website-top.html	2 Sep 2003 22:27:56 -0000	1.8
  @@ -91,17 +91,14 @@
   				<td><a href="http://www.konqueror.org">Konqueror</a></td>
   				<td><a href="http://www.kde.org/info/3.1.3.php">3.1.3</a></td>
   				<td><ul>
  -						<li>#pagenav apppears as a vertical list while it should be a horizontal list</li>
  -						<li>The footer images may appear next to each other while there should be some space between them</li>
  -						<li>Pages are too wide and have a horizontal scrolling bar. They should fill the browser viewport, not overflow it</li>
  +						<li>#pagenav sometimes apppears as a vertical list while it should be a horizontal list</li>
  +						<li>The footer images sometimes appear next to each other while there should be some space between them</li>
  +						<li>Pages are too wide and have a horizontal scrolling bar. They should fill the browser viewport, not overflow it (seems to be the case with many other websites too)</li>
   					</ul>
   				</td>
   			</tr><tr>
  -				<td rowspan="2"><a href="http://www.opera.com">Opera</a></td>
  -				<td><a href="http://www.opera.com/download/">6</a></td>
  -				<td>The list of available translations on the mirror pages is left-aligned while it should be right-aligned.</td>
  -			</tr><tr>
  -				<td><a href="http://www.opera.com/download/">7.11</a></td>
  +				<td><a href="http://www.opera.com">Opera</a></td>
  +				<td>6, <a href="http://www.opera.com/download/">7.1</a></td>
   				<td>None</td>
   			</tr><tr>
   				<td><a href="http://www.apple.com/safari/">Safari</a></td>
  @@ -120,10 +117,10 @@
   			</tr><tr>
   				<td><a href="http://www.microsoft.com/mac/products/internetexplorer/internetexplorer.aspx?pid=internetexplorer">5.2 Mac</a></td>
   				<td><ul>
  -						<li>#header links are incorrectly underlined</li>
  +						<li>None</li>
   					</ul>
   				</td>
  -			</tr>			
  +			</tr>
   		</tbody></table>
   		<p>Other grapical browsers or versions older than those mentioned above probably display the page but there might be bugs. We suggest you upgrade to a standards compliant browser like those above, but in case you're not able to, we <a href="http://linuxfromscratch.org/mailman/listinfo/website">accept patches to the stylesheet</a> if they solve your problems.</p>
   		<p>By using the <a href="http://www.w3.org" title="The independant body that governs the Internet">World Wide Web Consortium (W3C)</a> standards, the website is <a href="http://www.alistapart.com/stories/netscape/">future proof</a>.</p>
  
  
  
  1.10      +1 -1      www/test/style/advanced.css
  
  Index: advanced.css
  ===================================================================
  RCS file: /home/cvsroot/www/test/style/advanced.css,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- advanced.css	2 Sep 2003 20:43:59 -0000	1.9
  +++ advanced.css	2 Sep 2003 22:27:56 -0000	1.10
  @@ -37,7 +37,7 @@
   h5, h6 { font-size: 104%; font-style: italic; padding: 0 0 0 0.5em; color: #000;}
   
   p { padding: 0 0 0 1em; }
  -em.highlight, div.highlight { border: 1px solid #e80; color: #000; background-color: #fe8; }
  +em.highlight, { border: 1px solid #e80; color: #000; background-color: #fe8; display: block; }
   
   address { margin: 1em; padding: 1em; border: 1px solid #ddd; background-color: #eee;}
   
  
  
  



More information about the website mailing list