One could consider splitting Runoregi into two parts:
- back-end: just an interface to the database; presents documents equivalent to Runoregi views in JSON format
- front-end: written only in HTML/CSS/JavaScript, accepts JSON data as input (e.g. by sending AJAX requests)
Maybe this could have some advantages as opposed to the current way:
- it would be easier to redesign the user interface, put own branding, combine Runoregi's functionality with other elements
- faster page loading? some views with a large amount of data (e.g. verse view with neighboring clusters, search results) could be loaded asynchronously or using pagination
One could consider splitting Runoregi into two parts:
Maybe this could have some advantages as opposed to the current way: