search

pydy / pydy-tutorial-human-standing

PyDy tutorial materials for MASB 2014, PYCON 2014, and SciPy 2014/2015.
http://pydy.org
160 stars 71 forks source link

Update content on PyDy.org #8

Closed moorepants closed 10 years ago

moorepants commented 10 years ago

We need a little polishing on the website. Would be nice to have a general cleanup. We will share the url to all potential users.

gilbertgede commented 10 years ago

Well, I added an update for PyCon 2014. I think there are some tools to go from DokuWiki (that's the one we use, right?) to markdown.

If there are no objections though, under our pydy user, I might make the pydy.github.io repository and start moving content over?

moorepants commented 10 years ago

After all that work to get the site live again! :)

No, that sounds good to me. I think having a sphinx/jekyll/(or your favorite static site generator) hosted as a git repo is a better long term solutions. Github even has the git based wiki's built in that can be used. All of that data can be moved from github via git if it ever fails.

We should point pydy.org to the new site as soon as it has enough content.

I'm +1 for that.

gilbertgede commented 10 years ago

I started looking into jekyll, which is more blog focused. That raises the question - should the new pydy.org be more "blog-like", i.e. each example or announcement is a new post, which can then be indexed according to category? Or do we want to keep the wiki look & feel that we have now? Sphinx might be better if we want to retain that. Thoughts?

moorepants commented 10 years ago

We can just use Sphinx since we are all familiar with it. My dissertation, for example, is a Sphinx site hosted on Github.

I use Hyde for my personal website and you can make pages or blog posts. I assumed that Jekyll would allow you to do either or.

gilbertgede commented 10 years ago

Jekyll does, but it doesn't seem as "clean" as I would expect. From what I understood of the documentation, if something is not a post (going in the _post directory), it has to be in the top-level directory.

I'll start trying out Sphinx.

moorepants commented 10 years ago

I have some scripts here in my sphinx makefile that help handle a gh-pages branch on the same repo as the source:

https://github.com/moorepants/dissertation/blob/master/Makefile

May be helpful.

Another option is to have two repos, one for the source and one for the content produced by the source.

gilbertgede commented 10 years ago

OK, I have put a few of the wiki pages in a Sphinx-built page here: http://pydy.github.io/ It's set up so that we (the developers) work in the dev/ directory, and everything is pushed up to the main directory. For an org page, I believe everything has to be in the main folder of the master branch (different than for project pages). Let me know what you think about how it's starting to look.

moorepants commented 10 years ago

The website is as updated as it is probably gonna get. Closing.