<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog Mum &#187; NPG2WP</title>
	<atom:link href="http://blogmum.com/category/wordpress/npg2wp/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogmum.com</link>
	<description>WordPress made easy</description>
	<lastBuildDate>Mon, 05 Apr 2010 00:20:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WordPress Comments</title>
		<link>http://blogmum.com/2009/05/wordpress-comments/</link>
		<comments>http://blogmum.com/2009/05/wordpress-comments/#comments</comments>
		<pubDate>Mon, 18 May 2009 12:34:09 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=619</guid>
		<description><![CDATA[<p>I think more blog inches have been expended discussing commenting than any other aspect of blogging - and perhaps rightly so. Commenting was, when it first started, revolutionary: it turned the internet from a broadcast medium into something so much richer. I don't think it's overstating the case to say that existence of the Web 2.0, post-Cluetrain internet-as-conversation many of us take for... <a href="http://blogmum.com/2009/05/wordpress-comments/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<p>I think more blog inches have been expended discussing commenting than any other aspect of blogging - and perhaps rightly so. Commenting was, when it first started, revolutionary: it turned the internet from a broadcast medium into something so much richer. I don't think it's overstating the case to say that existence of the Web 2.0, post-Cluetrain internet-as-conversation many of us take for granted now, can be laid at the door of blog commenting (unless we blame Pierre Omidyar and eBay feedback for it instead). </p>
<p>And with success, comes trouble. In the case of blogs, that's comment spam. I recently went back to a blog which I'd left for a year to find more than 50,000 spam comments awaiting my approval, advertising everything from - well, there was nothing I really wanted to buy <img src='http://blogmum.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  Dealing with blog comments is a battle - between blogger and spammer, and between spammer (who needs to be inconvenienced) and legitimate commenter, who doesn't. And it's managing that second battle that can cause many difficult decisions for bloggers on the best way to set up their blog. </p>
<p>Let's look first at what you can do, and then we'll consider why you might want to do it. </p>
<p>Comments settings are accessible from the WordPress dashboard under Settings &gt; Discussion.
<ul>
<li>The first two options relate to <a href="http://blogmum.com/2008/12/whats-a-pingback/">pingbacks</a>. </li>
<li><strong>Allow people to post comments on the article </strong> is the master switch: if this is not checked, then by default, commenting will be switched off for all posts on your blog. You could, however, choose to switch it on again for individual posts under "Discussion" on the Add New Post page. </li>
<li><strong>Comment author must fill out name and e-mail </strong> only relates to filling out the form, not to verification of the information: there is no checking that the email address is a valid one. </li>
<li><strong>Users must be registered and logged in to comment </strong>will force users to register before they can comment. If you don't have "anyone can register" set in Users settings, then this will effectively stop commenting for anyone but the blog author(s). (This is a pretty common cause of "lots of traffic but no comments" syndrome!) </li>
<li><strong>Automatically close comments on articles older than xx days</strong>: most spam is on older posts, so closing comments after real discussion is finished is a good way to knock out lots of spam. Change the default "14" days if discussions on your own blog go on longer than this: most don't. </li>
<li><strong>Enable threaded (nested) comments</strong> lets commenters reply to previous commenters, rather than just to the bottom of a long comment thread. </li>
<li><strong>Break comments into pages...</strong> can speed up page loading on posts with hundreds of comments (it's not worth worrying about if you get fewer than hundreds). </li>
<li><strong>Comments should be displayed with the older/newer comments at the top of each page</strong>: the convention is to show oldest comments at the top; you should stick with that unless you have a very good reason not to. </li>
<li><strong>Email me whenever...</strong>: you might not want an email every time anyone posts a comment, but you should get one each time a comment is held for moderation, i.e. a blog admin needs to manually approve its publication. It's only polite to moderate comments reasonably promptly. </li>
<h3>Moderation section</h3>
<li>Checking <strong>An administrator must always approve the comment </strong>means that you will manually have to approve every comment that appears on your blog. </li>
<li>Checking <strong>Comment author must have a previously approved comment</strong> means that you'll need to approve each commenter's first comment, but after that, they'll be published automatically. The check is done against emails, so if you have commenters who use a range of different email addresses, approval would need to be done for each of them. </li>
<li><strong>Hold a comment in the queue if it contains xx or more links. </strong> Spammers commonly post a list of dozens of links.  </li>
<li><strong>Comment moderation</strong> and <strong>comment blacklist </strong>lists allow you to set your own lists of words that will throw comments into moderation or be marked as spam. Useful to filter out your own least-favourite profanities or pharmaceuticals. </li>
<li>We'll come to <strong>avatars</strong> in another post, but this is where you set up the options for "little pictures in comments". </li>
</ul>
<p>So given all these options, which do you set? Two general principles about blog comments:
<ol>
<li><a href="http://blogmum.com/2008/11/3-plugins-to-stop-comment-spam/">Let plugins do the donkey work for getting rid of spam.</a> It should be the odd spam comment that slips through to your comment settings to deal with. </li>
<li>It's your blog; do what works for your content and your readers, do what makes you happy. You can always change settings if you change your mind. </li>
</ol>
<div class="alignright photodiv"><a href="http://www.flickr.com/photos/8070463@N03/2531409306/" title="Angry kitty" target="_blank"><img src="http://farm3.static.flickr.com/2284/2531409306_877bdcf1df_m.jpg" alt="Angry kitty" border="0" /></a><br /><small><a href="http://creativecommons.org/licenses/by-nd/2.0/" title="Attribution-NoDerivs License" target="_blank"><img src="http://blogmum.com/wp-content/plugins/photo-dropper/images/cc.png" alt="Creative Commons License" border="0" width="16" height="16" align="absmiddle" /></a> <a href="http://www.photodropper.com/photos/" target="_blank">photo</a> credit: <a href="http://www.flickr.com/photos/8070463@N03/2531409306/" title="Tambako the Jaguar" target="_blank">Tambako the Jaguar</a></small></div>
<h3>You'll get the comments your blog invites </h3>
<p>The thought of letting people write what they like on your website can be a daunting one, but in practice, once you've shut the spammers out, you'll mostly get the comments your blog invites. If you write snarky, ascerbic posts about religion or politics, you'll get snarky, ascerbic commenters - some of whom will agree with you, and some of whom won't. If you post <a href="http://icanhascheezburger.com/">pictures of kittens</a>, you'll probably get less snark, tho ur komentz miyt reed liyk dis. If you have a business blog, you might be worried that disgruntled customers will take out their frustrations in your blog comments; if this is the case, you should probably revise your customer service processes. And most people, basically, are good: instances of real nastiness in blog comments are thankfully rare.</p>
<h3>If you want comments, make commenting easy </h3>
<p>If you don't want comments, then turn them off. It's your blog. But you'll have a better time blogging if you do allow comments: conversation, feedback, discussion, argument and even the odd insult make blogging more interesting for you, and reading your blog more interesting for your readers. If you're only posting, you're preaching to the wind: is anyone listening? does anyone agree, disagree, even care? how will you know? </p>
<p>Commenting should be easy for your commenters. Don't seek to moderate dissent by putting hurdles in the way of dissenters: all you'll do is put off the moderate people, and ensure that only the most rabidly furious make it through to your blog. Requiring registration will put most people off: don't do it. </p>
<p>But do require name and email address. Though WordPress doesn't check the validity of the email address, most people do give you a real one, and I think that slight lack of  anonymity does act to curb the worst excesses of keyboard-warrior behaviour. </p>
<p>Increase the number of allowed links above the default 2. Spammers who post lists of links post dozens, but many innocent commenters include a couple of links in a well-considered comment. Give those people a break. </p>
<p>If you want conversation on your blog, turn off admin approval. One of the nicest things that happens on any blog is when commenters start talking to each other; that's the point at which it's turned into a conversation. Having admin approve every comment stifles that, because conversations only really happen in real time. At the very least, turn on "commenter must have previously approved comment" so that you only need to approve the person: telling your regular commenters that you *still* don't approve them and *still* need to check everything they say before you publish it, tells them that you don't trust them. Worse still, if you can't moderate comments quickly, it sends out messages like their opinion isn't important, or (in the extreme) that you're censoring them.</p>
<div class="alignleft photodiv"><a href="http://www.flickr.com/photos/47148215@N00/197155071/" title="July 24 - See No / Hear No / Speak No Evil" target="_blank"><img src="http://farm1.static.flickr.com/66/197155071_f24e96ee48_m.jpg" alt="July 24 - See No / Hear No / Speak No Evil" border="0" /></a><br /><small><a href="http://creativecommons.org/licenses/by-nd/2.0/" title="Attribution-NoDerivs License" target="_blank"><img src="http://blogmum.com/wp-content/plugins/photo-dropper/images/cc.png" alt="Creative Commons License" border="0" width="16" height="16" align="absmiddle" /></a> <a href="http://www.photodropper.com/photos/" target="_blank">photo</a> credit: <a href="http://www.flickr.com/photos/47148215@N00/197155071/" title="Rob Gallop" target="_blank">Rob Gallop</a></small></div>
<p>This isn't to say that you have to publish everything. Use the moderation list in a way that's meaningful for your content. A comments policy can also help your readers to know beforehand what's acceptable; it can also help you if you decide not to publish a comment, to have a pre-existing document to point to, explaining exactly why something's not allowed. (At very least, you should probably decide, and state, what level of sweariness you'll permit.)</p>
<p>Be careful with the blacklist filter. This matches partial words, so - as the form says - "press" will match "WordPress". Potentially this can turn it into a <a href="http://en.wikipedia.org/wiki/Scunthorpe_Problem">Scunthorpe filter</a>, so add words sparingly and as needed.<br />
<br clear="all" /></p>
<h3>It's okay to delete comments </h3>
<p>I suffered over this one, but the conclusion I have come to is this: I believe that people have the right to free speech, and that means they have the right to their own blog. It does not mean they have the right to say what they like in my comments, particularly when they want to promote their own agenda in a way that makes things unpleasant for me and the rest of my readers. To put it rather more graphically, that everyone has the right to crap, doesn't mean they have the right to crap on my living room carpet. Remember: it's your blog. </p>
<h3>"Unapprove" </h3>
<p>Deleting is permanent, so throwing something into moderation so it's not visible on the published blog can be a way to give yourself time to calm down, think rationally, even take advice before you make the decision to let it stand, or remove it. From the admin section for Comments, you can "unapprove" individual comments, and they will be held awaiting your later approval. </p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=619&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2009/05/wordpress-comments/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>WordPress RSS Feeds</title>
		<link>http://blogmum.com/2009/05/wordpress-rss-feeds/</link>
		<comments>http://blogmum.com/2009/05/wordpress-rss-feeds/#comments</comments>
		<pubDate>Sat, 02 May 2009 01:08:27 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[advertising]]></category>
		<category><![CDATA[Atom]]></category>
		<category><![CDATA[Feedburner]]></category>
		<category><![CDATA[feeds]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[permalinks]]></category>
		<category><![CDATA[RSS]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=346</guid>
		<description><![CDATA[<p>What's a feed and why would I want one? A feed is, simply, another way for people to read your blog posts that doesn't require them to actually visit your site to do so. If you read a lot of blogs and news sites, clicking through to all of the websites to see if there's anything new can get tedious. Feeds allow your readers to "subscribe" to your blog: that is, add your feed to a feed reader -... <a href="http://blogmum.com/2009/05/wordpress-rss-feeds/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<h3>What's a feed and why would I want one? </h3>
<p><img style="border: 0px;" src="http://blogmum.com/wp-content/uploads/2009/05/f-tiagopinhal.jpg" alt="RSS feed button" title="RSS feed button" width="114" height="150" class="alignleft size-full wp-image-384" />A feed is, simply, another way for people to read  your blog posts that doesn't require them to actually visit your site to do so. If you read a lot of blogs and news sites, clicking through to all of the websites to see if there's anything new can get tedious. Feeds allow your readers to "subscribe" to your blog: that is, add your <a href="http://en.wikipedia.org/wiki/Web_feed">feed</a> to a <a href="http://en.wikipedia.org/wiki/List_of_feed_aggregators">feed reader</a> - software that will automatically notify them when you've published a new post, and allow them to read it without even having to click to visit your site. </p>
<p><a href="http://www.whatisrss.com/">What Is RSS.com</a> explains more about how this works. </p>
<h4>But I want people to visit my site! </h4>
<p>When you publish your RSS feed, you have the choice to show whole posts, or just a teaser: a shortened version of the whole thing. The setting can be changed for WordPress in Settings &gt; Reading. </p>
<p>There's been <a href="http://labnol.blogspot.com/2006/12/do-you-publish-full-text-feeds-or.html">a lot of</a> <a href="http://www.problogger.net/archives/2007/09/12/full-or-partial-rss-feeds-the-great-feed-debate/">debate</a> in recent years about whether it's better to publish full or partial feeds. People who argue for partial feeds say that they'd rather have people come to their site to read their posts (and click their advertising while they're there): a feed is, for them, a notification system that says "come to my site, there's something new", rather than handing over the content to be read whenever their readers choose. They also say that full feeds make it easy for other people to steal their words and republish them on spam blogs. </p>
<p>I say that both of these arguments are trumped by the fact that <em>partial feeds are really annoying</em>. *You* might prefer me to come look at your advertising; *I* prefer to read your posts in my feedreader at my convenience. And that way, I'm actually more likely to read what you've said; if I have to click to read more, the first part of your post had better be a really compelling bit of writing, otherwise I'm just going to move onto the next blog. </p>
<p>If you want advertising, there are plenty of ways to advertise on your RSS feed - Google has <a href="https://www.google.com/adsense/support/bin/answer.py?hl=en&#038;answer=20012">Adsense for Feeds</a>, and there are <a href="http://www.blogclout.com/blog/goodies/feed-footer-plugin/">WordPress plugins to add banner ads to your feeds</a> too. </p>
<p>If you're undecided whether you want to offer full or partial feeds, you can always offer both: the <a href="http://www.scratch99.com/wordpress-plugin-dualfeeds/">Dual Feeds plugin</a> will automate this. On TameBay we publish a full feed with "all rights reserved" - just for personal reading use - and a partial feed with a <a href="http://creativecommons.org/">Creative Commons licence</a> that anyone can republish, because they'll be linking back to us. </p>
<p>[This issue of blog content theft is a much bigger one than this post has room for. I'll be revisiting it at a later date, but if you're having problems with people taking your words as their own, I'd recommend a visit to the excellent <a href="http://www.plagiarismtoday.com/">Plagiarism Today</a>.]</p>
<h3>Default feeds and where to find them </h3>
<p>The orange logo above has become the <a href="http://www.feedicons.com/">standard for feeds</a>. Most themes will include some variant of it as a link to your feed, allowing your readers to find it and subscribe easily. If that's not the case, don't panic: WordPress automatically generates feeds for you, so all you have to do is link them. </p>
<p>If you've set up <a href="http://blogmum.com/2009/04/wordpress-permalinks/">pretty permalinks</a> for your blog, the main feed for your posts will be at<br />
<code>http://domain.com/feed/</code> </p>
<p>If for some reason you haven't or can't set up pretty permalinks, then you can provide your readers with direct links to one of several flavours of feeds WordPress generates: RSS2 is the WP default, and either of its possible URLs should work fine in any up-to-date feedreader:</p>
<p><code>http://domain.com/wp-rss2.php</p>
<p>http://domain.com/?feed=rss2</code></p>
<p>If you <a href="http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared">prefer Atom 1.0</a>, then go for one of </p>
<p><code>http://domain.com/wp-atom.php</p>
<p>http://domain.com/?feed=atom</code></p>
<p>You can generate these automatically with the following PHP code (especially useful if your domain name might change or you're making a theme for publishing):</p>
<p><code>&lt;?php bloginfo('rss2_url'); ?&gt;<br />
&lt;?php bloginfo('atom_url'); ?&gt;</code></p>
<h3>Who's reading my feed?</h3>
<p>One of the problems in the early days of RSS (and one big argument used by proponants of partial feeds) was that it was difficult to tell just how many people were reading your feed. That's changed, thanks to a lovely company called <a href="http://www.google.com/support/feedburner/">Feedburner</a>, which is now owned by Google. </p>
<p>Feedburner allows you to redirect your feed through their servers, where number of subscribers and all sorts of other data can be monitored. They also reproduce your feed as an email subscription option for readers who'd rather have your blog emailed to them. The service is free, and absolutely invaluable. </p>
<p>To get started, install the <a href="http://www.google.com/support/feedburner/bin/answer.py?hl=en&#038;answer=78483">Feedburner Feedsmith</a> plugin (can be downloaded from Google and uploaded via FTP, or just installed automatically through the WordPress plugins admin section). </p>
<p><strong>Coming tomorrow</strong>: posts are not the only feed. WordPress offers many more feeds, from comments to individual tags, categories and authors. If you're not already, why not <a href="http://blogmum.com/feed/">subscribe to my feed</a> ready for the next post. </p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=346&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2009/05/wordpress-rss-feeds/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>WordPress Users</title>
		<link>http://blogmum.com/2009/04/npg2-wordpress-users/</link>
		<comments>http://blogmum.com/2009/04/npg2-wordpress-users/#comments</comments>
		<pubDate>Sun, 19 Apr 2009 15:31:27 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[administrator]]></category>
		<category><![CDATA[author]]></category>
		<category><![CDATA[change password]]></category>
		<category><![CDATA[contributor]]></category>
		<category><![CDATA[editor]]></category>
		<category><![CDATA[subscriber]]></category>
		<category><![CDATA[user level]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=325</guid>
		<description><![CDATA[<p>Today I want to take a quick look at WordPress users: how to change how your name appears next to your posts, and how to add new users to your blog (and make sure they can't do anything you don't want them to). If you've got a brand new install of WordPress, you've probably just got one user, and that user is probably called something like "admin". Which is all very well for signing into the... <a href="http://blogmum.com/2009/04/npg2-wordpress-users/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<p>Today I want to take a quick look at WordPress users: how to change how your name appears next to your posts, and how to add new users to your blog (and make sure they can't do anything you don't want them to). </p>
<p>If you've got a brand new install of WordPress, you've probably just got one user, and that user is probably called something like "admin". Which is all very well for signing into the WordPress admin section, but probably not the name you want next to your posts. </p>
<h3>Editing your profile</h3>
<p>Click on the "Users" tab from the Dashboard and you'll see a list of all the users currently registered on your blog. To change profile info, click on the relevent user name. You can change and add a lot of information on this next screen: most of it isn't necessary because it doesn't show up in most themes (but see below if you want it to). <img src="http://blogmum.com/wp-content/uploads/2009/04/wpusername.png" alt="wpusername" title="wpusername" class="aligncenter size-medium wp-image-329" /><br />
Options that you will probably want to fill out are the real name and nickname fields; these are what WordPress uses to determine the name that it gives for the author of your posts. It'll make some suggestions in the drop-down box next to "Display name publicly as", but if you don't like any of those,
<ul>
<li>add the display name you want to the nickname field, </li>
<li>click the "update profile" button</li>
<li>then select the new nickname from the drop-down list</li>
<li>and update your profile again. </li>
</ul>
<h3>Changing your password </h3>
<p>Scroll to the bottom of your user profile, and the form to change your password is there. Though it's tempting to abandon the hideously random one WP auto-generates, do pick something reasonably secure <img src='http://blogmum.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  </p>
<h3>Changing your avatar</h3>
<p>The "avatar" is the little picture which shows up beside your name in the users' list, and also beside your comments in most new-ish WP themes. If you have the shadowy person-shape, or worse still the blue Gravatar logo, go to <a href="http://gravatar.com/">Gravatar.com</a> and sign up for an account. </p>
<p>If you want to change your picture, again that needs to be done through Gravatar not through the WordPress dashboard. And if you want multiple pictures to use depending on where you're writing, you can also do that through Gravatar. </p>
<h3>Adding the author's information to the post</h3>
<p>Not all themes include the author's name next to the post. Some people think that if there's only one author, it's pretty pointless having their name on all their posts. I disagree: I'd like to be top of Google for my own name, and having it on every blog post I write will help that. And of course, if you have a multi-author blog, you probably want to have each writer's name by their posts. </p>
<p>If your theme's missing this information, it's easy to add in: <code>Post written by &lt;?php the_author(); ?&gt; </code> will add the "display name publicly" field to your blog, and there are <a href="http://codex.wordpress.org/Template_Tags/the_author#Related">several other tags</a> to show the author's first or last name, email, URL, description, etc. etc. If you have a lot of guest posters, you can use this information to - for example - display a short bio at the end of the post. </p>
<h3>Adding more users</h3>
<p>Click on Users &gt; Add New to add a new user (yes, it's that simple <img src='http://blogmum.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  ). You'll have to fill out the username, email address and password; WordPress will then email details of the registration to your new author. You'll also need to select what role you want the new user to have; which you pick will depend on how much freedom you want them to have on the blog.
<ul>
<li><strong>Administrators</strong> can do anything, including adding and removing plugins and themes, and removing other users. </li>
<li><strong>Editors</strong> can publish and edit all posts*, but cannot change the appearance or functionality of the blog. </li>
<li><strong>Authors</strong> can publish and edit their own posts, but no one else's. </li>
<li><strong>Contributors</strong> can write and edit their own posts, but not publish them.</li>
<li><strong>Subscribers</strong> can only leave comments  </li>
</ul>
<p>If you want your new user to be able to publish their own posts without your approval, you might make them an Author; if you'd prefer to check over what they've written first, make them a Contributor. It's easy to alter a user's access level (just change it from Dashboard &gt; Users), so I would recommend choosing a lower level and increasing it if necessary; making everyone an Administrator is potentially asking for trouble. </p>
<p>* WordPress 2.7.1 doesn't allow Editors to edit Administrators' posts. It's not quite clear at the moment if this is deliberate or a bug; I guess we'll find out when 2.8 is released later this month! </p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=325&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2009/04/npg2-wordpress-users/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>WordPress Permalinks</title>
		<link>http://blogmum.com/2009/04/wordpress-permalinks/</link>
		<comments>http://blogmum.com/2009/04/wordpress-permalinks/#comments</comments>
		<pubDate>Fri, 03 Apr 2009 10:48:27 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[permalinks]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=66</guid>
		<description><![CDATA[<p>Perma- what now? For every post you write, WordPress generates one single page just with that post on it. The URL of that page is commonly known as its "permalink"; it's short for permanent link, the link where that post will always be found, even when it's moved off your blog's front page. By default, WordPress permalinks look like this: http://blogmum.com/?p=16 This is both bad and... <a href="http://blogmum.com/2009/04/wordpress-permalinks/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<h3>Perma- what now? </h3>
<p>For every post you write, WordPress generates one single page just with that post on it. The URL of that page is commonly known as its "permalink"; it's short for permanent link, the link where that post will always be found, even when it's moved off your blog's front page. </p>
<p>By default, WordPress permalinks look like this:<br />
<code>http://blogmum.com/?p=16</code><br />
This is both bad and ugly: bad, because the "?" tells search engines that this is a dynamically generated page, potentially with unstable content, and ugly because - well, read it. It tells neither your human readers nor Google anything about what's on the page it links to. </p>
<p>It's much better to use meaningful permalinks like this:<code></p>
<p>http://blogmum.com/2008/11/keep-your-wordpress-blog-secure/</code></p>
<p>Not only can anyone looking at your URL immediately get an idea of what your post will be about, but search engines can see it too, which will increase your chances of being found for the keywords in your title (you *are* thinking about Google when you write your post titles, aren't you?).</p>
<h3>How to make pretty permalinks</h3>
<p>Fortunately, there is a fairly easy cure for this. In WP Admin, Settings > Permalinks allows you to set up human-readable permalinks in the style of your choice. <a href="http://codex.wordpress.org/Using_Permalinks">WordPress gives you a range of elements</a> you can include in your link:</p>
<ul>
<li>Timestamp elements: year, month, date, hour, minutes and seconds
<li>Post title and post number
<li>Category and author of the post </ul>
<p>Several of these are pre-set in the dashboard and can be selected by clicking the radio buttons; if you want to create your own style, <a href="http://codex.wordpress.org/Using_Permalinks#Choosing_your_permalink_structure">choose the appropriate tags</a> and type them into the "custom structure" box. </p>
<h3>Which elements should you include? </h3>
<ul>
<li>Always include the post name; these words are a huge boost to your SEO.
<li>
Each permalink should <strong>begin</strong> with numeric data (year, or post number) rather than text: beginning permalinks with textual data can cause <a href="http://comox.textdrive.com/pipermail/wp-testers/2009-January/011097.html">performance problems</a>.
<li>Each permalink should <strong>end </strong>with the post name (or the post number) so that a unique URL is generated.
<li>If you've imported a lot of blog posts from another blogging system (e.g. Blogger), then mirroring the existing permalink style ensures that links to your old posts stay valid in WordPress.
<li>Year, month and perhaps date can help human readers to see when they're looking at an old post.
<li>Adding some numerical data (dates or post numbers) <a href="http://codex.wordpress.org/Using_Permalinks#Using_only_.25postname.25">is advisable</a> to prevent conflicts with other parts of your WP install.
<li>Hours, minutes and seconds are probably unnecessary (if they seem necessary, maybe you should post a bit less often...).
<li>If your blog has multiple authors, adding the author field to the permalink is an option. </ul>
<p>Personally, I like <strong>year/month/post title</strong>: it's short enough, but meaningful to both human readers and search engines. </p>
<h3>Need a shorter URL? </h3>
<p>The cool thing about WordPress's behaviour here is that the old, ugly URL will still work: it just redirects to your new, sexy URL. So if you've got year and month and date and a long post title, and the resulting very long URL is going to break in emails or be too long for Twitter, you can still use the domain/?p=post_number one, and anyone using it will be redirected to your pretty link automatically. </p>
<p>If you need to find the post number, go into Manage Posts and hover over the post title: the last number of the URL in your browser status bar is the post number. </p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=66&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2009/04/wordpress-permalinks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Custom Fields</title>
		<link>http://blogmum.com/2009/03/the-normal-persons-guide-to-wordpress-custom-fields/</link>
		<comments>http://blogmum.com/2009/03/the-normal-persons-guide-to-wordpress-custom-fields/#comments</comments>
		<pubDate>Tue, 03 Mar 2009 11:08:51 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[custom fields]]></category>
		<category><![CDATA[NPGtWP]]></category>
		<category><![CDATA[Skribit]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=186</guid>
		<description><![CDATA[<p>What is a custom field? A custom field is simply a way to add the same type of information to some or all of your WP posts. Just as all posts can currently have a title, category and tags, as well as content, you might choose to add custom fields to show your mood, the music you're listening to, the deal of the week on your ecommerce website or the filename of a thumbnail picture you want to... <a href="http://blogmum.com/2009/03/the-normal-persons-guide-to-wordpress-custom-fields/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<h3>What is a custom field? </h3>
<p>A custom field is simply a way to add the same type of information to some or all of your WP posts. Just as all posts can currently have a title, category and tags, as well as content, you might choose to add custom fields to show your mood, the music you're listening to, the deal of the week on your ecommerce website or the filename of a thumbnail picture you want to display with your post.</p>
<p>Many plugins also utilise custom fields: for example, if you're running the <a href="http://wordpress.org/extend/plugins/sociable/">Sociable</a> plugin to allow your readers to share your posts via social media, you'll see "sociableoff" as an custom fields option - unsurprisingly, it allows you to switch off Sociable for individual posts.</p>
<h3>How to set custom fields</h3>
<p>Let's take a simple example: I want to add my mood to each post. The Custom Fields section is towards the bottom of the Add New Post page. </p>
<p>To add a new custom field, put the field key, e.g. "mood", in the "name" box, and the value, e.g. "cheerful", in the "value" box. Click the "add custom field" to save. <br clear="all"><br />
<div id="attachment_191" class="wp-caption alignleft" style="width: 310px"><a href="http://blogmum.com/wp-content/uploads/2009/03/customfields1.jpg"><img src="http://blogmum.com/wp-content/uploads/2009/03/customfields1-300x111.jpg" alt="Adding a new custom field" title="Adding a new custom field" width="300" height="111" class="alignleft" /></a><p class="wp-caption-text">Adding a new custom field</p></div><br clear="all"></p>
<p>If you've previously set a custom field, the name will appear in a drop-down list in the Custom Fields section. So for your next post, "moods" will already be available, and you can just add your new mood to the value box. <br clear="all"><br />
<div id="attachment_192" class="wp-caption alignleft" style="width: 310px"><a href="http://blogmum.com/wp-content/uploads/2009/03/customfields2.jpg"><img src="http://blogmum.com/wp-content/uploads/2009/03/customfields2-300x110.jpg" alt="Using an existing custom field in a new post" title="Using an existing custom field in a new post" width="300" height="110" class="alignleft" /></a><p class="wp-caption-text">Using an existing custom field in a new post</p></div><br />
<br clear="all"></p>
<h3>How to show custom fields in your posts</h3>
<p>Here's the simplest way to get a custom field to show in your posts. Just add this code to your theme where you want the custom field information to show:<br />
<code><br />
&lt;?php $my_custom_field = get_post_meta($post->ID, &#34;mood&#34;, true);<br />
echo 	&#34;&lt;p&gt;Mood: 	&#34;.$my_custom_field.&#34;&lt;/p&gt;&#34;; ?&gt;</code></p>
<p>"mood" in the first line within the double quotes should be the name of the custom field you want to show (but make sure you preserve the quotes). </p>
<p><a href="http://codex.wordpress.org/Using_Custom_Fields">Find out more about using custom fields from the WordPress Codex.</a></p>
<p><em><br />
This question came via the Skribit widget in my sidebar: if there's a question you'd like answered, please post it! </em></p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=186&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2009/03/the-normal-persons-guide-to-wordpress-custom-fields/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>WordPress Plugins</title>
		<link>http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-plugins/</link>
		<comments>http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-plugins/#comments</comments>
		<pubDate>Tue, 18 Nov 2008 15:30:07 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=7</guid>
		<description><![CDATA[<p>We've looked at how to install WordPress and how to make it pretty; today I want to look at making WP do more. Plugins are additions to the basic WordPress functionality, which allow you make it do just about anything you can imagine, from adding polls to your posts to controlling banner ads. Find them in the official WordPress plugin directory. Like themes, they're extremely easy to add to... <a href="http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-plugins/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<p>We've looked at <a href="">how to install WordPress</a> and <a href="">how to make it pretty</a>; today I want to look at making WP <em>do more</em>. </p>
<p>Plugins are additions to the basic WordPress functionality, which allow you make it do just about anything you can imagine, from <a href="http://lesterchan.net/portfolio/programming/php/#wp-polls">adding polls to your posts</a> to <a href="http://www.irisco.it/?page_id=40">controlling banner ads</a>. Find them in the official <a href="http://wordpress.org/extend/plugins/">WordPress plugin directory.</a> Like themes, they're extremely easy to add to your WP install. </p>
<h2>The least you need to know</h2>
<ul>
<li>Download and unzip your chosen plugin
<li>Upload the plugin folder or single .php file to /wp-content/plugins/
<li>From your dashboard, click on 'plugins', and 'activate' your chosen plugins.
<li>Find where the plugin management is hiding, and make any customisations you need. </ul>
<h2>Managing and updating plugins </h2>
<p>Most plugins will come with some kind of customisability or options that you can change to suit your particular requirements. The link to manage these options might appear under "manage" on your dashboard, or under "settings". A few show up on the top of the plugin management page. Some even add their own top-level link to your dashboard. I think WordPress might do well to add a "plugin management" tab and have all plugins work from there, because as it stands, it can be rather confusing. Don't be afraid to do a little searching about if your plugin management page doesn't appear where you're expecting first-off. </p>
<p><img src="http://www.tamebay.com/wp-content/uploads/2008/09/pluginbubble.png" alt="wordpress plugin update reminder" title="pluginbubble" class="alignleft size-full wp-image-4082" />Like the core WordPress install, plugins change: new features are added, security is updated, incompatibilities are ironed out. WP will tell you when one of your plugins needs to be updated: just watch out for the bubble on your dashboard. Most plugins can be automatically updated from within WordPress: there's no messing about with FTP here.</p>
<h2>If it all goes wrong...</h2>
<p>... don't panic. Sometimes some plugins conflict with others you already have installed; even more rarely, they're released prematurely and don't work correctly. Normally, you can just go to Plugins on the dashboard and disable the guilty party. If you can't get access to your dashboard, deleting the plugin file from /wp-content/plugins/ via FTP should resolve the problem. </p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=7&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-plugins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Themes</title>
		<link>http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-themes/</link>
		<comments>http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-themes/#comments</comments>
		<pubDate>Tue, 18 Nov 2008 15:28:30 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=5</guid>
		<description><![CDATA[<p>Last week, we looked at installing WordPress's blogging software. If you're playing along, you should have a WordPress install that looks something like the screenshot on the left. As well as starting writing, one of the first things you'll probably want to do is to change the look of your blog. This is done with something WP calls "themes". A theme is a collection of files which modify the... <a href="http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-themes/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.tamebay.com/wp-content/uploads/2008/08/new-kubrick.gif"><img src="http://www.tamebay.com/wp-content/uploads/2008/08/new-kubrick-300x233.gif" alt="" title="new-kubrick" width="300" height="233" class="alignleft size-medium wp-image-3838" /></a><a href="http://www.tamebay.com/2008/08/the-normal-persons-guide-to-installing-wordpress.html">Last week</a>, we looked at installing WordPress's blogging software. If you're playing along, you should have a WordPress install that looks something like the screenshot on the left. As well as starting writing, one of the first things you'll probably want to do is to change the look of your blog. This is done with something WP calls "themes". </p>
<p>A theme is a collection of files which modify the appearance and layout of your blog. WordPress separates the files that make your blog pretty from the files that make it work - so that you can change the appearance easily and quickly without needing to rebuild the core functionality of the program. </p>
<h2>The least you need to know</h2>
<ul>
<li>Find a theme you like
<li>Download and unzip it
<li>Upload the theme folder to wp-content/themes/
<li>Activate it in the Design section of your dashboard. </ul>
<h2>What to look for in a theme </h2>
<p>Choosing a theme can be a overwhelming process. There are literally <a href="http://www.google.com/search?q=wordpress+theme&#038;ie=utf-8&#038;oe=utf-8&#038;aq=t&#038;rls=org.mozilla:en-GB:official&#038;client=firefox-a">thousands out there</a> to choose from, so where do you start? Think about what you'll need from a theme first:
<ul>
<li>do you want a casual feel, or something more formal and business-like?
<li>do you have a specific image you want to portray - sporty, fashionable, healthy - or will you be more abstract?
<li>what colours do you like? does your blog theme need to match branding you have elsewhere?
<li>what content will you have other than blog posts? do you need space to pimp your eBay listings, your website, or for other advertising?
<li>do you need space to import content from Flickr, YouTube, Twitter, elsewhere?
<li>how do you want the header to look? do you need space for your logo? or photographs? or do you want a very minimal header that leads straight into the main content?
<li>are you picky about which side the sidebar(s) go?
<li>where do you want the navigation placed: across the top, down the side, a mixture of both?
<li>do you like fixed-width layouts, or fluid-width which stretch to the full width of the browser window?
<li>do you want a reverse-chronological theme where the newest post is always at the top, or something more magazine-like and organised by category? </ul>
<p>Many people begin with their colour requirements - "I want a red theme" - but as colour is one of the easiest things to change, it makes sense to start with the more fixed elements, like layout, sidebars, space for advertising, first. Pick a few themes that might be what you want, and preview them all on your own blog (see below): it's surprising how different a theme can look when it's using your own content. </p>
<h2>Finding themes</h2>
<p>The <a href="http://wordpress.org/extend/themes/">official WP theme directory</a> has just started up again; it's a little thin right now, but expect to see it grow rapidly. In the meantime, there are dozens if not hundreds of lists of WP themes for your perusing pleasure: here are a few I like:
<ul>
<li><a href="http://www.smashingmagazine.com/2008/01/08/100-excellent-free-high-quality-wordpress-themes/">Smashing Magazine's top 100 list</a> with lovely big preview graphics
<li><a href="http://www.wpthemes360.com/">WP Themes 360</a> has some nice designs
<li><a href="http://wordpress.pro">WordPress.pro</a> has a few designs which seem to  have business potential
<li><a href="http://www.briangardner.com/themes">Brian Gardner's themes</a> which include Revolution, on which TameBay was built
<li><a href="http://www.pingable.org/20-of-the-best-free-magazine-wordpress-themes/">Pingable's list of 20 free magazine themes</a>, some of which were nearly TameBay </ul>
<h2>Premium and sponsored themes </h2>
<p>Most WordPress themes are free, donated to the community by their creators. A few are "premium", that is, paid-for themes. Although these have the disadvantage that you have to pony up some dough, they have two advantages: firstly, you're unlikely to find as many people using them as the popular freebies, and secondly, you may get some form of support from the designer, which you're less likely to do with free themes. </p>
<p><a href="http://www.solostream.com/2007/07/12/popular-wordpress-sites-say-no-to-sponsored-themes/">Sponsored themes</a> are a little more invidious: they are supported by advertising links in the footer and/or sidebars. Some people object to this, and some don't, but it's something to be aware of: you should know what you're advertising on your own blog. </p>
<h2>Making your own theme </h2>
<p>It's outside the scope of this blog post, but if you're reasonably confident in HTML, CSS and PHP, you can make your own blog theme . This can be particularly useful if you want your blog to fit the design of a larger site, for example if you're integrating it with your ecommerce store. <a href="http://codex.wordpress.org/Theme_Development">WordPress give some advice</a> to those embarking on this path.</p>
<h2>Installing a theme</h2>
<ul>
<li>Download and unzip your chosen theme</li>
<li>Upload the entire theme folder (not just its contents) to <strong>/wp-content/themes/</strong>
<li>Click the "Design" tab on your dashboard
<li>Click the thumbnail of your new theme to preview it with your blog
<li>If you're happy, click the "Activate..." link from the top right </ul>
<h2>Just testing</h2>
<p>It's easy, so test out a few themes you might like:</p>
<p><object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/7z0gniG4P3E"></param> <embed src="http://www.youtube.com/v/7z0gniG4P3E" type="application/x-shockwave-flash" width="425" height="350"></embed></object></p>
<p>Next time, we'll be looking at WordPress plugins, essential add-ons to make your blog a better place to play. </p>
<h3>Related Posts </h3>
<p><a href="http://blogmum.com/2008/11/how-do-i-get-my-new-theme-onto-my-blog/">FTP for absolute beginners</a></p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=5&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2008/11/the-normal-persons-guide-to-wordpress-themes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Installing WordPress</title>
		<link>http://blogmum.com/2008/11/the-normal-persons-guide-to-installing-wordpress/</link>
		<comments>http://blogmum.com/2008/11/the-normal-persons-guide-to-installing-wordpress/#comments</comments>
		<pubDate>Tue, 18 Nov 2008 15:27:40 +0000</pubDate>
		<dc:creator>Sue</dc:creator>
				<category><![CDATA[NPG2WP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogmum.com/?p=3</guid>
		<description><![CDATA[<p>because there are no dummies or complete idiots around here. :-) I've assumed some basic knowledge of t'internet and web hosting here, including how zip files and FTP work. If anything needs more clarification, leave me a comment. Why WordPress? There are lots of blog management systems, and not all of them take effort to install like WordPress does. If you use BlogSpot, for example,... <a href="http://blogmum.com/2008/11/the-normal-persons-guide-to-installing-wordpress/">Read more</a></p>]]></description>
			<content:encoded><![CDATA[<p><small>because there are no dummies or complete idiots around here. <img src='http://blogmum.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </small></p>
<p>I've assumed some basic knowledge of t'internet and web hosting here, including how zip files and <a href="http://blogmum.com/2008/11/how-do-i-get-my-new-theme-onto-my-blog/">FTP</a> work. If anything needs more clarification, leave me a comment. </p>
<h2>Why WordPress? </h2>
<p>There are lots of blog management systems, and not all of them take effort to install like WordPress does. If you <a href="http://www.tamebay.com/2008/03/blog-101-getting-started.html">use BlogSpot</a>, for example, you can be up and running in a minute or two. But WordPress more than pays off a little effort to get started:
<ul>
<li>the content stays on your own server and can be backed up, by you, so you know it's always going to be there,
<li>the sheer range of <em>stuff you can do</em> with WordPress is unmatched by any other BMS I've seen,
<li>the community around WP is a great place to be,
<li>and it's free.  </ul>
<p>So lets get started. </p>
<h2>The least you need to know</h2>
<ul>
<li>Download the latest version of WordPress from wordpress.org.
<li>Edit wp-config-sample.php with your own database details, and save as wp-config.php
<li>Upload to your hosting
<li>Open /wp-admin/install.php in your browser, and follow the instructions from there. </ul>
<p>Sounds easy, yes? Lets look at each stage in detail.</p>
<h2>Hosting</h2>
<p>You will need some web hosting to run WordPress. The <a href="http://wordpress.org/about/requirements/">up-to-date minimum requirements</a> are available via WP's site: they're pretty basic, and most web hosting accounts will be adequate. If, for example, you're already running your own ecommerce site, you can almost certainly run a WP blog on the same hosting. If you're not sure, WP provide a handy email to copy to your hosts to check.</p>
<p>If you don't have hosting yet, <a href="http://wordpress.org/hosting/">WP have a number of recommended hosts</a>: they're all in the US, but that largely doesn't matter, and several of them offer one-click WP install. This can be an advantage getting started, but do check that the version you're being offered is the most recent one, and remember you'll have to keep it updated yourself when new releases come out.</p>
<h2>Get the software</h2>
<p>You can always find the latest release of WordPress <a href="http://wordpress.org/download/">via wordpress.org</a>. If you downloaded it a while back but haven't installed it yet, check that there isn't a newer release before you go any further: new releases add security features as well as functionality, so it's important to keep your WP install up to date. </p>
<p>Once downloaded to your computer, you'll need to unzip the software. If this doesn't happen automatically (and it should), <a href="http://www.google.com/search?hl=en&#038;safe=off&#038;client=firefox-a&#038;rls=org.mozilla%3Aen-GB%3Aofficial&#038;hs=0S3&#038;q=free+unzip&#038;btnG=Search">there are any number of free utilities to do this</a> for you. Save everything on your PC somewhere where you can find it again easily. </p>
<h2>Edit wp-config-sample.php</h2>
<p>This is the file that gives WordPress the specific information about your own database installation. You'll need to edit the bits in red (be careful you don't delete any inverted commas by mistake):</p>
<pre>define('DB_NAME', '<span style="color: red;">putyourdbnamehere</span>');    // The name of the database
define('DB_USER', '<span style="color: red;">usernamehere</span>');     // Your MySQL username
define('DB_PASSWORD', '<span style="color: red;">yourpasswordhere</span>'); // ...and password
define('DB_HOST', '<span style="color: red;">localhost</span>');    // 99% chance you won't need to change this value </pre>
<p>The bits after // on each line are comments to help you. </p>
<p>Where do you find this info?
<ul>
<li>Your hosting package may come with a database already set up. Check your control panel or the welcome email you received when you opened your account.
<li>You may need to manually set up a database yourself; look on your control panel for something like database or MySQL management.
<li>If in doubt, your hosts will be able to give you the information. </ul>
<p>In the same file, you'll see three "<a href="http://codex.wordpress.org/Editing_wp-config.php#Secret_keys_.282.6.29">secret key</a>" phrases: change these to something long and nonsensical. </p>
<p>Use Notepad or another plain text editor, *not* Word, to edit PHP files. Save the edited file as <strong>wp-config.php</strong> (.php is the file extension: if your text editor tries to call it wp-config.php.txt or similar, override that). </p>
<h2>Upload WordPress </h2>
<p><img src="http://www.tamebay.com/wp-content/uploads/2008/08/wp-files.gif" alt="" title="wp-files" class="alignnone size-full wp-image-3847" /><br />
You now have a folder on your PC called Wordpress, with all the WP files in it: you need to upload the *contents* of that folder to the directory on your server where you want the blog to appear. </p>
<p>So now you need to decide what you want the URL of your blog to look like.
<ul>
<li>If your blog is part of a larger site, you might want it in its own directory, for example <strong>www.domain.com/blog</strong>: upload the WP package to that directory.
<li>If the entire domain *is* your blog, then upload to the root public HTML directory (which might even be called public_html, depending on your hosts). </ul>
<p> <img src='http://blogmum.com/wp-includes/images/smilies/icon_eek.gif' alt=':shock:' class='wp-smiley' />  Don't upload the WordPress folder itself, only its contents, or you'll end up with URLs that look like www.domain.com/blog/wordpress. </p>
<p><a href="http://www.tamebay.com/wp-content/uploads/2008/08/wp-install-screen.gif"><img src="http://www.tamebay.com/wp-content/uploads/2008/08/wp-install-screen-300x222.gif" alt="" title="wp-install-screen" width="300" height="222" class="alignleft size-medium wp-image-3863" /></a>Once the upload is complete, open <strong>[your blog directory]/wp-admin/install.php</strong> in your browser, and follow the on-screen instructions. You'll need to tell WordPress the title of your blog and your email address, and then it will install everything for you. At the end of the installation, you'll be given an admin password. This should also be emailed to you, but make a note of it now - WP generates some fantastically random passwords, so I'd make the next thing you do...</p>
<h2>Set up your admin user account and password</h2>
<p>Click the "users" link from the top right, and then the "admin" user name. You can fill out some important details here including how you want your name to display on your posts (unless you want to be called "admin" forever), and also change your password to something you can remember. </p>
<p>Now would also be a good time to bookmark your admin dashboard: it lives at <strong>/wp-admin/</strong> if you forget. </p>
<p><a href="http://www.tamebay.com/wp-content/uploads/2008/08/new-kubrick.gif"><img src="http://www.tamebay.com/wp-content/uploads/2008/08/new-kubrick-300x233.gif" alt="" title="new-kubrick" width="300" height="233" class="alignleft size-medium wp-image-3838" /></a><br />
<h2>And we're done!</h2>
<p>You should now have a plain-vanilla install of WordPress, that looks something like the screen shot to the left. This is now functional, and you can start writing: click "Write" from the top of your admin dashboard to write a post. WordPress comes with one post and one comment "pre-installed"; you probably want to delete these, so go into "Manage" to remove them. </p>
<p>It's worth taking a bit of time to look around the WordPress dashboard at this point: generally, things you might want to use often (Write, Manage, Comments) are the big links on the left, and things you'll use less often are the smaller links on the right. It can look a little daunting at first, but once you get used to what lives where, it's really pretty straightforward.</p>
<p>Next weekend, we'll be looking at making things pretty with WordPress themes.</p>
<img src="http://blogmum.com/?ak_action=api_record_view&id=3&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blogmum.com/2008/11/the-normal-persons-guide-to-installing-wordpress/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
