-
-
Notifications
You must be signed in to change notification settings - Fork 376
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
How to use MiniBlog #237
Comments
Yep, that's pretty much how it would work. This way would also allow you to first pull in changes from other repo's and test it before publishing to your blog. |
Also, is this intended to be a "real" project or a bit of a technology sampler? Would be nice to add more themes, Disqus comment support, Google Analytics etc - pull requests ok? |
Yes, it's a real project. There are tons of people who use Miniblog as their blog engine. |
But then Mads just rejected my GA and copyright patch 'cos it's not Core - which means that the features will never improve and I have to develop everything I want myself |
Adding Disqus and GA takes seconds, why just add that bloat to the core project? Just develop your own theme and use that instead. I have a fork with my own theme. |
Ok, that might be the way to go - covers off the core layout issues such as the GA tag etc |
I've seen several forks with both GA and Disqus support. There is even one with some pretty advanced features for adding your own commenting system with ease. Browse the forks and you just might find what you are looking for :) |
That's what I've been doing :-) |
Sorry to be dumb, but what's the best way to consume the source., this is my idea at the moment...
Then on "publish" I have my custom configuration changes and posts and I push that branch to azure.
On "dev" I can do code development and then merge to publish or to master if I want to issue a pull-request.
The text was updated successfully, but these errors were encountered: