Luke Lee

Right, I don't think we should clutter the UI for history purposes. However, the margin notes feature stays out of the way unless you hover over it so that seemed...

Good point. Looks like it's an issue. Lets make sure to test this on our new markdown rendering when it's ready. I'll post back when that happens, hopefully this week.

Can you test this on the site now? We deployed our markdown rendering fixes today so hopefully this takes care of it. Thanks!

Good idea. We're already using github web hooks for [several things](https://github.com/pluralsight/guides-cms/blob/master/pskb_website/webhooks.py) including cache invalidation. So, it shouldn't be too hard to use the existing `push_event` endpoint to handle something like...

Another idea would be to try using a code review tool for this feedback between editors and authors. I recently came across the [Omniref](https://www.omniref.com) tool, which is a new approach...

Adding a commit message box to the create/edit guide process has some other benefits: 1. Provides useful information in the github repository - Currently all the commit messages are very...

The endpoint could live at a URL like, `/api/list-guides/` and require one extra argument for the `stack`. The return would be a JSON data structure with a list of guide...

We currently have all _almost_ all of this information in the redis hearts database and the details.json file in the github repository. The only thing we're lacking is a guide...

Something else we probably want to provide in the API is the ability to search on tags. This way API users could further filter their guide searches. The ability to...

Any additional thoughts on adding or not adding an API @paulocheque @edroman @prtkgpt ?