Link doc entries to their definition in p5 source code.

[toolness]

One of the hardest things about fixing a minor bug or typo is figuring out where it's located in a project's source code.

But one of the great things about YUIDoc is that it gives us that information in the data.json blob it builds for our reference docs!

So I thought that it might be nice to unintrusively link to the source code for a p5 API in its documentation. I stress the word unintrusively because I don't want to confuse the beginners who may be learning programming for the first time, and could be thrown off by the extra information.

Other benefits of linking to the source:

• It invites users of p5 to become contributors.
• It generally makes it easier to "pop open the hood" and see how p5 works.

Here's what it looks like--the example screenshot below is taken from the documentation for plane():

The first link there is to view the source for plane(), while the second is to edit it (yay to GitHub for providing permalinks to edit files at a specific line number!). My hope is that beginners who don't know anything about git can fix simple typos and issue PRs for them.

Notes:

• Um, I couldn't easily figure out where the CSS for the docs were stored, so I've inlined the CSS for now. It is kind of gross but I should be able to fix it before merging.

[iamjessklein]

👍 I agree this feels like a super humane approach to redirects @toolness

[PaliwalSparsh]

This is simply amazing. 😃

[lmccart]

brilliant, love it. we also have this addition to the footer. i'm going to go ahead and merge both and then you or i can take a crack on styling. the css files are actually located in the p5.js-website repo: https://github.com/processing/p5.js-website/blob/master/css/main.css