profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/milmazz/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

milmazz/bupe 67

BUPE is a Elixir ePub generator and parser (supports EPUB v3)

milmazz/elixir_getting_started_guide_to_go 18

Elixir Getting Started Guide (EPUB format)

milmazz/a11ybot 3

Retweet messages with especified hashtag or search terms to twitter

milmazz/eisula 3

Proyecto Escuela de Ingeniería de Sistemas ULA

milmazz/elixir-style-refcard 3

Elixir Style reference card

milmazz/aaron 2

CommonMark parser

milmazz/django-election-monitor 2

Election Monitor

ian-bateman/phauxth 1

Authentication library for Phoenix, and other Plug-based, web applications

milmazz/elixir-in-action-book 1

Exercises, answers and tips from my reading journey through the book "Elixir in Action" by Saša Jurić

GetThru/bamboo 0

Testable, composable, and adapter based Elixir email library for devs that love piping.

PR opened phoenixframework/phoenix

guides: update 'Controllers' guide

This PR includes the following changes:

  • Replace put_layout/2 with put_root_layout/2 in the Assigning Layouts section, so, that way the sample works as expected.
  • Update the code examples to match Phoenix v1.6.0
  • Reduce the verbosity in some links, instead we use the autolink feature from ExDoc (See: https://github.com/elixir-lang/ex_doc/#auto-linking)
  • Sorted the link references at the end of the document
+34 -27

0 comment

1 changed file

pr created time in 14 hours

push eventmilmazz/phoenix

Milton Mazzarri

commit sha 0ca6ede5f2f9b3f60fdf2104e52e710559f445d0

guides: update 'Controllers' guide This commit includes the following changes: * Replace `put_layout/2` with `put_root_layout/2` in the _Assigning Layouts_ section, so, that way the sample works as expected. * Update the code examples to match Phoenix v1.6.0 * Reduce the verbosity in some links, instead we use the _autolink_ feature from ExDoc (See: https://github.com/elixir-lang/ex_doc/#auto-linking) * Sorted the link references at the end of the document

view details

push time in 14 hours

create barnchmilmazz/phoenix

branch : guides/controllers

created branch time in 15 hours

PR opened phoenixframework/phoenix

guides: update the Routing docs

This PR includes the following changes:

  • Update the :browser pipeline to v1.6.0 (replace fetch_flash with fetch_live_flash, and the addition of put_root_layout)
  • Describe the new plugs in the browser pipeline section
  • Add a few changes for conciseness
+33 -25

0 comment

1 changed file

pr created time in 16 hours

create barnchmilmazz/phoenix

branch : guides/routing

created branch time in 17 hours

delete branch milmazz/phoenix

delete branch : guides/directory-structure

delete time in a day

delete branch milmazz/phoenix

delete branch : guides/request_lifecycle

delete time in a day

delete branch milmazz/phoenix

delete branch : guides/plug

delete time in a day

push eventmilmazz/phoenix

Milton Mazzarri

commit sha 9acdd9f380e00c3e2e0acadd78d8e6e19d737356

guides: 'Directory structure' page review

view details

push time in 4 days

Pull request review commentphoenixframework/phoenix

guides: update Plug page

 defmodule HelloWeb.Endpoint do  The default endpoint plugs do quite a lot of work. Here they are in order: -- [Plug.Static](https://hexdocs.pm/plug/Plug.Static.html) - serves static assets. Since this plug comes before the logger, serving of static assets is not logged+- `Plug.Static` - serves static assets. Since this plug comes before the logger, serving of static assets is not logged -- [Phoenix.CodeReloader](https://hexdocs.pm/phoenix/Phoenix.CodeReloader.html) - a plug that enables code reloading for all entries in the web directory. It is configured directly in the Phoenix application

REVIEWER: I deleted this line here because this Plug it's already included in the list right after "In the middle of the endpoint, there is also a conditional block:", which seems a more appropriate place for this Plug.

milmazz

comment created time in 4 days

PullRequestReviewEvent

PR opened phoenixframework/phoenix

guides: update Plug page

This PR includes:

  • updates the default endpoint plugs based on the output of mix phx.new hello (v1.6.0), the main addition is the description of Phoenix.LiveDashboard.RequestLogger
  • I also replaced some links like [Module](https://hexdocs.pm/project/module.html and took advantage of the links that ExDoc creates when it founds modules enclosed by backticks :)
  • Now the pipeline :browser reflects the output from mix phx.new hello
  • Finally, fixed a missed link to Plug.Conn.assign/3, you can find the link at the bottom of the text as references.
+12 -10

0 comment

1 changed file

pr created time in 4 days

create barnchmilmazz/phoenix

branch : guides/plug

created branch time in 4 days

PR opened phoenixframework/phoenix

guides: update 'request life-cycle' page

This PR updates the pipeline structure in HelloWeb.Router based on the mix phx.new hello output using v1.6.0.

This PR also removes the (ab)use of the simply word on the same page. I would suggest avoiding saying that things "are easy" or that they're not challenging, everyone learns at its own pace, and that's fine. See https://justsimply.dev/ for more examples.

+8 -6

0 comment

1 changed file

pr created time in 4 days

create barnchmilmazz/phoenix

branch : guides/request_lifecycle

created branch time in 4 days

PR opened phoenixframework/phoenix

guides: 'Directory structure' page review

This PR updates the "Directory structure" page based on the output from mix phx.new hello (1.6.0). It also adds a summary of the new Hello.Mailer module.

+28 -16

0 comment

1 changed file

pr created time in 4 days

create barnchmilmazz/phoenix

branch : guides/directory-structure

created branch time in 4 days

Pull request review commentphoenixframework/phoenix

Introduction guides review

-# Introduction

Should I update the file path from guides/channels/channels.md to be something like guides/real-time/channels.md? Just to follow the pattern described in the sidebar.

milmazz

comment created time in 4 days

PullRequestReviewEvent
PullRequestReviewEvent

PR opened phoenixframework/phoenix

Introduction guides review

This PR fixes a few things in the "Introduction" guides:

  • Add the Authentication item to the Overview page to match the listed sections in the sidebar

image

  • Replace the Channels group section with Real-Time, to match the Overview list description.

image

  • Replace the "Introduction" title to be "Channels", which is located under the "Real-Time" section

image

  • Remove the un-existent output Webpack is watching the files from the "Up and Running" page.
+4 -5

0 comment

4 changed files

pr created time in 4 days

push eventmilmazz/phoenix

Milton Mazzarri

commit sha 8ed8f00f812690febc896dc50bdd5c3a2bb64ef5

Update Channels title page

view details

push time in 4 days

create barnchmilmazz/phoenix

branch : introduction-guides

created branch time in 4 days

fork milmazz/phoenix

Peace of mind from prototype to production

https://www.phoenixframework.org

fork in 4 days

startedsasa1977/demo_system

started time in 11 days

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentelixirschool/elixirschool

new blog post about Rocket Validator

+---+author: Jaime Iniesta+author_link: https://github.com/jaimeiniesta+categories: general+date: 2021-09-02+layout: post+title: "Validating Accessibility and HTML with Rocket Validator"+excerpt: >+Learn how we're checking and monitoring the new Elixir School site to detect and fix accessibility and HTML issues using Rocket Validator.+---++## Intro++One of the core principles of Elixir School is to be an inclusive community. We want to help people from all over the world learn to code using Elixir. To facilitate that, we provide translations of the lessons to many languages, maintained by volunteers worldwide. By removing the language barrier, we're helping more people get into the Elixir community.++Apart from the language barrier, there are other barriers that we're aware of - [web accessibility barriers](https://www.w3.org/WAI/people-use-web/abilities-barriers/) are everywhere on the World Wide Web, making it harder for people to access content that is often taken for granted.++Low vision may make a web page unreadable if the text has low contrast or the font size cannot be adapted easily. Unsighted people can use screen readers to hear the page content, but it won't work well if the content is poorly structured and can't be properly interpreted by the screen reader software. People with reduced mobility may prefer to navigate through the lessons using the keyboard instead of the mouse, but again this won't work if the document is not laid out correctly.++The good news is that we can make Elixir School accessible for everyone. And it's not a hard task, it just requires that we're aware of those barriers and that we follow the web standards to provide well-structured web pages.++## How to find accessibility and HTML issues++The World Wide Web Consortium (W3C) is an international community that defines and develops [Web standards](https://www.w3.org/standards/), HTML being probably the most used -and abused- of those standards. At the end of 1997, the [W3C launched](https://www.webdesignmuseum.org/web-design-history/w3c-html-validator-1997) the [W3C HTML Validator](https://validator.w3.org/), a service to check any web page and find issues in its HTML structure. More than two decades later this service is still around and in good health and many tools have been built around its [open source validator](https://github.com/validator/validator).++HTML is the basis of web pages, but still a perfectly valid HTML page can have accessibility issues. For example, a web page may have a bad combination of colors that results in low contrast: a light color text over a light background may lead to unreadable text by people with low vision. If a video has no captions, deaf users won't understand what it's talking about. Sections of the document may be not accessible for users that don't employ a mouse to move through the document. Zooming and scaling may be disabled, making it impossible for the users to enlarge the web page to see it better. Many known issues are easily detected using automated accessibility checkers like [axe-core](https://github.com/dequelabs/axe-core).
HTML is the basis of web pages, but a perfectly valid HTML page can still have accessibility issues. For example, a web page may have a bad combination of colors that results in low contrast: a light color text over a light background may lead to unreadable text by people with low vision. If a video has no captions, deaf users won't understand what it's talking about it. Sections of the document may not be accessible for users that don't employ a mouse to move through the document. Zooming and scaling may be disabled, making it impossible for the users to enlarge the web page to see it better. Many known issues are easily detected using automated accessibility checkers like [axe-core](https://github.com/dequelabs/axe-core).
jaimeiniesta

comment created time in a month

Pull request review commentelixirschool/elixirschool

new blog post about Rocket Validator

+---+author: Jaime Iniesta+author_link: https://github.com/jaimeiniesta+categories: general+date: 2021-09-02+layout: post+title: "Validating Accessibility and HTML with Rocket Validator"+excerpt: >+Learn how we're checking and monitoring the new Elixir School site to detect and fix accessibility and HTML issues using Rocket Validator.+---++## Intro++One of the core principles of Elixir School is to be an inclusive community. We want to help people from all over the world learn to code using Elixir. To facilitate that, we provide translations of the lessons to many languages, maintained by volunteers worldwide. By removing the language barrier, we're helping more people get into the Elixir community.++Apart from the language barrier, there are other barriers that we're aware of - [web accessibility barriers](https://www.w3.org/WAI/people-use-web/abilities-barriers/) are everywhere on the World Wide Web, making it harder for people to access content that is often taken for granted.++Low vision may make a web page unreadable if the text has low contrast or the font size cannot be adapted easily. Unsighted people can use screen readers to hear the page content, but it won't work well if the content is poorly structured and can't be properly interpreted by the screen reader software. People with reduced mobility may prefer to navigate through the lessons using the keyboard instead of the mouse, but again this won't work if the document is not laid out correctly.++The good news is that we can make Elixir School accessible for everyone. And it's not a hard task, it just requires that we're aware of those barriers and that we follow the web standards to provide well-structured web pages.++## How to find accessibility and HTML issues++The World Wide Web Consortium (W3C) is an international community that defines and develops [Web standards](https://www.w3.org/standards/), HTML being probably the most used -and abused- of those standards. At the end of 1997, the [W3C launched](https://www.webdesignmuseum.org/web-design-history/w3c-html-validator-1997) the [W3C HTML Validator](https://validator.w3.org/), a service to check any web page and find issues in its HTML structure. More than two decades later this service is still around and in good health and many tools have been built around its [open source validator](https://github.com/validator/validator).++HTML is the basis of web pages, but still a perfectly valid HTML page can have accessibility issues. For example, a web page may have a bad combination of colors that results in low contrast: a light color text over a light background may lead to unreadable text by people with low vision. If a video has no captions, deaf users won't understand what it's talking about. Sections of the document may be not accessible for users that don't employ a mouse to move through the document. Zooming and scaling may be disabled, making it impossible for the users to enlarge the web page to see it better. Many known issues are easily detected using automated accessibility checkers like [axe-core](https://github.com/dequelabs/axe-core).++## The power of automated site validation++So, it's great that we have tools that help in detecting issues on web pages. Both the W3C HTML validator and axe-core are open source and can be incorporated into our web development flow. But, there's an important limitation: they can only check one URL at a time. When you have a small website with just a few web pages, it might be an option to do manual checks using these tools. But, what can we do with a large site like Elixir School? According to the latest reports, Elixir School has more than 1,000 web pages. If we want to check them all with the W3C Validator and axe-core, we would need to run 2,000 manual checks!++## 🚀 Rocket Validator to the rescue!++[Rocket Validator](https://rocketvalidator.com) is an online service that performs site-wide validation of large websites. It's basically an automated web crawler that will find the internal web pages of a site and validate each web page found using the W3C Validator and axe-core, producing detailed reports on the issues found, within seconds.++This service, also powered by Elixir, Phoenix, LiveView and Oban, is a subscription-based service for web agencies and freelance developers. But, it's free for open source projects like [Elixir School](https://github.com/elixirschool/school_house/pulls?q=is%3Apr+label%3A%22rocket+validator%22+is%3Aclosed) and [Docusaurus](https://github.com/facebook/docusaurus/pulls?q=is%3Apr+rocket+validator)! We're using Rocket Validator to run reports on the new Elixir School and to monitor the site via weekly-scheduled and deploy-triggered validations.++## Running a site validation report++To run a site-wide validation report, we just need to enter a starting URL. This is usually the front page of the site we're going to validate, but it can be any internal URL, or an XML or TXT sitemap containing the web pages to validate. Rocket Validator will visit this initial URL and discover the internal web pages, adding them to the report.++![Rocket Validator new site validation report](https://www.dropbox.com/s/amt7ilhw3b0sdh2/rocket-validator-new-report.png?raw=1)++We can also define the validation speed as a rate limit of requests per second and define the options:++* **Check HTML**. Will run the W3C HTML Validator on each page found.+* **Check Accessibility**. Will run axe-core on each page found.+* **Deep Crawl**. Will find more web pages on the site by following recursively the internal links found.++Once we click on **Start Validation**, results will appear within seconds as the web pages are validated. We can browse the Summary Report to see a global overview including the most important issues (so you know what to fix first), as well as reports that group the common issues on the site and detailed reports per each web page.++![Rocket Validator summary report](https://www.dropbox.com/s/z611nr8ofpikawx/rocket-validator-summary-report.png?raw=1)++## Sharing reports++Any site validation report generated by Rocket Validator can easily be shared, just by pasting its URL. This lets us reference any section of the report in Github issues, so we can work together on fixing them.
Any site validation report generated by Rocket Validator can easily be shared just by pasting its URL. This lets us reference any section of the report in Github issues, so we can work together on fixing them.
jaimeiniesta

comment created time in a month

Pull request review commentelixirschool/elixirschool

new blog post about Rocket Validator

+---+author: Jaime Iniesta+author_link: https://github.com/jaimeiniesta+categories: general+date: 2021-09-02+layout: post+title: "Validating Accessibility and HTML with Rocket Validator"+excerpt: >+Learn how we're checking and monitoring the new Elixir School site to detect and fix accessibility and HTML issues using Rocket Validator.+---++## Intro++One of the core principles of Elixir School is to be an inclusive community. We want to help people from all over the world learn to code using Elixir. To facilitate that, we provide translations of the lessons to many languages, maintained by volunteers worldwide. By removing the language barrier, we're helping more people get into the Elixir community.++Apart from the language barrier, there are other barriers that we're aware of - [web accessibility barriers](https://www.w3.org/WAI/people-use-web/abilities-barriers/) are everywhere on the World Wide Web, making it harder for people to access content that is often taken for granted.++Low vision may make a web page unreadable if the text has low contrast or the font size cannot be adapted easily. Unsighted people can use screen readers to hear the page content, but it won't work well if the content is poorly structured and can't be properly interpreted by the screen reader software. People with reduced mobility may prefer to navigate through the lessons using the keyboard instead of the mouse, but again this won't work if the document is not laid out correctly.++The good news is that we can make Elixir School accessible for everyone. And it's not a hard task, it just requires that we're aware of those barriers and that we follow the web standards to provide well-structured web pages.++## How to find accessibility and HTML issues++The World Wide Web Consortium (W3C) is an international community that defines and develops [Web standards](https://www.w3.org/standards/), HTML being probably the most used -and abused- of those standards. At the end of 1997, the [W3C launched](https://www.webdesignmuseum.org/web-design-history/w3c-html-validator-1997) the [W3C HTML Validator](https://validator.w3.org/), a service to check any web page and find issues in its HTML structure. More than two decades later this service is still around and in good health and many tools have been built around its [open source validator](https://github.com/validator/validator).++HTML is the basis of web pages, but still a perfectly valid HTML page can have accessibility issues. For example, a web page may have a bad combination of colors that results in low contrast: a light color text over a light background may lead to unreadable text by people with low vision. If a video has no captions, deaf users won't understand what it's talking about. Sections of the document may be not accessible for users that don't employ a mouse to move through the document. Zooming and scaling may be disabled, making it impossible for the users to enlarge the web page to see it better. Many known issues are easily detected using automated accessibility checkers like [axe-core](https://github.com/dequelabs/axe-core).++## The power of automated site validation++So, it's great that we have tools that help in detecting issues on web pages. Both the W3C HTML validator and axe-core are open source and can be incorporated into our web development flow. But, there's an important limitation: they can only check one URL at a time. When you have a small website with just a few web pages, it might be an option to do manual checks using these tools. But, what can we do with a large site like Elixir School? According to the latest reports, Elixir School has more than 1,000 web pages. If we want to check them all with the W3C Validator and axe-core, we would need to run 2,000 manual checks!++## 🚀 Rocket Validator to the rescue!++[Rocket Validator](https://rocketvalidator.com) is an online service that performs site-wide validation of large websites. It's basically an automated web crawler that will find the internal web pages of a site and validate each web page found using the W3C Validator and axe-core, producing detailed reports on the issues found, within seconds.
[Rocket Validator](https://rocketvalidator.com) is an online service that performs site-wide validation of large websites. It's an automated web crawler that will find the internal web pages of a site and validate each web page found using the W3C Validator and axe-core, producing detailed reports on the issues found, within seconds.
jaimeiniesta

comment created time in a month