iand

There are a few other methods at the bottom of this page too:
Installing_Multiple_Blogs

One thing you might want to do is make use of parent categories to create nested lists of related categories. So you might get something like this:

electronics <– parent
– computers <– subcategory
–wireless <–sub-sub category

You could also have a look at tagging plugins which would allow you more flexibility in classifying posts without creating more categories.

Podcasts are fine in their own category as you give your listeners the ability to subscrible to that single category

Copy and pasted from the Codex (which is blocked from China). Appoliges for not reformatting but it is time to go home from work:

Giving WordPress its Own Directory While Leaving the WordPress Index File in the Root Directory

There are times when you may need more control over where your WordPress files are on your server. You can have the core WordPress files in their own directory and limit the only WordPress files in your root directory to the index.php and .htaccess files. Some users want WordPress to power their site, but they also want to have their other programs and directories segregated from WordPress to avoid conflicts.

To begin, you need three pieces of information:

1. The new address to which you will have moved the WP core files (eg. http://example.com/wordpress)
2. The new address of the directory to which you will move the basic index.php (eg. http://example.com)
3. The path in the file system to the new location to which you will move wp-blog-header.php (eg. /home/user/public_html/wordpress/wp-blog-header.php).

Note: To find the file system path to a directory: in a blank text file, add the following and save it as a PHP file, such as filesystem.php, and upload it to the directory for which you want to find the path. Run it by typing in the address in your browser to the file such as http://example.com/wordpress/filesystem.php:

<?php echo dirname(__FILE__); ?>

The process to move WordPress into its own directory and have the index.php in the root directory is as follows:

1. Create the new location for the core WordPress files to be stored.
2. Go to the Options panel.
3. In the box for WordPress address (URI): change the address to the new location of your main WordPress core files. Example: http://example.com/wordpress/
4. In the box for Blog address (URI): change the address to the new location of the index.php file in your root directory. Example: http://example.com/index.php
5. Click Update Options.
6. Move your WordPress core files to the new location. This includes the files found within the original directory, such as http://example.com/wordpress along with all of the directories in that directory, to the new location.
7. Copy the index.php and .htaccess files from the WordPress directory into the root of your site.
8. Open index.php in a text editor
9. Change the following and save the file. Change the line that says:
require(‘./wp-blog-header.php’);
to the following, using your directory name for the WordPress core files:
require(‘./wordpress/wp-blog-header.php’);
10. Login to the new location. It might now be http://example.com/wordpress/wp-login.php
11. If you have set up Permalinks, go to the Permalinks panel and update your Permalink structure. WordPress will automatically update your .htaccess file if it has the appropriate file permissions. If WordPress can’t write to your .htaccess file, it will display the new rewrite rules to you, which you should manually copy into your .htaccess file (in the same directory as the main index.php file.)

Caveats

The only catch is the “Edit this” links will no longer appear by every entry and comment if you’re using this option. This is a limitation of how we’re setting cookies, and this may be fixed in the future.

[Just an aside – is the google cache of the codex blocked too?]

I am not sure if it a bug or slightly convoluted logic (after all, you are still home, just looking at page two of it).
For a fix try ((is_home()) && ($paged <= "1"))
though you might need == instead of <=

If you are after:
category 1
*post
*post
category 2
*post
*post etc..

Try this thread. You can see an example of it here (select ‘ajaxed’ from the theme list).

I use this plugin (with 2.0.1) which gets rid of the submit button.

Alternatively, in your root index.php add the following:

if( !isset($cat) ) {
$cat = '-4';
}

above the line require('./wp-blog-header.php');

Again assuming you want to exclude category 4. May have slighty different results to Petit’s solution, but works for me. Caveat – you can exlcude only one category with this method.

I have been getting that error for the last month or so (about since ping-o-matic was revamped). Have also seen a few other people with the same problem.

There is probably a way to point it at some other ping-server instead, but have not had any luck find a solution as yet.