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

Splitting the blog directory (again) #10

Open
citrusui opened this issue Feb 12, 2017 · 0 comments
Open

Splitting the blog directory (again) #10

citrusui opened this issue Feb 12, 2017 · 0 comments

Comments

@citrusui
Copy link
Owner

Porting the blog directory back to a submodule has a few advantages and disadvantages:

Note: core repo refers to https://github.com/citrusui/me, and blog refers to https://github.com/citrusui/blog.

Advantages

  • Slightly faster git clone's
  • Focused development. The core repo and blog have different goals: The former incorporates most of the functionality, and the latter provides detailed information in Markdown. Opening a pull request or issue would hopefully be directed to the core repo or the blog repo.
  • Different design choices. Files directly pertaining to blog would no longer be cluttering up the core repo, and vice-versa.

Disadvantages

  • Heavy reliance on _includes and _layouts. Should blog have duplicates of these folders in its own repo, or be strictly Markdown files? Would it make sense to be able to jekyll serve the standalone blog repo?
  • More tests. One without the inclusion of blog, and one with blog to make sure all goes well.
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

1 participant