RE: [dsdp-tm-dev] Proposed Website Changes

[Kevin J Doyle <kjdoyle@xxxxxxxxxx>]

Hi Martin,

Some work can be found at http://www.eclipse.org/dsdp/tm/tm-new/
 and a new Bugs page http://www.eclipse.org/dsdp/tm/tm-new/bugs/ 

The work was done before your comments, so it uses a custom nav bar which
we can change as you mentioned below.  I do like the look of this
nav bar though with just the words Information below Target Management.
 Information about Target Management is too long and if the top level
item already says Target Management then it's redundant.
 
+1 for making our frontpage smaller
(ideally 1280x1024) and more sexy
     - Add Screenshot
     - Improved
"What it is" text
     - Offload
"about" info into a good About / learn more... link
     - Offload
downloads / release info into a good "Downloads" link
         -
Note that we need to keep some links for downloadable documents vs. downloadable
software
        
I was thinking that the downloadable documents
could just be found on the About page.

     - Combine
what's new and events
         -
I'd still like to keep all the links about presentation material from previous
conferences etc.
         
 But these might need to be offloaded into a separate page (like "Buzz"
on RAP)

Currently I have a Presentations link on
the navbar for this.  Buzz would probably be better though, as we
could then link to articles, etc in the future.

+1 for the reduced Eclipse.org
header like on RAP and Mylyn
     - Note that
this might actually just be a different Phoenix Theme:
       - Go
to http://www.eclipse.org/phoenix/
and there "Select your theme." "Lazarus"
     - Note that
the smaller layout sacrifices the EclipseLIVE, EPIC and Planeteclipse links
on top right

Correct this is just the Lazarus theme.  I
did some work different from Mylyn/RAP to make sure the increase/decrease
Font links still work. One thing I noticed with this theme is the branding.
  It has a natural spacing between the header and the branding text
now ("Target Management (Remote System Explorer)").  Do
we want a heading like that on every page anyways?

+1 for a good bugs page, it can
be based on what we already have here:
     http://www.eclipse.org/dsdp/tm/development/bug_process.php

I created a page that is similar but
has less links and uses tables to make it look nicer.  We could add
some of the report links as well though and additional queries, but would
like to keep it simple.  The page you linked is focused on the bug
process.  Quick glance at it looks like we need to update it for new
committers/contributors and add some more summary field tags like efs,
ftp, etc.

-1 for fully custom navbar on
the left. We should better be based on the Common Navbar,
    and if that one
is not good then discuss with Bjorn / Process people / Phoenix people
    a better common
Navbar. I'd like to see more consistency in the sites from different projects.
    - Note that even
when we are based on the Common Navbar we can still customize it easily
    - Based on Common
Navbar we'll automatically pick up any REQUIRED changes
    - Add only what
we think we'd like to add (so no more tm-log.csv link)

My main reason for a custom navbar was to
get rid of the Integrators link which use to not link to anything, but
now links to our Getting Started page.  Instead I'll open up a bug
for not displaying menu items for links that aren't defined in the meta
data.  Did we change something recently to make the Integrators link,
link to the Getting Started page?

I'll change the tm-new site to use the Common Navbar with the additions
we like.

+1 for revamping about / getting
started pages
     - perhaps
even separate "getting started for users" vs. "getting started
for integrators"
       where
the latter would point to documents, APIDoc, tutorials, ...

I was thinking about this as well.  If we have enough time/content
to split it up this would be great to do.

--------------------------
Kevin Doyle

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: dsdp-tm-dev-bounces@xxxxxxxxxxx

31/01/2008 05:30 AM

Please respond to
Target Management developer discussions <dsdp-tm-dev@xxxxxxxxxxx>

To	"Target Management developer discussions" <dsdp-tm-dev@xxxxxxxxxxx>
cc
Subject	RE: [dsdp-tm-dev] Proposed Website Changes

Hi Kevin,
 
Great suggestions, over all. Thanks
for your engagement on this. Some details:
 
+1 for making our frontpage smaller
(ideally 1280x1024) and more sexy
     - Add Screenshot
     - Improved
"What it is" text
     - Offload
"about" info into a good About / learn more... link
     - Offload
downloads / release info into a good "Downloads" link
         -
Note that we need to keep some links for downloadable documents vs. downloadable
software
     - Combine
what's new and events
         -
I'd still like to keep all the links about presentation material from previous
conferences etc.
         
 But these might need to be offloaded into a separate page (like "Buzz"
on RAP)
+1 for the reduced Eclipse.org
header like on RAP and Mylyn
     - Note that
this might actually just be a different Phoenix Theme:
       - Go
to http://www.eclipse.org/phoenix/
and there "Select your theme." "Lazarus"
     - Note that
the smaller layout sacrifices the EclipseLIVE, EPIC and Planeteclipse links
on top right
+1 for a good bugs page, it can
be based on what we already have here:
     http://www.eclipse.org/dsdp/tm/development/bug_process.php
-1 for fully custom navbar on
the left. We should better be based on the Common Navbar,
    and if that one
is not good then discuss with Bjorn / Process people / Phoenix people
    a better common
