# Project Status The library is at a stage in which the major functionality of the H5P editor and player are working. You can check in the lists below, what is already implemented and what isn't. ## Finished functionality * [x] store and serve libraries / content types * [x] store and serve content * [x] create, read, update and delete operations on content * [x] manage file uploads (= images, video etc.) in temporary files * [x] decoupling of storage through interfaces * [x] provide AJAX endpoints for the editor and player * [x] backend communication with the H5P Hub * [x] register the site * [x] send usage statistics * [x] get information about content types on the hub * [x] download and install new content types / updates of content types on user request * [x] validation of packages (structural integrity and conformity of content and libraries) * [x] offers downloads for h5p packages ("exporting" content) * [x] support for copy & paste in the editor * [x] support for editor interface languages other than English * [x] addons (required to display mathematical formulas) * [x] MongoDB and S3 storage implementation for content and temporary files * [x] library administration endpoint and React UI component * [x] check permissions of users (install libraries, download h5p package, embed h5p package, create restricted, update libraries, install recommended, copy h5p?) * [x] MongoDB and S3 storage implementation for libraries * [x] Redis cache for caching * [x] catch and relay xAPI statements * [x] alter library files, semantics (allows site admins to change libraries without hacking the actual files; very useful) (published soon) * [x] filter html to prevent cross-site-scripting (XSS) vulnerabilities. * [x] add csrf tokens to AJAX POST requests * [x] storing user state in the player (for continuing later where the user left off) ## Unfinished functionality * [ ] validation of content against full library semantics (currently only text is validated) * [ ] logging & statistics generation: e.g. use of libraries by author, view of embedded content etc. (see h5p-php-library:h5p-event-base.class.php for a list of events) * [ ] provide embed route for content \[embed links can be generated but no route yet] * [ ] bundle and cache assets (aggregates all css and js files into two big files to decrease http requests; done in h5p-php-library:h5p-default-storage.class.php->cacheAssets(...)) * [ ] logging and statistics (there is a debug logger, but not one that allows you to log domain events) * [ ] mass content updates (possibly funded in the future) * [ ] option to disable H5P Hub * [ ] performance optimizations --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.lumi.education/development/status.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.