I am not sure we have a clear guidance from Apache for using Wiki vs
website for documentation.

What I liked about wiki is ease to add new content and potentially have
comments from users. I would vote for website being basic and being
redirected to wiki for all content. Not sure what others think on this..

On Wed, Jul 29, 2015 at 10:29 AM, Don Bosco Durai <[email protected]> wrote:

> Our current one is based on Kafka
> https://cwiki.apache.org/confluence/display/KAFKA/Index
>
> I like Hive wiki better. But it is some work. Since it is going to be
> mostly rearrangement of content, we can create a temporary page and try it
> out. And if we like it, we can move to index.
>
> Also I am worried about having two sites. Wiki and our homepage. Home page
> can be more fancy, but difficult to maintain. Wiki is easy to manage, but
> the look and feel are very basic. We need to have a strategy for
> distributing the content and also making both the sites and easy to go
> back and forth.
>
> Thanks
>
> Bosco
>
>
> On 7/29/15, 9:27 AM, "Balaji Ganesan" <[email protected]> wrote:
>
> >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]>
> 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