<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>PS: What's up?: Stories by Christina Wodtke</title>
    <link>http://blog.publicsquarehq.com/person/1312</link>
    <pubDate>Fri, 01 Jun 2007 03:28:22 GMT</pubDate>
    <description>Stories by Christina Wodtke</description>
    <item>
      <title>New! Add RSS feeds to your Publication</title>
      <link>http://blog.publicsquarehq.com/view/new-add-rss-feeds-to</link>
      <guid>http://blog.publicsquarehq.com/view/new-add-rss-feeds-to</guid>
      <description>Erstwhile Matt Pelletier of EastMedia has just added the ability to add rss feeds as a way of populating content to the pages of your publication. It's a easy way to tie in blogs, or any outside ap with an RSS feed. For example, let's say you wanted to show the latest blog posts form friends using typepad, or say you wanted to pull in job listings from a job board... Just this!

&lt;pre&gt;
   &lt;ul&gt;
   {% feedreader url: 'http://digg.com/', max: 15 as link %}
     &lt;li&gt;&lt;a href="{{ link.href }}"&gt;{{ link.description }}&lt;/a&gt; 
     {{ link.extended }}&lt;/li&gt;
   {% endfeedreader %}
   &lt;/ul&gt; 
&lt;/pre&gt;</description>
      <pubDate>Fri, 01 Jun 2007 03:28:22 GMT</pubDate>
      <author>Christina Wodtke</author>
      <category>Tips and Tricks</category>
      <category>Update!</category>
    </item>
    <item>
      <title>EM and EN</title>
      <link>http://blog.publicsquarehq.com/view/em-and-en</link>
      <guid>http://blog.publicsquarehq.com/view/em-and-en</guid>
      <description>&lt;a href="/articles/emen"&gt;The Trouble With EM &#8217;n EN (and Other Shady Characters)&lt;/a&gt; by  &lt;a href="/authors/s/peterksheerin"&gt; Peter K Sheerin&lt;/a&gt; is the best article I've found on the En dash and the Em dash, and how to render them easily. 

