Why don't we redesign our website and docs rubyonrails.org like laravel.com

[Agus Syahputra]

Ruby on Rails is the father of the MVC framework used by many web developers.

But the design of the main website rubyonrails.org is getting old.

Can we redesign our website so it looks more modern and to structure the docs so it's more simple and easier to read?

[Kasper Hansen]

I prefer the more differentiated look of the current design to laravel’s corporate-ish blandness. So don’t think we’ll be stepping away from that.

Now as for the docs, we’re happy to help review/merge PRs from volunteers with concrete suggestions for readability improvements 👍

--

Kasper

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-core/57555db3-e7b2-425d-8448-97ec726ec1bf%40googlegroups.com.

[Xavier Noria]

The current design is from 2016 https://weblog.rubyonrails.org/2016/1/19/new-rails-identity/.

[Agus Syahputra]

Yeah, maybe we need a volunteer designer for this.

I don't know, I just want that rubyonrails.org need cool/modern new look. Maybe like https://reactjs.org

And also for the docs, maybe we have to re-structure the menus so it's easier to navigate the guides. Make it simpler like https://reactjs.org or git books.

And also for the guides, I think the guides are too many words, maybe we can make it shorter.

[Agus Syahputra]

Sorry I can not edit my previous message. This is the git books link: https://docs.gitbook.com as the sample of the structure of the menu. I just think the menu is easier to be used.

[Xavier Noria]

On Wed, Oct 30, 2019 at 1:18 PM Agus Syahputra <agus.p...@gmail.com> wrote:

I don't know, I just want that rubyonrails.org need cool/modern new look. Maybe like https://reactjs.org

The website looks modern to us, an old design would something more like this.

And also for the docs, maybe we have to re-structure the menus so it's easier to navigate the guides. Make it simpler like https://reactjs.org or git books.

A matter of opinion too. We have a guides selector, and a sidebar for sections. I mean, you can always polish and iterate things, and perhaps you personally would prefer another navigation UI, but the current layout is fine for us.

And also for the guides, I think the guides are too many words, maybe we can make it shorter.

No way, we need more words :).

 

[Diego Toral]

I agree and think guides need some love.

I think Rails guides is confusing, specially for newcomers. I remember struggling to understand it on my first days of Rails. Ideally, the guides should be easy to use and friendly to newcomers, searchable (I currently use google) and show the Rails version somewhere.

On 30 Oct 2019 09:29 -0300, Agus Syahputra <agus.p...@gmail.com>, wrote:

Sorry I can not edit my previous message. This is the git books link: https://docs.gitbook.com as the sample of the structure of the menu. I just think the menu is easier to be used.

--

You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-core/3ae52b3a-5137-4b03-b1db-004d045208b7%40googlegroups.com.

[Xavier Noria]

On Fri, Nov 1, 2019 at 1:52 PM Diego Toral <diego...@gmail.com> wrote:

I think Rails guides is confusing, specially for newcomers. I remember struggling to understand it on my first days of Rails.

Can you elaborate? What was difficult to understand for you?

 

searchable

Patches welcome. Constraints are:

    1) The website is static.

    2) Open source search engine.

Furthermore, if the solution is provided by a company, no logos or advertisements of any kind.

[Colin Ross]

I think it might also be important to note that the guides don't intend to be exhaustive reference or a cookbook, but a high level guide to what the framework provides for customization and where to look next.

The version is the current stable version as a default with previous versions still available via the path, eg https://guides.rubyonrails.org/v4.2/

On Friday, November 1, 2019 at 5:52:52 AM UTC-7, Diego Toral wrote:

I agree and think guides need some love.

I think Rails guides is confusing, specially for newcomers. I remember struggling to understand it on my first days of Rails. Ideally, the guides should be easy to use and friendly to newcomers, searchable (I currently use google) and show the Rails version somewhere.

On 30 Oct 2019 09:29 -0300, Agus Syahputra <agus....@gmail.com>, wrote:

Sorry I can not edit my previous message. This is the git books link: https://docs.gitbook.com as the sample of the structure of the menu. I just think the menu is easier to be used.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rubyonra...@googlegroups.com.

[Agus Syahputra]

For the guides, now we have two menus. 

- The first one is the drop-down on the top. Which is the menu to navigate between pages.

- The second one is the chapters menu. Which is the menu to navigate between title inside a page.

We have to make those sticky, so it will be easier to navigate.

The condition now, the menu is not sticky and not working well when displayed on the mobile screen. Making it hard to navigate the guides.

If you can see what I mean, please see this https://doorkeeper.gitbook.io/guides/. 

(Please Try to view the doorkeeper guides on mobile)

The doorkeeper guides use gitbook and it did pretty well jobs to make the menu sticky and also good on mobile screen.

 

The first image shows the chapters (contents) menu. The second image show the pages menu. 

[Agus Syahputra]

I try to make the chapters menu sticky.

I will push the code when finished.

You can view what I mean on this gif: https://media.giphy.com/media/H6tgCqFmim06GwZEt7/source.gif