[ci skip] Updated the tutorial intro page with more about getting started with it.

Author: lonnieezell

user_guide_src/source/images/error.png

@@ -18,6 +18,10 @@ Getting Started
 
 	installation/index
 
+****************************
+Build Your First Application
+****************************
+
 .. toctree::
 	:includehidden:
 	:titlesonly:

user_guide_src/source/images/welcome.png

@@ -1,6 +1,9 @@
-########
-Tutorial
-########
+############################
+Build Your First Application
+############################
+
+Overview
+********
 
 This tutorial is intended to introduce you to the CodeIgniter4 framework
 and the basic principles of MVC architecture. It will show you how a
@@ -26,7 +29,7 @@ small part of the functionality of the CodeIgniter framework. You'll go
 through the following pages:
 
 -  Introduction, this page, which gives you an overview of what to
-   expect.
+   expect and gets your default application downloaded and running.
 -  :doc:`Static pages <static_pages>`, which will teach you the basics
    of controllers, views and routing.
 -  :doc:`News section <news_section>`, where you'll start using models
@@ -45,4 +48,85 @@ Enjoy your exploration of the CodeIgniter framework.
 	static_pages
 	news_section
 	create_news_items
-	conclusion
+	conclusion
+
+Getting Up and Running
+**********************
+
+You can download a release manually from the site, but for this tutorial we will
+use the recommended way and install the AppStarter package through Composer.
+From your command line type the following:
+
+::
+
+    ➜ composer create-project codeigniter4/appstarter ci-blog -s rc
+
+This creates a new folder, ci-blog, which contains your application code, with
+CodeIgniter installed in the vendor folder.
+
+By default, CodeIgniter starts up in production mode. This is a safety feature
+to keep your site a bit more secure in case settings are messed up once it is live.
+So first let's fix that. Copy or renmae the ``env`` file to ``.env``. Open it up.
+
+This file contains server-specific settings. This means you never will need to
+commit any sensitive information to your version control system. It includes
+some of the most common ones you want to enter already, though they are all commented
+out. So uncomment the line with CI_ENVIRONMENT on it, and change ``production`` to
+``development``::
+
+    CI_ENVIRONMENT = development
+
+With that out of the way it's time to view your application in a browser. You can
+serve it through any server of your choice, Apache, Nginx, etc, but CodeIgniter
+comes with a simple command that takes advantage of PHP's built-in server to get
+you up and running fast on your development machines. Type the following on the
+command line from the root of your project::
+
+    php spark serve
+
+
+The Welcome Page
+****************
+
+Now point your browser to the correct URL you will be greeted by a welcome screen.
+Try it now by heading to the following URL:
+
+::
+
+    http://localhost:8080
+
+and you should be greeted by the following page:
+
+.. image:: ../images/welcome.png
+
+This means that your application works and you can start making changes to it.
+
+Debugging
+*********
+
+Now that you're in development mode, you'll see a toolbar on the bottom of your application.
+This toolbar contains a number of helpful items that you can reference during development.
+This will never show in production environments. Clicking any of the tabs along the bottom
+brings up additional information. Clicking the X on the right of the toolbar minimizes it
+to a small square with the CodeIgniter flame on it. If you click that the toolbar
+will show again.
+
+In addition to this, CodeIgniter has some helpful error pages when you hit exceptions or
+other errors in your program. Open up ``app/Controllers/Home.php`` and change some line
+to generate an error (removing a semi-colon or brace should do the trick!). You will be
+greeted by a screen looking something like this:
+
+.. image:: ../images/error.png
+
+There are a couple of things to note here:
+
+1. Hovering over the red header at the top reveals a ``search`` link that will open up
+Google.com in a new tab and searching for the exception.
+2. Clicking the ``arguments`` link on any line in the Backtrace will expand a list of
+the arguments that were passed into that function call.
+
+Everything else should be clear when you see it.
+
+
+Now that we know how to get started and how to debug a little, let's get started building this
+small news application.