By default, WIP is setting a pull request status to pending if it finds one of the following terms in the pull request titles:

• wip
• work in progress
• 🚧

WIP is a free app.

https://github.com/wip/app
https://wip.vercel.app/stats

I found some broken links on http://mruby.org/docs/api/.

• index(top-left)
• doc/guides/compile.md
• doc/guides/mrbgems.md
• MIT License.
• contribution guidelines

I guess this page is mruby/mruby/README.md.
So, I couldn't come up with good modification. 😢

Some time ago I followed the mentioned tutorial. But the last part (Bytecode (.c)) seems to be a bit confusing for a beginner:

This line: "To execute this bytecode the following boilerplate has to be written:"
I think the most straightforward tip for beginners is to write a file "test_main.c" with this code, and add a include to "test_program". This way, if the generated code is updated everything can be kept. (I was confused as where to add the boilerplate code, and could not get it working together with the array.)

Then the compile command is:

gcc -std=c99 -Imruby/include test_main.c test_program.c -o test_program.o  mruby/build/host/lib/libmruby.a

This makes this example just a bit more specific so an experimenting user only has to follow this tutorial exactly.

I'd like to translate the docs into Chinese,
but I'm not sure if it's a good idea to make PRs here.
:-)

I've put together something to start with and I'm using the logo provided by @h2so5 however it isn't an "official" logo. If there is any objection to this please raise it here. I don't know if @matz needs to bless a logo or not but that would remove any questions.

This is what it looks like:

Now that MRuby has been around for a number of years it's a bit tricky to sort through gems to know what's possibly up-to-date and what's likely abandoned and no longer compatible. Is there any interest in adding a bit of metadata to mgems.yml to make it easier to highlight what's likely maintained and what's likely not?

https://fundamental-code.com/mruby-timeline/ is something I put together with a bit of git log parsing. There are plenty of short lived gems from 2016 and earlier which I'd wager likely have some compatibility issues with how MRuby has evolved over the years.

I think it's time to set up www.mruby.org as CNAME to mruby.github.io. See help page.

https://mruby.org/ still mentions 3.1.0, but 3.2.0 is the latest release.

The last bit of documentation I wrote was approved of and merged by @matz into mruby. Now I want to add the documentation to mruby.org. Usually what would happen is that I'd generate the doc using mruby-yard. In this case, the only thing that changed was that I added docs to string.h. So I'd then take the generated doc in this case a file called mruby_2Fstring.h.html. Then I'd just copy and paste it to the proper directory in mruby.github.io then I'd do a PR. Of course, if it's merged it would then go live. Is that still okay? Because I remember before @zzak said that the size was too big. I want to make sure I do this correctly this time!

Setup a free plan for open source.

AccessLint brings automated web accessibility testing into your development workflow. When a pull request is opened, AccessLint reviews the changes and comments with any new accessibility issues, giving you quick, timely, and targeted feedback, before code goes live.

AccessLint helps you keep on target with digital accessibility by giving specific, ongoing accessibility feedback to your team. It can catch simple errors that might break your website for your customers with disabilities.

Accessibility guidelines defined in WCAG 2.0 help us build applications that work better for more people. They also give us a rough measure of compliance with legal requirements outlined in the ADA and Section 508. AccessLint runs a growing list of WCAG 2.0 tests, e.g. missing alt attributes that make pages more opaque for screenreader users, positive tabindex values that can create confusion for keyboard users, invalid ARIA, and unlabelled fields.

https://github.com/marketplace/accesslint

Looks strange when you mouse over the links.

Bootstrap 4 is a major rewrite of the entire project.
There are breaking changes when upgrading from Bootstrap 3 to 4 as detailed here:

https://getbootstrap.com/docs/4.0/migration/

We can just snapshot a reduced numbers of pages or only the core pages like the home page and the pages in the menu.

That would be 6 pages to start. When you run out of free monthly snapshots it just stops for the rest of the month.

5,000 free screenshots a month we can just snapshot at one browser width, so only one snapshot per page.

It works on pull requests and there are various ways to use it including on Circle CI.

Percy does pixel perfect diffs or visual regression testing.

