Re: Can the documentation for Unison be migrated from the UPenn site?

Greg Troxel <[email protected]> writes:

>> Also, there appears to be no css file to render the html version with the 
>> similar look as the previous html documentation, but that's minor (and 
>> perhaps intentional).  
>
> My take is that unison being on github is a bug not a feature and my
> energy, if any, would go to finding a place to migrate to.  Yes, lots of
> things about github are awkward.  Plus they train proprietary AI on GPL
> code -- which in my view is not ok.

I don't think the lack of css is intentional.  I think it's just that
there is no .css in the sources.  Adding a css file (being careful about
licensing) seems fine, and I'm open to a PR that does that.  I would
like to stick with sources in the repo, and I don't really want to add
build deps like a css generator; I don't know if the old css is hand
written, or something else.

That won't fix the github html rendering issues, but it's progress and
lets the html in a package be rendered better.

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].