[Tf-curation] CMDI Best Practices meeting February

[Twan Goosen]

Hi Pavel,

Thanks for that addition! This may indeed be a useful factor in
comparing the options, albeit not one with a high priority, at least not
for the best practices document. However this comparison may come in
handy in other contexts as well in which this may be more of a concern.

For the record, GitBook allows for customisation through custom CSS and
theme plugins:
<https://help.gitbook.com/content/can-i-customize-design.html>. I have
included this information in the new column.

Best,
Twan

On 19/01/2018 13:31, Pavel Stranak wrote:
> Hi,
> 
>> On 19 Jan 2018, at 11:21, Twan Goosen <twan at clarin.eu> wrote:
>>
>> 2. GitBook alternatives comparison:
>> <https://docs.google.com/spreadsheets/d/1v0FmwYojN4Z_85GbETlIonokXKUXeQJe0tQ-7Rstn2U/edit?usp=sharing>
>>
>> If you are aware of potential alternatives to GitBook, please add them
>> to this sheet. There are some columns to describe the features and
>> conditions for each of the solutions. If you think other information
>> might be useful, feel free to add it.
> 
> I didn't add another option, but another column. I use markdown regularly, but for very different things than Latex. Basically I use markdown when I do not care about typesetting, only about structure. 
> 
> I don’t know GitBooks, so I have no idea about its typesetting mechanism. I know how to do a custom page size, headers, footers, fonts, margins (and margin notes), 2-column text, or typeset math in Latex. I have no idea whether I can do any of that in GitBooks.
> 
> I am not saying it must be a  decisive factor, because things get more complicated when we think about eBooks, just that we should probably consider it.
> 
> 
> Pavel
> 

-- 
Twan Goosen
Software developer at CLARIN ERIC
www.clarin.eu | twan at clarin.eu