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

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-12355:
---------------------------------------

[~maxandersen]It seems you have everything it needs by default on mac.

{quote}ExecJS lets you run JavaScript code from Ruby. It automatically picks the best runtime available to evaluate your JavaScript program, then returns the result to you as a Ruby object.

ExecJS supports these runtimes:
therubyracer - Google V8 embedded within Ruby
therubyrhino - Mozilla Rhino embedded within JRuby
Node.js
Apple JavaScriptCore - Included with Mac OS X
Microsoft Windows Script Host (JScript)
{quote}

I guess Google Chrome install V8 and that's why it is working for me.
                
> 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
>             Fix For: 4.0.x
>
>         Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
>  etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://xcoulon.github.io/jbosstools-website/ <-- current version

--
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