Editing WordPress Installation Guidelines (section)

== Installation ==

=== Workflow ===

=== Guidelines ===
* When installing for a client make sure to create an admin account and an editor account. 
* Give the client the editor account without admin privileges so they can’t attempt to update WP themselves.

=== Installing the WordPress distribution ===

* Download latest version of WordPress.
* Unzip into the site directory.
* (Optional, but recommended) Rename the root directory. See [[#Installing_WordPress_in_a_non-standard_location|Installing WordPress in a non-standard location]]

=== WordPress configuration settings & procedure ===

* Configure the installation using WordPress's script by navigating to `[staging_server]/[root_dir]/wp-admin/`
** '''Database Name:''' `[CLIENT]_wp` ''(this may have to change to accommodate the client's hosting provider)''
** '''User Name:''' `[CLIENT]_wp` ''(this may have to change to accommodate the client's hosting provider)''
** '''Password:''' Go get a new secure one.
** '''Database Host:''' `localhost` ''(default setting)''
** '''Table Prefix:''' `wp_` ''(default setting)''
** Record the first 3 settings somewhere, like in the (non-WP) `app_config` file.
** Click '''OK'''
* WordPress installs the database objects.
* Click '''Run the install''' when prompted.
* Enter '''Site Title''', '''Username''', '''Password''', '''Email''', and '''Allow search engines to index this site''' when prompted
** Enter "admin" user credentials, using a very secure password.
** Enter your own email address.
** Click '''OK''' or whatever.

=== Client configuration ===

* Log in as "admin".
* Create a editor account for the client's use.
** Dashboard > Users > Add New
*** Username and strong but semi-english password
*** Client's email address
*** '''Role:''' Editor

=== Theme ===

* See: [[Creating Custom WordPress Themes]]

=== Installing WordPress in a non-standard location ===
How to install WordPress in a non-standard location to make it at least a little bit difficult for people to hack it.

* Install WordPress somewhere other than the location that you would ultimately like to have the public access it.
** The WordPress directory and the directory where the public will access the blog should be at the same level down from the website root directory.
** So the set up might be something like this:
<pre>
/blog (public address)
/wordpress/wp-admin (WordPress installation location with CMS)
</pre>
Copy the <code>index.php</code> file from the WordPress installation directory to the public blog location. <code>Index.php</code> basically just makes a call to the WordPress library to pull in all the content to render the page. As long as all the include directives resolve ok, that index.php file will work anywhere on the site, but bad people won’t be able to simply type <code>/blog/wp-admin</code> to try to get at the WordPress editor.