Skip to content
This repository was archived by the owner on Jul 8, 2021. It is now read-only.

Provenance of included JavaScript and CSS #49

Open
sophokles73 opened this issue Nov 21, 2016 · 4 comments
Open

Provenance of included JavaScript and CSS #49

sophokles73 opened this issue Nov 21, 2016 · 4 comments

Comments

@sophokles73
Copy link

Hi,

I really like your theme and I would like to use it for the Eclipse Hono project's website. However, in order to do so, the Eclipse folks will need to do a provenance check on the artifacts included in the theme before letting me put it into our source repo.

I have tried to figure out where the CSS and JavaScript files originate from. The only one I could clearly identify was the modernizr.js file, all others lack a header indicating who the author is and under what license we would be able to use it :-(

Can you shed some light on this?

@digitalcraftsman
Copy link
Owner

Hello @sophokles73,

thank you for considering this theme for your project's website. This theme is a port of the original Material theme written for Mkdocs.

I just pulled the final assets from the upstream project because I don't have the need to add lot's of customizations. You can find the original stylesheets here which are written in Sass. The linked repo contains the compile steps for the pre-processor as well.

all others lack a header indicating who the author is and under what license we would be able to use it

The author of all stylesheets and scripts is Martin Donath (@squidfunk). This port and the original are both licensed under the MIT license.

Feel free to ask any questions if something is not clear 😉

@sophokles73
Copy link
Author

Thanks for the info. That will help a lot in going through the process :-)
One more thing, would you be willing to create a tag on the current repo so that I can refer to a particular version of the theme when submitting it for review to Eclipse?

@digitalcraftsman
Copy link
Owner

This is possible. I already planned this for the future because the original project got a complete overhaul that I would like to port as well. In combination with new features of Hugo (e.g. i18n support) it would be necessary to use tags because the introduced changes will likely not be backwards compatible.

Please let me now if you decide to use this theme for your project's website. It's always great to a theme in the wild.

@digitalcraftsman
Copy link
Owner

digitalcraftsman commented Nov 22, 2016

I created a tag called v0.1 for the latest commit of this theme.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants