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

Documentation questions to answer! #27

Closed
zachleat opened this issue Jan 6, 2018 · 1 comment
Closed

Documentation questions to answer! #27

zachleat opened this issue Jan 6, 2018 · 1 comment
Assignees

Comments

@zachleat
Copy link
Member

zachleat commented Jan 6, 2018

https://twitter.com/verlok/status/949536166075920384
https://twitter.com/etportis/status/943505488355803136

@zachleat zachleat added this to the Next Release (version TBD) milestone Jan 10, 2018
@zachleat zachleat self-assigned this Jan 10, 2018
@zachleat zachleat modified the milestones: v0.2.6, Next Release (version TBD) Jan 12, 2018
@zachleat
Copy link
Member Author

Planning on a full Jekyll migration guide in #68.

The short answers are:

Should we use 11ty instead of Jekyll?

Yes

What are the benefits?

https://www.zachleat.com/web/introducing-eleventy/

Do we need to change the repo file structure?

No! https://github.com/zachleat/zachleat.com/tree/master/web is an example of this. Most of the work is done in the .eleventy.js config file.

Will Github pages drop Jekyll in favor of 11ty?

Probably not since they are a Ruby shop afaik, but I’ll have a tutorial on how to autodeploy to GitHub soon. Netlify is easier, though. https://github.com/11ty/eleventy-base-blog does this.

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

No branches or pull requests

1 participant