Merge pull request OpenUserJS#974 from Martii/Issue-944moreDOCchanges

Few more doc changes

Auto-merge

Author: Martii

views/pages/documentPage.html

@@ -17,7 +17,12 @@ <h2 class="page-heading">
         <div class="panel panel-default">
           <div class="panel-body">
             <h3><a name="welcome"></a>Welcome<a class="anchor" href="#welcome"><em class="fa fa-link"></em></a></h3>
-            <p>Welcome to {{#pkg.name}}{{pkg.name}} <em>(OUJS)</em>{{#pkg.version}} v{{pkg.version}}{{/pkg.version}}{{/pkg.name}}{{#process.version}} using Node {{process.version}}{{/process.version}}{{#lastRestart}} last restarted on {{lastRestart}}{{/lastRestart}}{{#lockdown.scriptStorageRO}} in Read-Only Script storage mode;{{/lockdown.scriptStorageRO}}{{#lockdown.updateURLCheck}} <code>@updateURL</code> is required;{{/lockdown.updateURLCheck}}.</p>
+            <p>Welcome to {{#pkg.name}}{{pkg.name}} <em>(OUJS)</em>{{#pkg.version}} v{{pkg.version}}{{/pkg.version}}{{/pkg.name}}{{#process.version}} using Node {{process.version}}{{/process.version}}{{#lastRestart}} last restarted on {{lastRestart}}{{/lastRestart}}</p>
+            <ul>
+              {{#lockdown.scriptStorageRO}}<li>Read-Only Script storage mode is in effect.</li>{{/lockdown.scriptStorageRO}}
+              {{#lockdown.updateURLCheck}}<li>UserScript metadata block <code>// @updateURL</code> is required.</li>{{/lockdown.updateURLCheck}}
+              <li><em>No other site status messages at this time.</em></li>
+            </ul>
             <h3><a name="mission"></a>Mission<a class="anchor" href="#mission"><em class="fa fa-link"></em></a></h3>
             <p>User scripts are best described as lightweight site-specific browser extensions, written entirely in JavaScript and containing a specially formatted block of metadata that tells a User script engine, such as Greasemonkey, on what site to run the script. The script can do anything that originally JavaScript running on a website can do, such as modify the appearance or functionality of the site on the client-side. Some User scripts employ special API functions &ndash; provided by the User script engine &ndash; to do things that normal client-side JavaScript cannot, like cross-domain xmlhttpRequests. People who write User scripts <em>(script authors)</em> want a place to publish them where other users can download scripts for installation. And users want a place to find scripts that will be useful for them. There existed a de facto user script repository called userscripts.org. The site had many users and contained thousands of User scripts. Unfortunately userscripts.org has been in a state of flux and has been currently offline. Many active User script developers have expressed an interest in improving the site, but it remains closed source. Several members have shown interest in contributing to a competing open source User script repository and that is how the idea for OpenUserJS was born.</p>
             <p>OpenUserJS.org is built mostly in the native tongue of what User scripts are written with. This has the extreme advantage of being able to contribute directly to the project without being hindered by alternate computer programming languages that may or may not be compatible. It makes paramount sense to have a site built with JavaScript and not some possibly unfamiliar and alternate computer syntax with no relation to JavaScript. <strong>This allows OpenUserJS to be at the top of its class</strong>. Developers, or collaborators as it is sometimes referred to, are also highly encouraged to use all the tools available in the development environment. This includes a private database to test things before they are implemented as well as the standard open-source philosophy granted with our repository at GitHub. All of the tools made openly available are a great set of places to share findings through testing and other forms of collaboration from bug fixes to having meta discussions regarding adding or changing new features and general usage.</p>