download in homepage

[ibolmo]

Missing download link in homepage. Maybe default to core?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5759166-download-in-homepage?utm_campaign=plugin&utm_content=tracker%2F130405&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F130405&utm_medium=issues&utm_source=github).

[SergioCrisostomo]

@pietrogregorini would it be ok to add one more button in the top menu for this? (it would be just a shortcut to the core/builder) page eventually. I am most afraid the menu will overlap the logo in the break-point to mobile layout.

[pietrogregorini]

This issue requires some brainstorming, IMO.

1. It would be useful to add a navigation menu on top for mobile version (i.e. drop-down).
2. Download should be in the main menu before Blog.
3. Download link in the menu should take the user to a new Download page, where he can download the complete version of Core and More (yes, both) or get instruction to get the libraries on Google JavaScript Library, I think. In the same page, for both products, there will be a call-to-action link to Builder.
4. Builder should remain inside respective product, as a sort of advanced-user tool, I guess.

About menu overlapping logo in mobile layout, we can modify break-points or reduce Menu texts when device become less wide in horizontal.

[ibolmo]

Referencing your list: (1) I wonder if that's an issue. E.g. if I'm on mobile why would I need to download? (2) and (3) Would you be opposed to doing an overview to core and more under the intro text and OS License? something like:

MooTools Packages
 [       Core                  ] [           More            ]
   Classy mootools ... (intro text)     Even more class ... (intro text)
      Download                   Download
     Documentation          Documentation
     Learn More                Learn more

(4) I don't think builder needs to be in the homepage. So I'd agree they would be in their respective folders.

[pietrogregorini]

1 > Actually no need to download, but you may need to get access to Core, More, Blog, etc. instead to go through the whole homepage.

2/3 > That could be a solution, but the homepage must be redesigned a bit. As I said before, that homepage was designed to be used for Prime & friends, now the brief has completely changed so, even if could be a good design, it doesn't mean it fits perfectly the new needs. I will think about something new. In the meanwhile, do you plan to add even some demo? Again, I'd need some plus about framework to add in the about part, to make it more catchy.

4 > We agree about that, perfect.

[ibolmo]

Been thinking about it some more, and I'm really split on whether we should focus on this right now. In a way a download link would seem important but I think at this point we're more interested in teaching folks about MooTools.

I was reviewing the examples we have, and they're great. But they're static. I started to create JSFiddles with the examples, and I realized that it's also premature. Instead, I'd like to provide @pietrogregorini with some demos/examples that we'd like to showcase at the front of the page. These would be short-concise HTML/CSS/JS examples that we could do with as a slideshow with link to JSFiddle for people to play with. These would be 2-3 at first, and at least one from Core and another from More. Each example would include learn more links to each project.

@pietrogregorini @SergioCrisostomo @arian if the above sounds good. I can move this to 1.2 and I'd like to provide the team my suggestions on practical examples/demos. @pietrogregorini would that (and the above) be enough to help with the homepage design?

Cheers,

---

Just noticed this is related to #123.