![]() ![]() Have a look at the product release blog post. The heavy lifting on this feature was done by and I drew pretty pictures and provided the UI work, and helped build proof of concept prototypes. Text manipulations, links and media, lists, and less-used GitHub-flavored Markdown features are all properly grouped. We also ended up grouping functions by similar tasks. Since we didn’t want this feature to feel intrusive, this made things a lot lighter. While iterating, we stripped the button treatment on the toolbar. The toolbar shows powerful features while making it easier for beginners to use GitHub. Task lists, for example, are a really powerful project management tool that very few users knew about. Instead of hiding Markdown functionality behind a help link, we put our powerful, but less-used features up front in a toolbar. Ultimately, we ended up building a single toolbar for our GitHub Flavored Markdown without modifying either of the tabs. This is a popular pattern and turns up in lots of Markdown-based editors like iA Writer. Italics, for example, could be rendered inline while still showing the Markdown syntax. This could allow for less toggling between the “Write” and “Preview” mode. I then wanted to try to add light styling to the “Write” tab. This being the very first issue I’d posted to github/github, it was wisely suggested that I scale back the scope of modifying our site-wide comment box. ![]() This style of editing was popularized by Wordpress. We’d remember that preference and allow for folks to ignore the Visual editor entirely. If this wasn’t desired, users could always flip tabs to see their raw Markdown. Our visual editor would render Markdown on the fly, allowing full use of the toolbar for formatting text. I would call these tabs “Visual” and “Markdown”. Instead of frequently switching to the “Preview” tab, I wanted to build an editor that would render Markdown on the fly. The comment area is plain text in the “Write” tab, but when switching over to "Preview", it shows the final rendered output. I first considered revamping the existing “Write” and “Preview” pane. Prior to joining, we only had a link to a help document explaining the syntax. This seemed like a decent opportunity to add a lightweight toolbar to surface some of these. Unfortunately, a great wealth of useful features were hidden behind this syntax. Markdown is a syntax that allows folks to make richer comments-adding things like links, lists, and images. Issue triage and project management are often equally as important as the code itself, especially as an organization grows.Īll of the comment fields throughout GitHub support GitHub-flavored Markdown. Increasingly, GitHub is used by non-programmers and programmers alike. In early conversations with GitHub, I’d shared my desire to help simplify some of their core experiences. This is a collection of the work that I was able to help ship during my time as a Hubber™. I had the opportunity to work full-time as a remote Product Designer at GitHub from March 2015 to October 2016. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |