Improve site navigation

Bug #225743 reported by Uli Fouquet
4
Affects Status Importance Assigned to Milestone
Grok Web Site
Confirmed
Undecided
Kamon Ayeva

Bug Description

Here is the navigation structure, as already proposed on the grok-dev mailing list (with modifications suggested by Kevin and others).

1) Get Grok(ked) [or Get Started]

• Download (also including: installation from SVN, installation issues, etc.)
• "Beginner" Tutorial (this is a direct link to the Tutorial in the "Reference Manual")
• Releases
• Grok extensions

This is a new section we propose to add, and which should come first, to get people started with Grok.

2) About Grok

• Why Grok ?
• Features
• Component Architecture
• Projects using Grok
• Who is Grok ?

This is already existing. We just need to improve its content a bit, and maybe add the "Projects using Grok" page.

3) Documentation

• "Beginner" Tutorial (this is a direct link to the Tutorial in the "Reference Manual")
• Developer Notes
• Refence Manual (this links to HTML generated using Sphinx on the server)
• Howtos (PHC)
• Tutorials (PHC)

4) Community

• Grok Mailing Lists & Forums
• IRC Channel / IRC Channel Log
• Grok Wiki
• Issue tracker

We will start with implementing this step by step starting with the GetStarted section.

Kamon, Fred & Uli

Changed in grok-web:
assignee: nobody → kamon-ayeva
status: New → Confirmed
Revision history for this message
Kevin Teague (kevin-bud) wrote :

My vote is for a section labelled 'Get Started' that only contains installation, first step links, etc. 'Releases' and 'Grok extensions' could be in other sections of the site. If we lump it all together under a 'Get Grok' section then we are mixing content of interest to the first time visitor with content of interest to a repeat vistor in the same section.

But then we don't want to have too many sections, so where do Releases and Grok Extensions go? Perhaps Releases could go into 'About Grok' or keep 'Project' around? I also think Grok Extensions (or whatever it's called "Grok Add-ons" "Grok Parts"?) is an important enough content area that it should have it's own section (and ideally it's own content-type or be hosted in a Grok mini-app).

However, I don't feel really strongly about the above statements - every visitor is going to expect to find things in slightly different ways in slighlty different places ... the proposals above are an improvement over the existing structure.

Revision history for this message
Kamon Ayeva (kamon-ayeva) wrote :

Ok, so alternative organization is (following Kevin's remark)::

1) Get Started

• Download (also including: installation from SVN, installation issues, etc.)
• "Beginner" Tutorial

2) Grok development _or_ Developing with Grok

• Releases
• Grok extensions

3) About Grok

• Why Grok ?
• Features
• Component Architecture
• Projects using Grok
• Who is Grok ?

4) Documentation

• "Beginner" Tutorial (this is a direct link to the Tutorial in the "Reference Manual")
• Developer Notes
• Refence Manual (this links to HTML generated using Sphinx on the server)
• Howtos (PHC)
• Tutorials (PHC)

5) Community

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.