The only other option I can think of is to create a gh-pages branch in the
avogadro git repo, as these automatically get rendered and served on
github. That being said, I think your approach is better.
The web dev aspect should be pretty straightforward. Jekyll takes markdown
files and runs them t
> I turned on wiki and issues for the repo if that helps. The GitHub wikis are
> backed by git, and have editing facilities built in
As I said before, I think we should consider separating developer-oriented docs
and user-centric docs. The MediaWiki lumped them together.
My proposal is to split
I turned on wiki and issues for the repo if that helps. The GitHub
wikis are backed by git, and have editing facilities built in, so that
might be the easiest (I haven't used the GitHub wikis much, but
willing to give it a try).
Marcus
On Fri, Oct 17, 2014 at 1:47 PM, Patrick Fuller wrote:
> To
To reiterate what Ian said, I think that pandoc + maybe a shell script will
get you most of the way there. If you have the XML, you can try (untested):
pandoc -f mediawiki -t markdown file.xml
(f is “from”, t is “to) I also just tried parsing a URL directly and it’s
not bad. This works decently w
OK, a first pass is here:
https://github.com/AvogadroChem/AvogadroChem.github.io
e.g.
https://github.com/AvogadroChem/AvogadroChem.github.io/blob/master/features.md
This includes all the images I could grab, although I'm sure there are errors.
It's not a functioning site yet, but if someone has
> It's worth noting that if you want to keep the wiki functionality but
> move it into GitHub,
Indeed, I think this would be a nice way to separate out *developer*
documentation and user documentation. The *dev* documentation can be put into
the GitHub repository wiki.
> Also, if you can get th
On Thu, Oct 16, 2014 at 4:33 PM, Geoffrey Hutchison wrote:
> Hi everyone,
>
> Despite the low level of action, I’ve been spending a lot of time *thinking*
> about Avogadro and the future. There are quite a few exciting things,
> although it may take a while before they fully appear.
>
> One thing
It's worth noting that if you want to keep the wiki functionality but
move it into GitHub, you can also clone the repo wiki and alter it
that way:
git clone https://github.com/user/reponame.wiki.git
Also, if you can get the Mediawiki markup out of the XML, you can
convert that to GitHub-flavoure
