[
https://issues.jboss.org/browse/JBDS-2872?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2872:
----------------------------------
Re: template:
Wow. They've just barely rolled out
https://www.jboss.org/products/eap and now
it's being completely reskinned as
http://www-stg.jboss.org/products/eap/overview/ ?
Similarly...
http://www.jboss.org/products/devstudio/ vs.
http://www-stg.jboss.org/products/devstudio/overview/
Re: copy:
If I change copy on
devstudio.jboss.com I will have to change it on the various
jboss.org
pages too. Not adverse to that, but technically that's Marketing's job so maybe we
want to wait until they settle on a skin & possibly clean up the copy themselves?
Also, re: first occurrence of product name appearing in copy as "Red Hat JBoss
Developer Studio" instead of "JBoss Developer Studio" - the graphic above
the copy and the page's <title> tag both conform, so the need to have the copy
prefixed w/ "Red Hat" seems unnecessary.
Re: two links:
I could have them target different anchors, or we could just have the one link. One is
probably simpler.
Re: password access to update sites
JBDS 3 required a password to use the update site. Details here:
https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
https://devstudio.jboss.com/download/7.x.html should direct users to
https://www.jboss.org/products/devstudio.html
------------------------------------------------------------------------------------------------------------------
Key: JBDS-2872
URL:
https://issues.jboss.org/browse/JBDS-2872
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: build, updatesite
Affects Versions: 7.1.0.GA
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 7.1.1.GA
Attachments: new-jbds-7x-dl-page.png
https://devstudio.jboss.com/download/7.x.html should direct users to
https://www.jboss.org/products/devstudio.html instead of the old JBDS PE / JBDS Eval
process.
--
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