If you have read the you should have created a public directory and if you installed XAMPP by using the following XAMPP tutorial, this directory will probably be in "C:\xampp\htdocs\myapp\public". Open the "public" folder of your app and create a new file called ".htacess" using your text editor or your IDE. If you can't see the htaccess file in the public folder after creating it, open the view "tab" in the Windows Explorer and enable "File name extensions and Hidden items" by clicking the checkbox next to it.
Adding an environment variable to our htaccess
The first thing we will add to our htaccess file is the environment variable. Our app will have an environment variable which will have three possible values, the first one is "development", the second one is "testing" and the third one is "production". "development" will be the environment type we will use while developing our application. "testing" is the environment variable value we will use while testing of our application and finally "production" is application environment we will use after we have deployed our application on the production server(s).
My goal was to create a structure that is very easy to understand, flexible enough for big or small websites and not totally different from what books or other guides recommend as a "files and folders structure for a Zend Framework project" best practice.
Another goal was to create a CMS core, which has lots of modules that can be (re)-used on (multiple) other websites. Every module is designed so that it can be copied and put in another project without having to modify any file of that project. The main directory of each module contains all the files it needs to work, I has its own bootstrap, its own configuration files, its views and of course its own models.
Installation of redis on CentOS 6:
Redis (the redis.io key-value store) is available in the remy repo which depends on the epel repo:
If you didn't already previously add the remi repo to your repositories then follow the following step to do so.
I wanted the remi repo "Enterprise Linux 6 (with EPEL)" package, you may have to use another one depending on your OS and version, i used centos6 and therefore choosed to use the following commands:
What are WAI-ARIA roles and what are they good for?
WAI-ARIA roles get used to annotate page elements. One of the goals we want to achieve by using WAI-ARIA roles is to improve accessibility, this means improving the way screen readers parse the document and therefore make it better machine readable so that screen readers can represent the content to the user with text-to-speech, sound icons, or on Braille output device.
Another goal is that we also improve the way search engines consume our content, because if you care about SEO it is never a bad idea to improve the semantic value of your document. If you use the ARIA roles and maybe also the new HTML5 elements you will improve the semantic value of your content. The more we define the structure of our documents the easier it is for a search engines to extract the valuable content. We can therefore also avoid getting penalized because we are tagging the content that is complementary and that is found on each of our pages, by clearly separating it from the more important part of the document.