&lt;blockquote&gt;&lt;strong&gt;The em dash&lt;/strong&gt; (&lt;code&gt;&amp;amp;#8212;&lt;/code&gt;) is used to indicate a sudden break in thought (&#8220;I was thinking about writing a&#8212;what time did you say the movie started?&#8221;), a parenthetical statement that deserves more attention than parentheses indicate, or instead of a colon or semicolon to link clauses. It is also used to indicate an open range, such as from a given date with no end yet (as in &#8220;Peter Sheerin [1969&#8212;] authored this document.&#8221;), or vague dates (as a stand-in for the last two digits of a four-digit year).&lt;/p&gt;

&lt;br&gt;

&lt;p&gt;&lt;strong&gt;The en dash&lt;/strong&gt; (&lt;code&gt;&amp;amp;#8211;&lt;/code&gt;) is used to indicate a range of just about anything with numbers, including dates, numbers, game scores, and pages in any sort of document.&lt;/p&gt;&lt;/blockquote&gt;

These characters are used so often by publishers &amp;#8212; why don't WYSIWYG pay them more attention?</description>
      <pubDate>Wed, 20 Jun 2007 07:00:00 GMT</pubDate>
      <author>Christina Wodtke</author>
      <category>Lessons Learned</category>
    </item>
    <item>
      <title>2.0 for everyone</title>
      <link>http://blog.publicsquarehq.com/view/2-0-for-everyone</link>
      <guid>http://blog.publicsquarehq.com/view/2-0-for-everyone</guid>
      <description>Great article &lt;a title="ByrneRenaissanceFINAL.pdf (application/pdf Object)" href="http://cmswatch.com/images/ByrneRenaissanceFINAL.pdf"&gt;The WCM Renaissance(pdf)&lt;/a&gt;, and particularly gratifying is this quote:

&lt;blockquote&gt;Web 2.0 is also exposing cracks in WCM space. Much the same way that WCM specialists accuse ECM vendors of "not getting it," many WCM tools that only recently added blog and wiki functionality suffer from complicated interfaces, unfriendly URLs, and other un-Web 2.0 shortcomings.

In particular, the prevalence of sexy Ajax interfaces on the public web makes traditional WCM contributor interfaces seem very outdated. Vendors point out that re-engineering their product UIs is not a trivial matter.

Growing interest in user-generated content (UGC) has also created architectural challenges for integrated WCM packages the same way that the rise of the web caught many document management vendors flat-footed. In enterprise settings, most web-content management services and repositories live in a protected zone behind the firewall, and don't naturally lend themselves to authors coming in from the public web.

To be sure, most enterprise customers don't know yet what it means to "manage" user-generated content, and important questions are stalling some initiatives. Should we put UGC through an approval workflow? Do we need to archive it? Do we expose our internal classification scheme so we can cross-reference internal and user content? And so on.&lt;/blockquote&gt;

I couldn't have paid someone to better explain the PublicSquare approach. USG is a gruesome acronym, mind you, but the idea is crucial: publish &lt;strong&gt;with &lt;/strong&gt;your audience, not &lt;strong&gt;at&lt;/strong&gt; them. </description>
      <pubDate>Wed, 27 Jun 2007 17:00:08 GMT</pubDate>
      <author>Christina Wodtke</author>
      <category>In the Press</category>
    </item>
    <item>
      <title>Five Thoughts on Publishing</title>
      <link>http://blog.publicsquarehq.com/view/five-thoughts-on</link>
      <guid>http://blog.publicsquarehq.com/view/five-thoughts-on</guid>
      <description>&lt;ol&gt;&lt;li&gt;Publishing does not belong to publishers. It's a fundamental activity that belongs to human life; it's communication. One-to-many has irreplaceable value. Blogs are published diaries, newspapers are there to tell you what's happening in the world, magazines to distract, entertain, educate. But in between those extremes we have a rich, fertile land full of publishing.&lt;ul&gt;
&lt;li&gt; Businesses publish. They have to buy coffee, and they have to publish. Newsletters, company reports, status updates, brochures. You have to communicate to your customers and unless you plan to call each one up by phone, you are going to publish. 
&lt;li&gt; Professional organizations publish. You gather with other nurses, or IAs, or engineers, or accountants to get better at your job, and the way you do that is to share what you've learned. From peer-reviewed papers to emailing lists, the professional organization exists most to exchange knowledge.
&lt;li&gt;Hobbyists publish. There is no delight on this earth that is as good as when its shared. Do you love fishing, knitting, lawn bowling, origami... doesn't matter, your love is always better when you share it. Like the professional organization, everyone strives to get better but now you are broadcasting out of personal pride. 
&lt;li&gt; Enthusiasts Publish. From spec miatas to organic produce, everyone has some funny little thing that lights them up inside. And those people can't stop looking to read more about it, and eventually when they run out, they start sharing what they know. Because its that great. And everyone should know its that great. 
&lt;li&gt;Schools- all school publish, from 'zines to newspapers. It's good for the kids.
&lt;li&gt;Localities- The Mountain View Voice is a newspaper, but still rooted in its 'hood more than the world, the Barron Neighborhood Association is a jumped up newsletter and every coop seems to have their own "what's happening" publication.&lt;/ul&gt;

&lt;li&gt; &lt;a href="http://www.eleganthack.com/archives/alexa-IAs.png"&gt;&lt;img alt="alexa-IAs.png" src="http://www.eleganthack.com/archives/alexa-IAs-thumb.png" width="250" height="158" hspace="5" vspace="5" align="right" /&gt;&lt;/a&gt;Blogging is less satisfying *and* less effective  than being with a group. I had coffee with &lt;a href="http://redcouch.typepad.com/'&gt;Shel Isreal&lt;/a&gt; the other day, and he admitted that many bloggers he knows were seeing their numbers go flat or drop. But groups have always outperformed individuals, no matter how august the individual. Take my baby, Boxes and Arrows. The (arguably) four most prestigious IA's can't touch B&amp;A's numbers. 

&lt;em&gt;(Note: mapped it a second time with peterme, and he's in the pack with the rest of us little fellows.)&lt;/em&gt;

And the same holds true for A List Apart and its very famous founder, Jeffrey Zeldman
&lt;a href="http://www.eleganthack.com/archives/alaVSzeldman.png"&gt;&lt;img alt="alaVSzeldman.png" src="http://www.eleganthack.com/archives/alaVSzeldman-thumb.png" width="250" height="157" hspace="5" vspace="5" align="right" /&gt;&lt;/a&gt;

It would be silly of me to even bother mapping a mommyblogger to maya's mom or babycenter.  Groups do better. Every member is also a writer, a fan, a marketeer, a copyeditor, a bugtracker -- there is power in the people, and more people more power. &lt;br clear="all'&gt;

&lt;li&gt; 90% of publishers are currently ignored. I'd like to argue that the vast majority of publishers are having to jury-rig the current set of tools to their use. Some are hacking blog tools, some hire a programmer to decrappify open source, others try to make Dreamweaver play nice with their team. Many cobble something together: basecamp+wordpress+dreamweaver+a wiki. If the vast majority of publishers are publishing as a secondary activity with other people, how come the tools so rarely reflect this? They are hard to use, expensive, missing features ... it's a mess.  There should be a happy place between typepad and interwoven. But not so much.

&lt;li&gt; The online world of publishing has segmented into the towers and the hoards. The towers are impermeable; from the small business's website down the street to the New York Times herself, the readers are ghettoized into forums where they content with chaos.  But what is the alternative? &lt;a href="http://www.eleganthack.com/archives/digg7-2-7.png"&gt;&lt;img alt="digg7-2-7.png" src="http://www.eleganthack.com/archives/digg7-2-7-thumb.png" width="250" height="172" hspace="5" vspace="5" align="left" /&gt;&lt;/a&gt;
Digg? Take a look at yesterday's headlines: money making scams and insults. Is this the shining future of citizen journalism?

There is a rising backlash against the lack of trustworthiness found in current citizen journalism; i.e. bloggers.  Previous posts capture some of the frustration against un-fact-checked, biased, half-truthed corporate shills and the rest of the rubble that makes ordinary peoples' lives actually worse. I've also blogged about the mess anonymous comments and posts can create from spam to trolls to actual cyberstalking.  It's time for responsibility and reputation. 

What if there is a middle group? What if we can combine editorial insight with the collective wisdom of the crowds? Do these two really have to be opposed? I think the future will take the best of old media and new, and create a far more participatory and engaging BUT trustworthy generation of publication, and in the best scenario that will also include Karl's Printshop down the street allowing his customers to give each other advice on how to make chapbooks and posters.

&lt;li&gt;Finally, and this is the most difficult for me to articulate, I believe the economy must evolve to support these folks. Maybe Karl the printer is good for awhile longer yet, and small businesses like him can consider their publishing a cost of doing business or even a loyalty play. But the bloggers are begging for a way to make a buck doing the thing they love, the thing that eats up their every waking hour. The enthusiasts, the hobbyists, the schools, and all the rest may not have much hope for making a living doing this anymore than folks who held a garage sale once a year thought they'd go pro before eBay showed up.  They deserve to make a living doing the thing they love best. I think we all deserve that. 
&lt;/ol&gt;

That's why we built PublicSquare, and the other products that will come on its heels such as the job board and the events calendar. Publishing is changing, and we'd like to help. 

</description>
      <pubDate>Fri, 07 Dec 2007 14:32:00 GMT</pubDate>
      <author>Christina Wodtke</author>
    </item>
    <item>
      <title>Big Release: Something for everyone</title>
      <link>http://blog.publicsquarehq.com/view/big-release</link>
      <guid>http://blog.publicsquarehq.com/view/big-release</guid>
      <description>&lt;p&gt;&lt;img src="/files/blog/big-release/crop-image-thumb.png" width="387" height="212" alt="crop image" align="right"/&gt;Hello true believers in independent publishing everywhere! We&amp;rsquo;ve got goodies for you this week!&lt;/p&gt;
&lt;p&gt;_We&amp;rsquo;ve added image manipulation._ &amp;nbsp;Wherever there are image links there are edit links now.&amp;nbsp; Take a test drive, and resize, reformat and play!

We do want to recommend though, that you create a copy *first* before you crop or resize. Those buttons apply immediately, so if you are a bit unsure about what you are doing, better to play with a copy (Christina found out the hard way!)

Also, when a file is uploaded, a caption can now be specified along with the keywords. &amp;nbsp;To see the caption used with a dropcap, the liquid template for a story will have to be modified. &amp;nbsp;In liquid, the story image tag is
&lt;pre&gt;
{{story.image.url}}&lt;/pre&gt;
&lt;p&gt;and  there is now a&lt;/p&gt;
&lt;pre&gt;
{{story.image.caption}}&lt;/pre&gt;
&lt;p&gt;tag available as well. 

    &lt;p&gt;Finally, we&amp;#8217;ve also changed the alt tag to show the caption rather than the keywords. However, if no caption is present, we&amp;#8217;ll still show the keywords so your old stories will continue to work the same. &lt;br  clear="all"/&gt;&lt;br  clear="all"/&gt;

&lt;h2&gt;We now let you autopublish!&lt;/h2&gt;&lt;img src="/files/blog/big-release/deadlines.png" width="" height="" alt="" align="right"/&gt; You notice now we&amp;rsquo;ve got two fields, one for internal deadlines (behaves the same way as the old deadline field but now also a &amp;ldquo;publish date&amp;rdquo; which will &lt;strong&gt;actually&lt;/strong&gt; publish your story with  or wihtout you! But don&amp;rsquo;t panic.. once you set that deadline, the story is marked publishable, just to warn you it&amp;rsquo;s on it&amp;rsquo;s way.&lt;br  clear="all"/&gt;&lt;br  clear="all"/&gt;


&lt;h2&gt; Never be seen without your makeup again!&lt;/h2&gt;
&lt;img width="284" height="216" src="/files/blog/big-release/staging-themes-thumb1.png" alt="How to stage a theme" align="right"/&gt;And another much-requested feature: template staging. Planning a makeover? Don&amp;rsquo;t want to get caught wearing your curlers? Well now you  can specify a theme to be &amp;ldquo;staged&amp;rdquo; that will show up as the  theme on your own personal staging site. &amp;nbsp;There is a link to the staging site available from the themes editing page (the &amp;ldquo;design&amp;rdquo; tab) on the theme designated as the staging site theme.   &lt;br /&gt;
&lt;/p&gt;

BTW, we've turned on the "forums" feature (another new and nifty feature, activated by clicking on "forums" under configuration) so you can tell us about bugs, issues, improvements and blow us kisses when we finally get it right....
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve got a few other little surprises planned&amp;hellip; Watch this space!&lt;/p&gt;</description>
      <pubDate>Wed, 30 Jan 2008 04:18:19 GMT</pubDate>
      <author>Christina Wodtke, Jim Meyer, Fleur Dragan</author>
      <category>Update!</category>
    </item>
    <item>
      <title>User Guide: Community Tools</title>
      <link>http://blog.publicsquarehq.com/about/user-guide-community</link>
      <guid>http://blog.publicsquarehq.com/about/user-guide-community</guid>
      <description>PublicSquare is based on the core concept that communities set their own standards, and it is the job of the software to hand communities the tools to manage their communities their own way. We believe in being yourself, and taking responsibility for your words. 

That said we also believe that Editorial is what keeps a publication from being a self-perpetuating suck-hole, and gets new ideas and concepts into the fray AS WELL AS cleaning up spelling and encouraging folks to have complete thoughts. Editors make better content. 

This means
* Everyone must log in to comment, rate or participate in any way
* Participants have a reputation that is affected by everything they do on the site.
* The community can rate comments, stories and ideas AND that affects the generator of their comment types reputation. 
* The community can flag any comment as offensive, and three flags means it disappears. BUT an editor/publisher (see PsRoles) can mark it as worth living on even if the community doesn't care for it.
* Sometimes the audience is smarter than the writer-- any comment can be nominated by a reader to the "Ideas":IdeasGuide slushpile. 
</description>
      <pubDate>Wed, 30 Jan 2008 15:22:18 GMT</pubDate>
      <author>Christina Wodtke</author>
    </item>
    <item>
      <title>User Guide: Ideas</title>
      <link>http://blog.publicsquarehq.com/about/user-guide-ideas</link>
      <guid>http://blog.publicsquarehq.com/about/user-guide-ideas</guid>
      <description>In traditional publishing, unsolicited manuscripts were often thrown out. Sometimes, they were set aside to pile up until the summer intern could go through them. In small webzines, they are often lost in email, misplaced in basecamp to-do lists, or thrown in a wiki (maybe...)

\PublicSquare provides a clean management system for all story idea submissions.  

A story is entered into the system on the public face of the publication. The story can them be voted for (requests) voted against (passes) and commented on. Why is this useful?
* see what ideas are interesting to your userbase
* see what ideas are controversial
* let your userbase tell you if the idea is plagiarized
* let your userbase help refine the idea! For example
** ask interview questions
** add more facts
** bring up the hard issues

When you evaluate an idea, we highly recommend you look at comments as well as rating... sometimes it pays to run a controversial article!

Length of idea submission is unlimited by default, if you want people to submit complete articles. </description>
      <pubDate>Wed, 30 Jan 2008 15:26:59 GMT</pubDate>
      <author>Christina Wodtke</author>
    </item>
    <item>
      <title>Keyboard Shortcuts for WYSIWYG</title>
      <link>http://blog.publicsquarehq.com/view/keyboard-shortcuts</link>
      <guid>http://blog.publicsquarehq.com/view/keyboard-shortcuts</guid>
      <description>&lt;p&gt;&amp;lt;img src=&amp;quot;/files/blog/keyboard-shortcuts/PS-WYSIWYG-2.png&amp;quot; width=&amp;quot;245&amp;quot; height=&amp;quot;215&amp;quot; alt=&amp;quot;WYSIWYG new functionality&amp;quot; title=&amp;quot;WYSIWYG new functionality&amp;quot; align=&amp;quot;right&amp;quot; /&amp;gt;You may have noticed &lt;span class="caps"&gt;WYSIWYG&lt;/span&gt; has gone on a diet and started working out&amp;hellip; and she's looking (and acting!) better than ever before. What you don't know is Jim, which exploring the depths of the FCKEditor documentation, found some awesome keyboard shortcuts for you! If you've never used them before, go ahead a play a bit. The secret is to hold these keys down together... or in order. So, for example, hold down the CTRL key (on window's machines, on Mac's it's usually the apple) and while holding it down, push the letter A. &lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Keyboard Shortcuts&lt;/h2&gt;
&lt;p&gt;&lt;br /&gt;
enter gets you a&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;
&lt;br /&gt;
shift-enter gets you a &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Accelerator keys:&lt;br /&gt;
&lt;br /&gt;
CTRL + A, select all&lt;br /&gt;
CTRL + C, copy&lt;br /&gt;
CTRL + F,&amp;nbsp; Launches find&lt;br /&gt;
CTRL + S, Saves (currently to disk, we're planning to return to it and get it to save to PS)&lt;br /&gt;
CTRL + X, Cut&lt;br /&gt;
CTRL + V, 'Paste' &lt;br /&gt;
SHIFT + INS, 'Paste' &lt;br /&gt;
CTRL + X, 'Cut' &lt;br /&gt;
SHIFT + DEL, 'Cut' &lt;br /&gt;
CTRL + Z, 'Undo' &lt;br /&gt;
CTRL + Y 'Redo' &lt;br /&gt;
CTRL + SHIFT + Z, 'Redo' &lt;br /&gt;
CTRL + L, 'Link' &lt;br /&gt;
CTRL + B, 'Bold' &lt;br /&gt;
CTRL + I, 'Italic' &lt;br /&gt;
CTRL + U, 'Underline' &lt;br /&gt;
CTRL + SHIFT + S, 'Save' &lt;br /&gt;
CTRL + ALT + ENTER, 'FitWindow' &lt;br /&gt;
CTRL + TAB, 'Source'&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;BTW, FitWindow is a feature we're very excited to discover. We know you've been begging for more room to edit! The only problem is we haven't figured out how to get out of full-screen mode. I'll keep you updated for when we do...&lt;/p&gt;</description>
      <pubDate>Wed, 27 Feb 2008 15:02:22 GMT</pubDate>
      <author>Christina Wodtke</author>
      <category>Tips and Tricks</category>
    </item>
    <item>
      <title>Anonymous Comments</title>
      <link>http://blog.publicsquarehq.com/view/anonymous-comments</link>
      <guid>http://blog.publicsquarehq.com/view/anonymous-comments</guid>
      <description>Due to popular request, we've added the ability for you to allow your visitors to comment without having to register. Just remember, without the enticement of building reputation (or the deterrent of losing it) you may see a drop in quality of comments as well as an increase of quantity. Please let us know your experience with anonymous comments!


How to turn them on:

If you're using one of our pre-packaged themes:
&lt;ol&gt;
&lt;li&gt;Dashboard &amp;rarr; Configuration &amp;rarr; Click the "Allow anonymous comments" checkbox&lt;/li&gt;
&lt;/ol&gt;

If you're using a custom theme, you've got a little more to do:
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Add conditional display of the anonymous poster info fields&lt;/strong&gt;: Find this in your _comment_form.liquid:
&lt;pre style="color: gray"&gt;&lt;code&gt;
{{ form.body }}
&lt;/code&gt;&lt;/pre&gt;
...and paste something like this above it:&lt;br/&gt;
&lt;pre style="color: green"&gt;
{% if comment.show_anonymous_poster_fields? %}
  &lt;span id="PosterName" class="AnonymousCommentLabel"&gt;Name 
&lt;small&gt;(required)&lt;/small&gt;&lt;/span&gt;
&lt;br/&gt;
  {{ form.poster_name }}&lt;br/&gt;
  &lt;span id="PosterEmail" class="AnonymousCommentLabel"&gt;Email 
&lt;small&gt;(required and never shared)&lt;/small&gt;&lt;/span&gt;&lt;br/&gt;
  {{ form.poster_email }}&lt;br/&gt;
  &lt;span id="PosterURL" class="AnonymousCommentLabel"&gt;Website 
&lt;small&gt;(optional)&lt;/small&gt;&lt;/span&gt;
&lt;br/&gt;
  {{ form.poster_url }}&lt;br/&gt;&lt;br/&gt;
{% endif %}
&lt;/pre&gt;&lt;pre style="color: gray"&gt;
{{ form.body }}
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Only show voting controls on signed comments&lt;/strong&gt;: 
Because anonymous users can not (and should not) gain reputation, you 
don't want to show the voting controls. You'll find something like this either 
in your _feedback.liquid or _comment.liquid:
&lt;pre style="color: gray"&gt;&lt;code&gt;
&lt;div class="CommentVotingArea"&gt;
[...]
&lt;/div&gt;
&lt;span id="{{ id.flagging }}" class="CommentFlag"&gt;
or &lt;a href="#" onclick="{{ action.flag }}" 
title="Alert the staff that this entry is inappropriate"&gt;
Flag as Offensive/Spam&lt;/a&gt;
&lt;/span&gt;
[...]
{% if on.poster %}
  &amp;middot;         
  &lt;a href="#" title="Delete this entry and ban this person from posting again" 
class="AdminToolbarLink" onclick="{{ action.ban }}"&gt;Ban&lt;/a&gt;
{% endif %}
&lt;/code&gt;&lt;/pre&gt;
... and make it look like this:&lt;br/&gt;
&lt;pre style="color: green"&gt;
{% unless on.anonymous_poster? %}
&lt;/pre&gt;&lt;pre style="color: gray"&gt;&lt;div class="CommentVotingArea"&gt;
[...]
&lt;/div&gt;
&lt;/pre&gt;&lt;pre style="color: green"&gt;{% endunless %}
&lt;/pre&gt;&lt;pre style="color: gray"&gt;&lt;span id="{{ id.flagging }}" class="CommentFlag"&gt;
&lt;/pre&gt;&lt;pre style="color: green"&gt;{% unless on.anonymous_poster? %}&lt;/pre&gt;
&lt;pre style="color: gray"&gt;or &lt;/pre&gt;&lt;pre style="color: green"&gt;{% endunless %}
&lt;/pre&gt;&lt;pre style="color: gray"&gt;&lt;a href="#" onclick="{{ action.flag }}" 
title="Alert the staff that this entry is inappropriate"&gt;Flag as Offensive/Spam&lt;/a&gt;
&lt;/span&gt;
[...]
&lt;/pre&gt;&lt;pre style="color: green"&gt;{% unless on.anonymous_poster? %}
&lt;/pre&gt;&lt;pre style="color: gray"&gt;  &amp;middot;         
  &lt;a href="#" title="Delete this entry and ban this person
from posting again" class="AdminToolbarLink" onclick="{{ action.ban }}"&gt;
Ban&lt;/a&gt;
&lt;/pre&gt;&lt;pre style="color: green"&gt;{% endunless %}
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Show your comment form when it's okay to comment&lt;/strong&gt;: 
Find this in your story.liquid:
&lt;pre style="color: gray"&gt;
&lt;p&gt;&lt;a class="actionmessage" href="{{ current_site.log_in_and_return_url }}
{{ '#post_comment' | urlencode }}"&gt;Register or log in to comment&lt;/a&gt;&lt;/p&gt;
&lt;/pre&gt;
...and replace it with:
&lt;pre style="color: green"&gt;
{% if story.show_comment_form? %}
  {% include 'comment_form' %}
{% else %}
&lt;/pre&gt;&lt;pre style="color: gray"&gt;  &lt;p&gt;&lt;a class="actionmessage" 
href="{{ current_site.log_in_and_return_url }}{{ '#post_comment' | urlencode }}"&gt;
Register or log in to comment&lt;/a&gt;&lt;/p&gt;
&lt;/pre&gt;&lt;pre style="color: green"&gt;{% endif %}
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stylize the new bits&lt;/strong&gt;: Add these styles to your screen.css:
&lt;pre style="color: green"&gt;&lt;code&gt;
.AnonymousCommentLabel {
  font-style: italic;
}

.comment_poster_name {
  width: 255px;	
}

.comment_poster_email {
  width: 255px;	
}

.comment_poster_url {
  width: 255px;	
}

.comment_body {
  width: 510px;	
}

.comments {
	font-weight: bold;
	padding-bottom: 2em !important;
}

.CommentInputErrorMsg {
  font-size: 1.1em;
  color: #c00;
  font-weight: bold;
  margin-bottom: 1em;
}
&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;/ol&gt;

</description>
      <pubDate>Sat, 11 Oct 2008 22:48:55 GMT</pubDate>
      <author>Christina Wodtke, Jim Meyer</author>
    </item>
  </channel>
</rss>

