Explicitly declare a transparent background color in the inline `style` declaration so the search box doesn't render white text on a white background in Safari. Remove `.bg-transparent` from the class attribute, since it doesn't exist in the built CSS file.
Explanation: for some reason (Purgecss misfire?) the CSS class `bg-transparent` does not appear in the built CSS file, so the assignment of the class to the `input` element is meaningless. The inline style declared using the `background` shortcut declaration lacks a background-color, which Chrome and Firefox interpret as a transparent background but which Safari just ignores, falling back to its default white background. This means text typed into the search field renders as white on white, effectively invisible. By explicitly declaring a transparent background color, the search box renders correctly in all three browsers (white text on black background).
"300s of Themes" is not typical English usage and makes it sound like themes are packaged in groups of 300. I've changed this to "300+ Themes" to make more sense.
```
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
```
I realise that these meta tags aren't doing any harm - but they are not needed at all and take up a few bytes of the page loading.
- The `HandheldFriendly` meta tag was used for a very old version of BlackBerry.
REF: https://developer.blackberry.com/playbook/html5/documentation/handheldfriendly.html
- The `MobileOptimized` meta tag was used for a very old version of Windows Mobile 5 / 6 (before even Windows Phone 7, 8 and Windows Mobile 10!).
Closes#743
- Added note that the content directory of an ExampleSite is now inherited from the HugoBasicExample for security reasons.
- Removed placeholder text for example README outline since there is no such outline.
- Instead I updated some of the points of what should be included in a README
cc: @digitalcraftsman
Adds a config entry to Directory Structure
Adds a Hugo.Environment entry to variables/hugo
Edit the configuration page to wrap first part under a Configuration File heading and introduce a second heading, Configuration Directory to present the feature.
