<?xml version="1.0" encoding="utf-8"?> 
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"> 
<channel> 
	<title>Capefish</title> 
	<link>http://capefish.org/talk</link> 
	<description>RSS feed for capefish.org</description> 
	<language>en</language> 
	<atom:link href="http://capefish.org/talk" rel="self" type="application/rss+xml" />
	

<item> 
	<title>RSS—Everywhere!</title> 
	<description><![CDATA[<h1>RSS—Everywhere!</h1>

<p>As of this morning’s <code>db422ba…</code> commit, each and every page can now have an RSS feed listing its children. Just point your feed reader at http://my.domain/path/to/page.xml and Capefish will serve up RSS 2.0 for that page’s children. Checkitout: <a href="/talk.xml">RSS for this page</a>.</p>]]></description>  
	<pubDate>Mon, 27 Oct 2008 13:16:58 -0400</pubDate>
	<guid isPermaLink="true">http://capefish.orgtalk/RSS-everywhere</guid>
</item>


<item> 
	<title>Authentication Makes It Happen</title> 
	<description><![CDATA[<h1>Authentication Makes It Happen</h1>

<p>Access to the site overview and page editor are now modulo authentication against the config/auth.passwd file.</p>

<p>If you lack this file, the site is basically a historyless wiki—so make sure you <code>script/basic_user add your-username >> config/auth.passwd</code> today!</p>]]></description>  
	<pubDate>Mon, 27 Oct 2008 13:16:58 -0400</pubDate>
	<guid isPermaLink="true">http://capefish.orgtalk/authentication-makes-it-happen</guid>
</item>


<item> 
	<title>WYSI-what now?</title> 
	<description><![CDATA[<h1>WYSI-<em>what</em> now?</h1>

<p>WYSIWYG: <em>what you see is what you get</em>. Hopefully.</p>

<p>After a short night of Dr. Pepper and <a href="http://jquery.com">jQuery</a>, rich-text editing is available. It’s in true WYSIWYG style: the page is presented as it looks when you load it, only when you click on the content you can add to it.</p>

<p>It’s a first step towards the full functionality that I want to eventually add, notably lacking controls for image insertion, links, or even bold/italic text. ERb content (i.e. anything in <code>&lt;%…%&gt;</code> sections) are placed inside a <code>&lt;span&gt;</code> which is hidden by the CSS: they’re preserved, but not editable. (I don’t intend to make them editable via the web editor; if you want to insert ERb content, edit the files in the /pages directory.)</p>

<p>Still, not bad for a start!</p>]]></description>  
	<pubDate>Mon, 27 Oct 2008 13:16:58 -0400</pubDate>
	<guid isPermaLink="true">http://capefish.orgtalk/wysi-what-now</guid>
</item>
</channel> 
</rss>