One advantage with Dokuwiki is just that it's so easy to transfer - I take all my notes on my localhost (because I also want to be able to use my notes when offline), and then just rsync all the files to the server for public consumption. It's read only, which makes it more safe, but if it ever got hacked (it's php after all), I can just overwrite everything again. Of course, this wouldn't work for a collaborative site (maybe some kind of distributed, git-like system would be appropriate).
Again it all depends on what the purpose is, what kind of workflows are needed etc. And it's always desirable that the data itself can be exported/reused by different tools, UIs etc. Stian On Mon, Dec 14, 2015 at 4:55 PM, Jan T Kim <[email protected]> wrote: > On Mon, Dec 14, 2015 at 03:21:52PM +0000, Greg Wilson wrote: > > We've been talking on and off for a couple of years about a lesson > > on "publishing in the 21st century". Should creating a personal/lab > > website be part of that? > > I have quite some reservations about website as a means of publication. > If the content is mainly human readable text (such as a paper, technical > report or similar), it's better to publish it in that format. If it's > any kind of software, a web UI is quite a nightmare in terms of usability > and reproducibility. Repeating the painful history of web interfaces > to tools such as BLAST (projects like BioPython used to parse content > out of HTML responses, and contributors / maintainers had to track any > changes that made to the presentation tier of the NCBI (or other) BLAST > server) should be avoided as much as possible. > > Another issue to consider is that people will try to "hack into" any > site. > > There are alternatives for provisioning software in a "ready to use" > form. Virtual machine images are a perhaps more classical form that > may be considered somewhat "heavyweight" in terms of effort involved > to create and to run them, while systems such as Docker or Anaconda > are more "lightweight" but may be considered unnecessarily / > undesirably dependent on companies behind them. However, they all > seem substantially preferable to web sites / applications as a way > of publishing scientific software to me. > > Best regards, Jan > > > > Cheers, > > Greg > > > > _______________________________________________ > > Discuss mailing list > > [email protected] > > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org > > -- > +- Jan T. Kim -------------------------------------------------------+ > | email: [email protected] | > | WWW: http://www.jtkim.dreamhosters.com/ | > *-----=< hierarchical systems are for files, not for humans >=-----* > > _______________________________________________ > Discuss mailing list > [email protected] > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org > -- http://reganmian.net/blog -- Random Stuff that Matters
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
