Merge pull request #311 from miharp/docs/issue-247-contributing

docs: remove stale OpenVoxDB CONTRIBUTING page

Author: corporate-gadfly

_data/nav/openvox_8x.yml

@@ -255,7 +255,7 @@
     link: "designing_convenient_roles.html"
 - text: Hiera
   items:
-  - text: Hiera
+  - text: About Hiera
     link: "hiera_intro.html"
   - text: Interactive Hiera Demo
     link: "hiera_demo.html"

_data/nav/openvoxdb_8x.yml

@@ -5,8 +5,6 @@
     link: release_notes.html
   - text: Overview and requirements
     link: index.html
-  - text: Contributing to OpenVoxDB
-    link: CONTRIBUTING.html
   - text: Frequently asked questions
     link: puppetdb-faq.html
   - text: Versioning policy

docs/_openvox_8x/hiera_config_yaml_3.md

@@ -29,7 +29,7 @@ This version of Puppet supports three formats for hiera.yaml --- you can use any
 
 ## Important: version 3 is deprecated
 
-Version 3 of hiera.yaml is deprecated, and we plan to remove support for it in Puppet 6.
+Version 3 of hiera.yaml is deprecated and not recommended. OpenVox 8.x still supports it for backward compatibility, but you should use [version 5][v5] instead.
 
 More importantly, it has some major problems:
 

docs/_openvox_8x/hiera_config_yaml_4.md

@@ -22,7 +22,7 @@ v4     | Environment and module layers | Deprecated. A transitional format, used
 
 ## Important: version 4 is deprecated.
 
-Version 4 of hiera.yaml is deprecated, and we plan to remove support for it in Puppet 6.
+Version 4 of hiera.yaml is deprecated and not recommended. OpenVox 8.x still supports it for backward compatibility, but you should use [version 5][v5] instead.
 
 More importantly, version 4 can't use some of Hiera 5's best new features, like custom backends.
 

docs/_openvox_8x/hiera_migrate.md

@@ -21,6 +21,8 @@ title: "Upgrading to Hiera 5"
 [custom_backend_system]: ./hiera_custom_backends.html
 [functions_puppet]: ./lang_write_functions_in_puppet.html
 
+> **Note:** Hiera 5 has been the default since Puppet 5 (2017), so most OpenVox 8.x users already use it and do not need this guide. It remains here for the rare case of migrating very old Hiera 3 data.
+
 Upgrading to Hiera 5 offers some major advantages. A real environment data layer means changes to your hierarchy are now routine and testable,
 using multiple backends in your hierarchy is easier and you can make a custom backend.