The current incarnation of ROS.org is getting a bit long in the tooth; in fact the original roll out of the site was some time in 2013. We’re well past due for a website refresh. After some internal discussion at Open Robotics our general consensus is to drop Wordpress in favor of Jekyll and do a full website rebuild for ROS 2. The motivation for using Jekyll is that the posting workflow is much more developer friendly, and it should make it easier for the community to submit events using pull requests.
Currently, we believe that ROS.org serves three primary use cases for the community:
- The initial entry point for new users looking to get started with ROS.
- A resource for non-technical individuals to find information about ROS and robotics in general (e.g. journalists, investors, educators, etc).
- A rough index of ROS resources for the established community.
The current ROS.org website generally suits these users but is woefully out of date. Our proposal is to keep most of the existing information architecture but give it all a solid update and a facelift. In this new version of ROS.org we would also like to address a few things that were overlooked in previous versions of the website like responsive design, accessibility, and localization. We’re particularly interested in hearing from anyone who might be willing to help translate the core ros.org pages into their local language.
One of the aspects of the current ros.org that we would like to keep are the user submitted “cards” for robots.ros.org. These robot/component cards are simply small bits of markdown that can be submitted by a user in a pull request, and we believe that this approach would be a great way for the community to interact with ROS.org. While we generally prefer ROS related information is on discourse, answers, or the wiki, our current belief is that it would be good to help maintain a lightly moderated lists of things like educational resources, robots and components, and companies using ROS.
Below is a rough outline of what we think the new ROS.org would look like. Sections marked with “card based” are sections where users would contribute cards to update the content. Sections in bold are new sections.
- About ROS
- ROS Branding Information
- ROS Media Contacts
- Contact Information
- Why ROS?
- What is it?
- ROS Architecture
- ROS 1 vs ROS 2
- Core Libraries
- Ecosystem and Collaborators
- ROS 2 Middleware (card based)
- Gazebo / Ignition
- Move It
- ROS Industrial
- TBD ROS-X Groups (card based)
- ROS Community
- Businesses / Start-ups
- Research Groups
- Building A Robot (getting started)
- Download Now
- Community Support (HELP!)
- Education Resources (free and paid classes and tutorials, card based)
- Professional Resources (list of freelancers and groups, card based)
- Robots & Components (card based)
- Get Involved
- Events (Discourse list)
Before we begin the transition process in earnest we wanted to talk to the community about the future of ROS.org. We have the following requests/questions:
- Does this outline look sound?
- Did we miss anything? What would you like to see on ros.org?
- Are there any accessibility needs over and above the existing W3C standards?
We’re also looking for assistance on this project. In particular we need:
- Contractors to help with some of the styling and design work. If you have a candidate please DM me.
- Contributors who would be willing to help with translation or regionalization. Please DM me if you are interested.