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

First pass of integrating Sculpin as a blog engine [DO NOT MERGE] #88

Closed
wants to merge 1 commit into from

Conversation

dragonmantank
Copy link
Member

This is to add blog functionality of #22, and is still a work in progress.

Adding this in changed a bit of things and still needs some cleanup, but pushing this up so that (if nothing else) this doesn't get lost, and others can start to look over it.

Sculpin is now used to generate any static pages, as well as markdown-based content like blog posts. Any file that isn't generated by Sculpin will then fall back to index.php and the existing Silex infrastructure and run like normal. Both Sculpin and Silex share the same layout and view files so that everything stays in sync.

As a word of note, this does add an extra step for setup as mentioned in the README. The public/ directory is now generated by Sculpin and no longer stored in version control, so any changes to public/index.php or assets like JS or CSS will need to have the rebuild command run to push changes to the public/ directory.

As a consequence of upgrading packages to satisfy dependencies for Sculpin, this also takes care of #85.

@dragonmantank
Copy link
Member Author

Closing this. While this did end up showing some deficiencies in the current code base (all of which I entered issues for), I think there is a better solution to this.

@dragonmantank dragonmantank deleted the feature/blog branch November 7, 2016 20:30
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

Successfully merging this pull request may close these issues.

1 participant