Documentation of performance and accessibility guide

[Tlazypanda]

Please describe the desired behavior.
Currently all the new changes introduced during Outreachy are not documented making it difficult for future contributors to maintain and improve on performance and accessibility.

Adding a performance and accessibility guide can help solve this problem by providing contributors links to changes made and offer tips on things to keep in mind while opening new pull requests.

[Tlazypanda]

Hey @jywarren as per our discussion on various issues that some sort of notes is required to keep track of changes maybe we can link this to the readme - https://hackmd.io/@itm2017004/BJuqtap6L initial draft ✌️

[Tlazypanda]

Hey @jywarren @cesswairimu @ebarry I am almost done with this can you please have a look? Thanks ✌️

[ebarry]

Yes, have it open now, will be reading during today! thank you @Tlazypanda for being part of the documentation revolution!

[ebarry]

Hi @Tlazypanda , it's so great to read documentation like this. Thank you!
Are any parts of this documentation aimed at non-coders, such as the people using the website directly? I was wondering this because of sections like https://hackmd.io/@itm2017004/BJuqtap6L#Avoiding-suspicious-link-text and the advice to avoid underlining.

[Tlazypanda]

Hey @ebarry I am not sure how links are rendered by the editor now but yes these can be used as general guidelines as well to make posts more accessible 😅 Originally this was meant for developers only but maybe we can extend it ✌️

[Tlazypanda]

Updated docs with some more added points 😅 suggestions and feedback welcome on what else to add ✌️

[cesswairimu]

Hey @Tlazypanda how are you doing? Did you want to move the documentation to the PL website or maybe make a markdown for it on the repo. Whats do you think? Thanks