[jbosstools-issues] [JBoss JIRA] (JBIDE-12355) JBoss tools website redesign

Thu Sep 6 10:02:33 EDT 2012

    [ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715433#comment-12715433 ] 

Xavier Coulon edited comment on JBIDE-12355 at 9/6/12 10:00 AM:
----------------------------------------------------------------

Website layout proposal:

{code}
jboss.org/tools
    /index.html -> landing page with carousel, latest news (blog), upcoming events
    /install
        /index.html how/where to download and install JBT/JBDS : nightly/milestones/stable releases. 
    /features
        /index.html -> highlight of the JBT modules 
        /<module>/index.html -> features of the given module
        /<module>/new_noteworthy -> latest news of the given module (simili blog)
                Each N&N file should have a custom header that refers to the JBT release version it is part of (ex : 4.0.0.Alpha1)
                There should also be a link to previous/next N&N
        /new_noteworthy -> aggregation of all the modules news per JBT/JBDS version or redirect to latest version ?
        /new_noteworthy/<version> -> aggregation of all the modules news for a given version 
                Each N&N file should provide a custom header in the .md files that indicates the release version (ex : 4.0.0.Alpha1). This value
                would help aggregating the N&N of each module. Order of modules can be defined in the .md file, too
                Also, this .md file should provide with URLs to download the given version
                There should also be a link to previous/next N&N

    /guides
        /index.html -> Link to Reference doc (hosted on docs.jboss.org/tools/latest) and to video tutorials (/guides/videos/index.html)
        /videos/index.html -> video tutorials hosted on vimeo.com
                     (structure of sections and items is defined in a .md file in _/data - could be moved into /videos/index.md)
                    The URLs could be retrieved from the N&N part
    /community
        /index.html links to code source, JIRA and forums (hosted at community.jboss.org)

    /blog blog articles (including archives)
{code}

Pending items:
       - latest doc reference is hosted on docs.jboss.org -> there could be a link to it from the landing/welcome page. What about previous versions ?
       - jboss.org/tools/usage could be converted into .md, but from where linking to it ?
        (its linked to from the tools - the url jboss.org/tools/usage is shown in dialog box you say yes to be part of the tracking)

>From jboss.org via remote-sitemap generator:
{code}
 http://www.jboss.org/tools 
 http://www.jboss.org/tools/usage *must* stay, linked from the tools itself. Sure. remaining question is: do we link to that page from the website itself ?
 http://www.jboss.org/tools/download *must* stay, main url used in docs/google
 http://www.jboss.org/tools/download/stable, can be a direct
 http://www.jboss.org/tools/download/dev, can be a direct
 http://www.jboss.org/tools/download/nightly, can be a direct
 http://www.jboss.org/tools/download/archive, can be a direct

 installation urls, don't think they are used much, should be there and
 look at why we have a new for each release..
 http://www.jboss.org/tools/download/installation,  
 http://www.jboss.org/tools/download/installation/update_4_0 
 http://www.jboss.org/tools/download/installation/update_3_3 
 http://www.jboss.org/tools/download/installation/update_3_2 
 http://www.jboss.org/tools/download/installation/update_3_1 
 http://www.jboss.org/tools/download/installation/update_3_0 

 // docs ...could be called guides instead (arquillian word)
 http://www.jboss.org/tools/docs -> overview over doc resources
 http://www.jboss.org/tools/docs/news -> link to N&N (not blog)
 http://www.jboss.org/tools/docs/reference -> link to real docs? 
 http://www.jboss.org/tools/docs/screencasts -> replace with /guides/videos 
 http://www.jboss.org/tools/docs/faq 
{code}

      was (Author: xcoulon):
    Website layout proposal:

{code}
jboss.org/tools
    /index.html -> landing page with carousel, latest news (blog), upcoming events
    /features
        /index.html -> highlight of the JBT modules 
        /<module>/index.html -> features of the given module
        /<module>/new_noteworthy -> latest news of the given module (simili blog)
                Each N&N file should have a custom header that refers to the JBT release version it is part of (ex : 4.0.0.Alpha1)
                There should also be a link to previous/next N&N
        /new_noteworthy -> aggregation of all the modules news per JBT/JBDS version or redirect to latest version ?
        /new_noteworthy/<version> -> aggregation of all the modules news for a given version 
                Each N&N file should provide a custom header in the .md files that indicates the release version (ex : 4.0.0.Alpha1). This value
                would help aggregating the N&N of each module. Order of modules can be defined in the .md file, too
                Also, this .md file should provide with URLs to download the given version
                There should also be a link to previous/next N&N

    /guides
        /index.html -> Link to Reference doc (hosted on docs.jboss.org/tools/latest) and to video tutorials (/guides/videos/index.html)
        /videos/index.html -> video tutorials hosted on vimeo.com
                     (structure of sections and items is defined in a .md file in _/data - could be moved into /videos/index.md)
    /install
        /index.html how/where to download and install JBT/JBDS : nightly/milestones/stable releases. 
                    The URLs could be retrieved from the N&N part
     /blog blog articles (including archives)
{code}

Pending items:
       - latest doc reference is hosted on docs.jboss.org -> there could be a link to it from the landing/welcome page. What about previous versions ?
       - jboss.org/tools/usage could be converted into .md, but from where linking to it ?
        (its linked to from the tools - the url jboss.org/tools/usage is shown in dialog box you say yes to be part of the tracking)

>From jboss.org via remote-sitemap generator:
{code}
 http://www.jboss.org/tools 
 http://www.jboss.org/tools/usage *must* stay, linked from the tools itself. Sure. remaining question is: do we link to that page from the website itself ?
 http://www.jboss.org/tools/download *must* stay, main url used in docs/google
 http://www.jboss.org/tools/download/stable, can be a direct
 http://www.jboss.org/tools/download/dev, can be a direct
 http://www.jboss.org/tools/download/nightly, can be a direct
 http://www.jboss.org/tools/download/archive, can be a direct

 installation urls, don't think they are used much, should be there and
 look at why we have a new for each release..
 http://www.jboss.org/tools/download/installation,  
 http://www.jboss.org/tools/download/installation/update_4_0 
 http://www.jboss.org/tools/download/installation/update_3_3 
 http://www.jboss.org/tools/download/installation/update_3_2 
 http://www.jboss.org/tools/download/installation/update_3_1 
 http://www.jboss.org/tools/download/installation/update_3_0 

 // docs ...could be called guides instead (arquillian word)
 http://www.jboss.org/tools/docs -> overview over doc resources
 http://www.jboss.org/tools/docs/news -> link to N&N (not blog)
 http://www.jboss.org/tools/docs/reference -> link to real docs? 
 http://www.jboss.org/tools/docs/screencasts -> replace with /guides/videos 
 http://www.jboss.org/tools/docs/faq 
{code}

> JBoss tools website redesign
> ----------------------------
>
>                 Key: JBIDE-12355
>                 URL: https://issues.jboss.org/browse/JBIDE-12355
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: website
>            Reporter: Max Rydahl Andersen
>            Assignee: Xavier Coulon
>         Attachments: features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> issue to track changes releated to jboss.org/tools redesign

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira