@Balaji, Spark is a good case to support version specific wiki pages.  What’s 
more, their layout addresses some of your concerns.  The latest documentation 
is at https://spark.apache.org/docs/latest/ and for previous versions you 
simply have to change the version in the URL, e.g. 
https://spark.apache.org/docs/1.2.1/.  A reasonable user would guess and go to 
the parent page (https://spark.apache.org/docs/) and navigate to the version of 
interest.

  *   Virtue of this approach is predictability to our users.  At any point in 
time we would have people at different versions of Ranger.  So this might help 
to keep the documentation stable for people at all versions.  Items that don’t 
change can be soft links to parts that stay the same from version to version 
(this is my guess as to how spark might have it).
  *   On the flip side depending on the tool that we use for wiki this may or 
may not be easy to do.

My 2 cents.

From: Balaji Ganesan
Reply-To: 
"[email protected]<mailto:[email protected]>"
Date: Wednesday, July 29, 2015 at 9:27 AM
To: "[email protected]<mailto:[email protected]>"
Cc: "[email protected]<mailto:[email protected]>"
Subject: Re: Rearranging Ranger Wiki pages ...

I think the Index page should be generic and not be tied to the release. I am 
looking at https://cwiki.apache.org/confluence/display/Hive/Home or 
http://wiki.apache.org/hadoop/ for what some of top projects include in their 
wiki.

The index page is probably the first page user would land and would need to be 
the link page to get to any section of the wiki easily. Here is what we should 
include in the index page

- Ranger overview
- How to get started?
- Ranger documentation (install, user guide)
- Ranger developer guide
- Ranger blog or tutorials

Some of the ranger documentation would be pertinent to the current release.



On Tue, Jul 28, 2015 at 1:17 PM, Don Bosco Durai 
<[email protected]<mailto:[email protected]>> wrote:
We might need to do some rearrangement of the wiki pages to make it more
scalable. At the high level, this is the principal we originally organized
the wiki pages:
1. Dashboard/Index page as the link to all important pages and links
2. Top level page tree is limited to top level pages (so we can avoid
clutters)
3. Each release has it¹s own page. All release related artifacts are
contained within the respective release page

Proposed change is to have top level release page under home/index and move
all the release folders/pages underneath it. This will help us limit the
pages under home/index.

If there are no objections, I will move the existing release specific
folders into /Release Folders. The downside is that anyone linking to
existing pages will break. But this is the downside of us using Wiki. The
search engines will reindex the new pages (eventually)

Seems our website also needs updates based on the 0.5 release. And it will
be good to overall it in the process. Any volunteers?

Thanks

Bosco








Reply via email to