User:Benjamin Mako Hill/Dynamic content library plan: Difference between revisions
Jump to navigation
Jump to search
(New page: == Braindump/list of features == === On-laptop verification of library content === We should be able to verify library content bundles automatically and test for the following things: *...) |
No edit summary |
||
| Line 1: | Line 1: | ||
The following is my current braindump and random ideas for features. Feel free to add to them. |
|||
== Braindump/list of features == |
|||
=== On-laptop verification of library content === |
=== On-laptop verification of library content === |
||
Revision as of 23:33, 9 February 2008
The following is my current braindump and random ideas for features. Feel free to add to them.
On-laptop verification of library content
We should be able to verify library content bundles automatically and test for the following things:
- Required/optional fields;
- Correct encodings on index.html and sub-files;
- Look for broken links;
- External links (note these);
This verification library should be able to run in two contexts:
- on a webserver where it can be used a method to test uploaded content bundles and provide verbose output;
- on the laptop where it runs a less resource intensive subset of essential checks and can skip or not include certain bundles in the index;
Other Content Features
- simple index and search
- tag/based browsing of content -- both user-tagged and not
- simple annotation of content library
- simple interface for browsing
Perhaps we want a Share activity that allows users to be able to connect to each other and to share not content but actual activities so that users can download these and put them in their own Journal/Datastore.