A few additions:
1. Squarespace is another hosted CMS for creating websites. It is somewhat similar to Wordpress, but has a good bit more flexibility in my experience, including the ability to embed lots of things (e.g. Interactive datasets, etc.). 2. Many universities run a centralized CMS that may not be as fully outfitted as other systems, but can offer the luxury (?) of look and feel that is consistent with your institution’s websites, technical support, university branding, and low cost for use (if not free). 3. If your institution has an institutional repository, you might consider trying to interface there when listing publications – they are going to provide persistent links to the publications and may have other services to give you an auto updated bibliography. 4. Greg – I would be very interested to see a “publishing in the 21st century” module, though I suspect that could very quickly blow up into an entire course. If you are still looking for feedback, ideas, or support for that module, I’d be happy to help. steve <><><><><><><><><><><><><><><><><><><><><><> Steve Van Tuyl Digital Repository Librarian Oregon State University Libraries & Press web | http://osulibrary.oregonstate.edu/staff/vantuyls orcid | http://orcid.org/0000-0002-8752-272X email | [email protected] phone | 541.737.3492 On 12/14/15, 7:17 AM, "C. Titus Brown" <[email protected]<mailto:[email protected]>> wrote: Also, highly suggest making sure there are links to auto-updating sites such as Google Scholar or ImpactStory so that information doesn't need to be maintained constantly. best, --titus On Mon, Dec 14, 2015 at 10:10:19AM -0500, Brendan Smithyman wrote: Hi Keith, Research websites usually end up hosted on a department computer, and usually only support basic server-side web technologies (i.e., they probably just send files to the web browser when asked, without much fancy extra processing). If users are Unix-savvy, they can probably upload using scp or rsync, but new users might find something like 'filezilla' to be more useful, with a graphical interface. Or, if the server has git installed, they can just store the site in a git repository and clone it on the web server. In terms of creating content, users could learn to use a 'static site generator', which takes a lot of the pain out of the process and allows users to write in markdown, for example. Well-known examples would be Jekyll, Hyde, or Hugo. I'm partial to mkdocs, but it's more targeted for generating software documentation. Teaching good practices for web design from scratch is more than a quick workshop, so I'd focus on presenting a few useful tools, and the info needed to find others and/or more extensive training. Hope this helps! Cheers, Brendan ??? Brendan Smithyman Postdoctoral Fellow Western University, Earth Sciences Biological & Geological Sciences, Rm. 1045 London, ON, Canada N6A 5B7 c. 778.990.5957 On Dec 14, 2015 9:40 AM, "Ma, Keith Frederick" <[email protected]<mailto:[email protected]>> wrote: > > Hi everyone, > > A group of graduate students here at Boston Univ. contacted me for help > planning and running a workshop on making research websites. The vision is to > provide an overview of some popular tools and what they are capable of, > followed by some time for the students to start working on their own websites > with the instructors and each other to help. This is still in the early > planning stages, with a tentative date in late February. > > I don't have much (any) experience in making websites, and am unfamiliar with > the associated software and hosting services. Can anyone provide some advice > about what we should include? Does anyone have experience running a similar > workshop? > > Many thanks, > Keith Ma > ?? > > _______________________________________________ Discuss mailing list [email protected]<mailto:[email protected]> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org -- C. Titus Brown, [email protected]<mailto:[email protected]> _______________________________________________ Discuss mailing list [email protected]<mailto:[email protected]> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
