I would like to suggest that we move the blogofile docs from the blogofile.com repo [1] to the blogofile core repo [2]. I guess this is mostly a matter of personal preference for me. I think that having them in the same repo as the code will help them to stay in sync with the code. It allows changes to code and related docs changes to be in the same commit, when appropriate. It will also make for a cleaner release process, and easier integration into a service like travis-ci.org if we want to do that down the road.
In conjunction with changing the repo location, I would also like to put the docs on readthedocs.org. We can take advantage of their multi-version feature to keep the 0.7 docs available while the 0.8 docs evolve. Ryan, if you have access to the CNAME record in your DNS for blogofile.com the docs can be hosted on readthedocs.org but continue to appear as they do now within blogofile.com [3].
On Wed, May 30, 2012 at 6:07 PM, Mike Pirnat <mpir...@gmail.com> wrote:
> +1 on both points. +even more on the docs-with-code point if bonus
> rounds of voting are allowed. :-)
> Sorry I am not offering much beyond cheerleading and pom-pom waving,
> but I want to make sure you know there's support for these ideas.
> --
> You received this message because you are subscribed to the Google Groups
> "blogofile-discuss" group.
> To post to this group, send email to blogofile-discuss@googlegroups.com.
> To unsubscribe from this group, send email to
> blogofile-discuss+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/blogofile-discuss?hl=en.
On Wed, May 30, 2012 at 3:07 PM, Mike Pirnat <mpir...@gmail.com> wrote:
> +1 on both points. +even more on the docs-with-code point if bonus
> rounds of voting are allowed. :-)
> Sorry I am not offering much beyond cheerleading and pom-pom waving,
> but I want to make sure you know there's support for these ideas.
The +1s are welcome, Mike. Helps me confirm that I'm making sense.
As for other stuff... your time will come... bwahahahaha! :-)
A CNAME record pointed at blogofile.readthedocs.org should now resolve to the latest update of the docs. I'm not sure how you want to integrate that into blogofile.com/documentation - perhaps a redirect to docs.blogofile.com with that subdomain named in the CNAME record?
I've also noticed that the github commits sidebar on the blogofile.com site isn't showing the recent commits I pushed to put the 0.7.1 docs in master. If you know why and can resolve that easily, Ryan, I'd appreciate it. Even better would be if that sidebar could reflect the plugins branch (at least until it is merged) so that current dev activity is evident.
> A CNAME record pointed at blogofile.readthedocs.org should now resolve to
> the latest update of the docs. I'm not sure how you want to integrate that
> into blogofile.com/documentation - perhaps a redirect to
> docs.blogofile.com with that subdomain named in the CNAME record?
> I've also noticed that the github commits sidebar on the blogofile.comsite isn't showing the recent commits I pushed to put the 0.7.1 docs in
> master. If you know why and can resolve that easily, Ryan, I'd appreciate
> it. Even better would be if that sidebar could reflect the plugins branch
> (at least until it is merged) so that current dev activity is evident.
> To post to this group, send email to blogofile-discuss@googlegroups.com.
> To unsubscribe from this group, send email to
> blogofile-discuss+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/blogofile-discuss?hl=en.
