While I agree we should try to avoid typos in our codebase.
Fixing typos It is a very easy and low barrier way to get new contributors, and
I think this kind of contribution is very welcome, so I’d prefer to not
discourage or even remove the possibility of people to submit typo PRs.
Maybe, some
Hi friends, in case it's relevant, i've recently built a source-code
focused spell checker in ruby https://github.com/robotdana/spellr designed
to be part of CI pipelines
On Tuesday, October 29, 2019 at 6:03:27 PM UTC+11, Masafumi Okura wrote:
>
> Hi Richard,
>
> I understand your concern. I'm n
The current design is from 2016
https://weblog.rubyonrails.org/2016/1/19/new-rails-identity/.
--
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-
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
> On 2
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?
--
You received this message b
Hi Richard,
I understand your concern. I'm not really familiar with spell checking on
technical documents, so I'd like to stop this discussion here. If I get
more familiar with how to introduce informational spell checker, I'll come
to give a proposal again.
On Monday, October 28, 2019 at 3:43