Navbar. I'd like to see more consistency in the sites from different projects.
    - Note that even
when we are based on the Common Navbar we can still customize it easily
    - Based on Common
Navbar we'll automatically pick up any REQUIRED changes
    - Add only what
we think we'd like to add (so no more tm-log.csv link)
+1 for revamping about / getting
started pages
     - perhaps
even separate "getting started for users" vs. "getting started
for integrators"
       where
the latter would point to documents, APIDoc, tutorials, ...
 
Cheers,
--
Martin Oberhuber, Senior
Member of Technical Staff, Wind
River
Target Management Project Lead,
DSDP PMC Member
http://www.eclipse.org/dsdp/tm

---

From: dsdp-tm-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Kevin J Doyle
Sent: Friday, January 25, 2008 6:14 PM
To: dsdp-tm-dev@xxxxxxxxxxx
Subject: [dsdp-tm-dev] Proposed Website Changes


Hi all,

As Martin mentioned at the meeting this week I'd like to spruce up the
website a bit.

I'm going to compare the site to the Mylyn/RAP sites as I believe those
are the best looking project sites.
Mylyn: http://www.eclipse.org/mylyn/
RAP: http://www.eclipse.org/rap/

Here the proposed changes:

1.  Change the layout used to be like the Mylyn/RAP sites.
--> This layout gives us more room as the header is reduced for Eclipse,
which currently takes up a lot of space.

2.  The main page should be reworked.  Take a look at the Mylyn/RAP
sites.
--> We should have an image that can show off as much of the product
as possible.  May need to be the Remote Systems View, so people can
actually see what it is.  Clicking on the image could take you to
a full screenshot showing the whole perspective.
--> Have links to Getting Started, Downloads, and Demos
--> Demos (Screencasts) would be nice to have showing off the basics
and could add more demos over time showing more advanced features.  Like
how to properly setup an EFS project. 
--> Provide a short description of what TM is and a link to the About
page for more information
--> Combine What's New and Events into News and display it in a table
like we have now for Events.
--> Removing the Quick Links and Getting Started div's.
--> Main idea is try to keep this page as short as possible and grab
people's attention.  If it doesn't have a scrollbar on 1280x1024 resolution
that would be ideal.

3.  Create a Bugs page.
--> Instead of having a link to all open bugs have a page dedicated
to Bug queries.
--> At the top have a link to open a bug and a link to the FAQ for what
to include in a bug report.
--> Below that have specific queries for All Bugs, Blocker/Critical/Major/Normal
bugs, Minor/Trivial, and one for Enhancements.  We can break this
up further into RSE/Terminal bugs.  This way users/extenders can see
we have a lot of minor/trivial/enhancement bugs. 

4. Navigation Bar Changes
--> Instead of using the default navigation bar I'd like to create a
custom one.  This way we can get rid of the dead Integrators link
=)
--> The way I see the Nav Bar is as follows.  This goes against
the current Eclipse project requirements though as the Information about
TM link is suppose to be the top item.  A Bug is open requesting to
change the project requirements, as the nav bar as it is now doesn't make
sense to me.  Bug #216474 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=216474
).

Target Management -- Links to main page
   Information  --- Goes to the Information about TM page that
was introduced recently.   ( http://www.eclipse.org/projects/project_summary.php?projectid=dsdp.tm
)
   About  -- Bring back our old About page that the link was
removed to recently
   Team -- Bring back the team page link that was removed recently.
   Plan - Plan for the next release. 
    Presentations - Links to ppt and information about past/upcoming
presentations. 
    Demos - If we have the time to create the demo's mentioned
above having this link would be good.
   Wiki - A link to the main wiki page as it's no longer on the Main
page.  This makes it easier to move around and still get to the wiki.
   Legal - A link to our tm-log.csv file.  This used to be on
the old nav bar, but with the recent changes was removed.  If it's
not required I don't think we need this one.
Users  
   Getting Started
   Downloads
   Bugs - Link to the new proposed Bug page.
   FAQ (wiki) - Link to our FAQ.  Displays wiki in the link to
show it will go to a wiki page.
   Newsgroup
Contributors
  Contributing (wiki) - A link to our FAQ about the part on Contributing.
  Mailing List
  CVS - A link to how to get the source from CVS.
  Development Tools
  
5.  Go through our About and Getting Started pages cleaning them up.
 For example on the Getting Started Page we have:

"The basis of RSE is a former IBM product, for
which a slide
show is still available. Our plans beyond TM
2.0 are available from the Target Management Project
Plan and our Use
Cases Document, which covers all areas of interest
to us. "

That is more for the About page. 

6. Look into simplifying the download page.  Maybe create a new page
that lists the latest release build and the latest milestone.  Have
links to the update site, a direct link to download the SDK, and a link
for all downloads for that release/milestone, which takes you to the current
download page for a release/milestone. Then at the top/bottom have a link
to Archive builds, which takes you to where our Downloads page currently
takes you.  Not sure if this will really simplify the process for
download though.

Opinions, comments, concerns, or additional changes you think we should
make?

Thanks,
Kevin Doyle_______________________________________________
dsdp-tm-dev mailing list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev