Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tachyons via cdn? #14

Open
ghost opened this issue Jan 8, 2017 · 3 comments
Open

Tachyons via cdn? #14

ghost opened this issue Jan 8, 2017 · 3 comments

Comments

@ghost
Copy link

ghost commented Jan 8, 2017

hey, thanks @joshosbrn for making this and sharing with the whole wide world!!

it's pretty super great.

just curious, why'd you opt to include Tachyons via cdn and not npm?

thanks!

@joshosbrn
Copy link
Owner

Hi there, @jchck! The original decision to go CDN instead of NPM was to save time, and honestly I wasn't as familiar with NPM when I built Jekyons. I believe @alexcarpenter made the Tachyons version number a variable in a PR a few months ago and that's felt right so far.

All of that to say, I'm definitely not opposed to moving to NPM. IMO the big drawback (obviously, I think) to using CDN for this is the inability to work offline. It looks like you have some commits on your fork; I'd love to check out a PR & discuss there as a group whenever you're ready!

Thanks! 👒

@ghost
Copy link
Author

ghost commented Jan 9, 2017

Ah, makes sense.

Cool, I'll clean up what I have a submit PR.

@alexcarpenter
Copy link
Contributor

@jchck @joshosbrn Yeah, from what I understand, Jekyons is a prototyping tool (not to say you cannot use if for production sites). Being able to get up and running quickly meant relying on the CDN version. Easy to maintain and no compiling needed. Just my two cents.

@ghost ghost mentioned this issue Jan 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants