Difference between revisions of "Features"

From QualityBox Wiki
Jump to navigation Jump to search
(migrated content)
(link to Look and Feel)
 
Line 1: Line 1:
 
 
The emphasis is on a complete feature set, quality, performance, and security that is turn-key, simple to use, and supported.
 
The emphasis is on a complete feature set, quality, performance, and security that is turn-key, simple to use, and supported.
  
Line 6: Line 5:
 
== Enterprise features ==
 
== Enterprise features ==
 
# Links to your Windows shared resources via '''Universal Naming Convention''' (UNC links) are supported.
 
# Links to your Windows shared resources via '''Universal Naming Convention''' (UNC links) are supported.
# Beautiful, responsive, mobile-first look and feel
+
# Beautiful, responsive, mobile-first [[Look_and_Feel|look and feel]]
 
# Clean URLs for easier use, better SEO.
 
# Clean URLs for easier use, better SEO.
 
# REST-like action verbs extend “Clean URLs” to include all the regular user interactions like ‘edit’ and ‘history’
 
# REST-like action verbs extend “Clean URLs” to include all the regular user interactions like ‘edit’ and ‘history’

Latest revision as of 10:43, 8 August 2019

The emphasis is on a complete feature set, quality, performance, and security that is turn-key, simple to use, and supported.

Free SSL included. https://wiki.example.com

Enterprise features[edit | edit source]

  1. Links to your Windows shared resources via Universal Naming Convention (UNC links) are supported.
  2. Beautiful, responsive, mobile-first look and feel
  3. Clean URLs for easier use, better SEO.
  4. REST-like action verbs extend “Clean URLs” to include all the regular user interactions like ‘edit’ and ‘history’
  5. Advanced “Document Not Found” handling
  6. Licensing selections in the “Upload” form.
  7. “Help” content included.
  8. Flexible powers for Site Administrators
  9. String Functions (via Scribunto and Lua)