https://docs.percy.io/docs
https://percy.io/pricing

Latest news on http://mruby.org/ is 1.3.0 released despite 1.4.1 being already out. That seems a bit confusing. Probably would be good idea to write at least short notice saying Hey, 1.4.1 is out. so it looks more up to date. Having What’s new in mruby 1.4.{0,1} would be nice too but I'm not qualified to write that...

I will be working on some of the list of issues from the current master from the Lighthouse report attached.

I have already started with PR #84

Google Lighthouse is an open-source, automated tool for measuring the quality of web pages. It can be run against any web page, public or requiring authentication. Google Lighthouse audits performance, accessibility and search engine optimization of web pages.

https://developers.google.com/web/tools/lighthouse

mruby-site-lighthouse.pdf

I'm currently maintaining CI for mgem-list and mruby in:
https://103.128.221.202.static.iijgio.jp/jenkins/

We want it be like https://mruby.org

Found an icon tester:

https://realfavicongenerator.net/favicon_checker?protocol=https&site=mruby.org

Looks like we are doing fine on Chrome and iOS Safari.
But on Windows 8 and 10, Mac OS Safari and classic desktop browsers we need to fix 9 issues.

refs #86
refs #84
refs #82
refs #85

Lighthouse also checks for the existence of a mask icon.

https://web.dev/maskable-icon/
https://web.dev/maskable-icon-audit/
https://maskable.app/editor

I think showcasing exisiting projects implemented with mruby on mruby.org will help spread the various use cases that can be used with mruby and raise its popularity and adoption.

Eg.

1. RubyOnWheelchair
2. mruby-cli
3. mruby-engine

Thoughts?

https://jsonfeed.org/

JSON Feed is a Web feed file format for Web syndication in JSON instead of XML as used by RSS and Atom.

A range of software libraries and web frameworks support content syndication via JSON Feed. Supporting clients include NetNewsWire, NewsBlur, and Reeder. Notable publishers include NPR.

Templates for rendering JSON feeds for your Jekyll blog -> https://github.com/snaptortoise/jekyll-json-feeds

https://github.com/vallieres/jekyll-json-feed
https://github.com/jguadagno/jekyll-json-feed
https://github.com/lildude/jekyll-json-feed
https://github.com/tedchoward/tidbits/blob/master/feed.json
https://ndarville.com/blog/2017/05/19/json-feed-for-jekyll/

refs #95
refs #94

https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps

refs #85

On one of my GitHub Pages sites it looks like this:

Relax while Imgbot optimizes your images.
Don’t spend another second worrying about compressing your images. Install Imgbot into your GitHub projects, and focus on your application.

Lossless compression is a class of data compression algorithms that allows the original data to be perfectly reconstructed from the compressed data. By contrast, lossy compression permits reconstruction only of an approximation of the original data, though usually with greatly improved compression rates. Lossless data compression is used in many applications. For example, it is used in the ZIP file format and in the GNU tool gzip.

https://imgbot.net/
https://en.wikipedia.org/wiki/Lossless_compression

I think we should copy mrbgem infomation on mruby wiki to libraries on mruby.github.io for now.

How do you think? If you agree, I'll send pull-request.

The url http://mruby.org does not point to a server, but a quick add of an A record to 192.30.252.153 and 192.30.252.154 would point it to GitHub's servers. For more information: https://help.github.com/articles/setting-up-a-custom-domain-with-pages#apex-domains

It seems like mruby.org is running inside a frame, but I don't know enough about how the template is generated to be able to fix it. I think it's generated using yard-mruby.

For example:

1. Go to mruby.org/
2. Click any link.
3. The address bar still says mruby.org

I think we should avoid using frames if possible.

/cc @sagmor @Mav7

Maybe helpful and interesting articles like @bovi's Five ways to execute mruby should be updated and added to the website?

I would help with that or do it on my own unless @bovi doesn't want it or people disagree with this idea.

Hi,

I wonder how we should manage the content of the website. Over at www.ruby-lang.org we are using Jekyll for it and it worked quite well for the site due to its heavy content for different languages. I guess we don't need to support the same amount of languages like ruby-lang, so Jekyll might be overkill. Any thoughts?