- <h1>A site about stuff</h1>
- <table border="1" width="100%">
- <tr>
- <td width="50%">
- <h2>Welcome</h2>
- Main site content goes here.
- </td>
- <td width="50%">
- <h2>News</h2>
- <div id="mkwsRecords" autosearch="dinosaur" sort="title:1"
- targets="connect.indexdata.com:9000/plos_api"><i>News items will appear here</i></div>
- </td>
- </tr>
- </table>
+ <script type="text/javascript">
+ jQuery.pazpar2({ "layout":"popup", width: 800, height: 500 } );
+ </script>
+
+ <pre>
+ An embryonic MasterKey Widget Set
+=================================
+
+This directory contains an embryonic MasterKey Widget Set, based
+initially on "jsdemo" though now far removed from those beginnnings.
+
+
+How this works
+--------------
+
+The goal is to make it that as much of the searching functionality as
+possible is hosted on
+ http://mkws.indexdata.com/
+so that very simple websites such as
+ http://example.indexdata.com/
+can have MasterKey searching with minimal effort.
+
+The following files must be hosted on mkws.indexdata.com:
+ mkws.js
+ mkws.css
+ /pazpar2/js/pz2.js (*)
+
+The following files make up the application:
+ index.html
+ favicon.ico [optional]
+ robots.txt [optional]
+
+(At present, the client application's configuruation also needs an
+Alias for /service-proxy/, to avoid cross-site scripting issues. We
+will fix this.)
+
+(*) if you don't have already installed pazpar2 on the machine, you can
+do it by installing a debian package or check it out from GIT:
+$ git clone ssh://git.indexdata.com:222/home/git/pub/pazpar2
+
+Configuring a client
+--------------------
+
+The application's HTML must contains the following elements as well as
+whatever makes up the application itself:
+
+[...]
+ </pre>
+ <script src="//code.jquery.com/ui/1.10.3/jquery-ui.min.js"></script>