Hierarchy inside out

I think it would be better to invert the hierarchy:
1x_ios--------------->| action
1x_web                  | alert
2x_ios                    | av
2x_web                  | communication
3x_ios                    | content
drawable_hdpi       | device
drawable_mdpi      | editor
drawable_xdpi       | file
drawable_xxdpi      | hardware
drawable_xxxdpi    | image
svg                         | maps
LICENSE                | navigation
README.md          | notification
browser.json           | social
index.html               | sprites
package.json          | toggle

It occurred to me when, I was finding a way to just download all the svg icons.

Start by inspecting the repository tree and the listed paths, including the icon directories, README.md, browser.json, index.html, and package.json. Compare the current layout with the proposed action/alert/category hierarchy; done means the repository structure consistently follows the requested organization.

Written by the indexing model from the issue text.