Re: [w3c/permissions] Convert to Bikeshed (#75)

All of these points are valid. I'm ok with the switch, but please try to keep the document source organized (I.e., tidy'd in some way). BikeShed's use of semantic like breaks makes it really hard to review changes and move stuff around the document. 

Sent from my iPhone

> On 10 Apr 2016, at 2:11 AM, Jeffrey Yasskin <notifications@github.com> wrote:
> 
> Both linking directions are more difficult than necessary with ReSpec: to link out, you need the Dependencies section and following a link takes two clicks. Even when Shepherd doesn't include the other spec to make the out-link automatic, the extra links you need are easier to write (49c5804#diff-ec9cfa5f3f35ec1f84feb2e59686c34dR25), and folks are adding that kind of thing to Shepherd fairly quickly right now.
> 
> To let other specs link in, you have to manually add all the dfn bits that Shepherd expects in order to let the other specs auto-link, and that can be extra-tricky for IDL things. It'd be possible to teach ReSpec to include this stuff, but Bikeshed's already there.
> 
> ReSpec also causes a FOUC that breaks reloads while you're iterating on a section. Try visiting https://w3c.github.io/permissions/#status-of-a-permission and pressing 'reload': you won't be looking at the right section anymore.
> 
> ReSpec also doesn't have any significant benefits anymore: the ability to save and then reload without an intermediate build step is provided by bikeshed watch.
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> 


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/pull/75#issuecomment-208004235