Simpler Website Tech: Leaving the PHP Island

Image: Images from Wikimedia Commons, combining Nihoa, Northwestern Hawaiian Islands and Lempisaari, Naantali, Finland. CC A and CC BY.

Cite as:



Citation format: The Chicago Manual of Style, 17th Edition

Jackson, Daniel. ‘Simpler Website Tech: Leaving the PHP Island’, 2020.

Part of a new GenR series for 2020 ‘Open Science Pro Tip’ where Open Science researchers share their digital know-how.

Researcher and developer Daniel Jackson shares his experiences of using flat file web technologies that can take the headaches out of running a research website by reducing maintenance tasks, lowering costs, avoid security headaches, and helping with archiving and keeping a site online long-term. The article covers a number of research site examples from running a personal site, for a research project, or archiving a site at the end of a project. Flat file approaches came about because of the long-standing security vulnerability of websites built on PHP/MySQL which continually run the risk of opening up a whole web server computer to being hijacked. The solution to this ‘vulnerability’ problem is quite simple, remove the machine from the equation, just serve HTML/CSS and any other assets needed — hence the name ‘flat file’ sites. 

Read More

Make Your Code Citable Using GitHub and Zenodo: A How-to Guide

This how-to guide is designed for researchers who want to create and re-use GitHub-based repositories in academic literature.

Open Science MOOC

The following guide has been made by the Open Science MOOC as part of preparation work on its first module release ‘Open Research Software and Open Source‘. The Open Science MOOC is made by an international volunteer group of over a hundred contributors, which you are free to join.

Gen R is a partner contributor to Open Science MOOC and over time as our editorial paths cross we will look to make a variety of contributions to the MOOC as a free and open learning resource for all.

Software Citation

It’s hard to overstate how important it is to have a record of what software has been produced, and also how little has been done in the past to create such indexes and catalogs of software. It’s like no one cataloged books for the last half-century and only now retrospectively took up the task.

Read More