[jbosstools-issues] [JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-18813:
---------------------------------------------

A few thoughts on what I believe we have learned from the last 2(?) years of having central.

1) users do not notice our software update page
2) it needs to not be slow/take alot of screen estate. 
3) if content is too JBoss specific some users just dont use it since they think its not relevant to them.

Since installing features is a key thing JBDS IS (integration stack) need to do and its also where addons for i.e. Mobile development will be I think it would be good
if we could make the software tab either more visible or at least more "findable". One way we already doing are that we can add wizards for plugins not installed yet,
this will help users to install the new plugins but it won't make them aware of the software update page that might have other features they like.
 
I dont have a good suggestion on *how* to make this better but it definitely makes me think that adding more tabs for users to click on is *not* a good idea.

#2 about speed I believe is crucial, not only about how fast it loads but also that users should be able to find what they want fast and not be overloaded with info.
Which also related to #3, hence we should not add lots of marketing info to this but instead focus on getting started on projects and/or quickstarts. 

About customization then my thinking here was to not make every part of the page customizible but more that since we will have different users and different usecases
my thought was we would 'tag' all our content with one or more tags (i.e. 'javae', 'mobile', 'integration', 'hibernate', 'switchyard' etc.) and then the user can say 
which content is interesting to them and we simply sort the content based on the tags.

so i.e. a default user will get nothing listed as most important and our default sorting of wizards will have just javaee ones first, and if a user installs integration stack we add 'integration' to his interests and it will make it so he get things tagged with 'integration' first and then 'javaee'  Same happens if user goes and install 'mobile' we will add that to his interest list and it will show up before 'javaee'.

This means users does not need to actually state or change anything and we will adapt to his actual installed 'interetsts'. We should of course let him turn on/off his interests but that could just be a simple banner of "tags" that he can turn on/off.



 



> Convert JBoss Central to an HTML5 page
> --------------------------------------
>
>                 Key: JBIDE-18813
>                 URL: https://issues.jboss.org/browse/JBIDE-18813
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: central
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, Screen Shot 2015-01-16 at 4.38.58 PM.png
>
>
> Central Page requires new capabilities :
> - needs more customization (display content depending on user preferences)
> - needs to scale with JBDS-IS, Fuse content
> - access to more examples, with filtering capabilities
> Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach : 
> - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
> - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)