Spec 3.0 was about existing pre-4.0 features (the current status quo). Thats 
the reason I want to release it asap, so we can work on 4.0 describing all 4.0 
features.

Am 20.01.2014 um 10:53 schrieb Jérôme LELEU <[email protected]>:

> Hi,
> 
> Could this Groovy script be integrated somehow in the process? I'm always 
> doutbful when it comes to manual operations: it's so easy to forget.
> 
> Two more comments about documentation:
> - I've tried to use jekyll on Windows and after a fierce struggle, I gave up 
> on using it (whereas it works perfectly on my Ubuntu station)
> - reading again the spec, I didn't find any mention of the front SLO: was it 
> meant on purpose?
> 
> Thanks.
> Best regards,
> Jérôme
> 
> 
> 
> 2014/1/18 Misagh Moayyed <[email protected]>
> JIRA tracking documentation tasks:
> https://issues.jasig.org/browse/CAS-1417
> 
> Misagh
> 
> 
> From: "Misagh Moayyed" <[email protected]>
> To: [email protected]
> Sent: Friday, January 17, 2014 1:53:06 PM
> Subject: Re: [cas-dev] CAS 4.0 Documentation
> 
> I realized the pages dont automatically generate anchor tags for section 
> headers, like the wiki. This is useful for TOCs to provide direct links to a 
> section. 
> 
> Rather than doing this manually, I put together a small groovy script that 
> auto-generates these tags:
> https://github.com/mmoayyed/markdown-anchors
> 
> There are a few quirks to be worked out wrt to unicode characters, but in 
> general, works great. 
> 
> Misagh
> 
> 
> From: "Robert Oschwald" <[email protected]>
> To: [email protected]
> Sent: Friday, January 17, 2014 8:55:10 AM
> Subject: Re: [cas-dev] CAS 4.0 Documentation
> 
> This anchors are used by Pandoc to generate the TOC in the final Spec PDF.
> 
> 
> 
> 
> 
> Am 17.01.2014 um 16:49 schrieb Jérôme LELEU <[email protected]>:
> 
> Hi,
> 
> I'm currently seeing a lot of anchors in the markdown files. For example:
> <a name="AuthenticationManager">  </a>
> ######`AuthenticationManager`
> 
> Is it normal? What's the use of this anchor in addition to the title below?
> 
> Thanks.
> Best regards,
> Jérôme
> 
> 
> 
> 2014/1/15 Misagh Moayyed <[email protected]>
> Fair point, the new coloring is pretty difficult on the eye. I am no CSS 
> expert, but I will see if I can just pull in the relevant CSS classes for 
> alerts. That should restore the theme to be not as much screamish :)
> 
> Misagh
> 
> 
> -- 
> You are currently subscribed to [email protected] as: 
> [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
> 
>  -- 
> You are currently subscribed to [email protected] as: 
> [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
> 
>  -- 
> You are currently subscribed to [email protected] as: [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
> 
> -- 
> You are currently subscribed to [email protected] as: 
> [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev


-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-dev

Reply via email to