See also:
Mises.org TODO list
This list is for anything that comes to mind, no matter how improbable.
-
Translate Mises.org into other languages.
-
Automatically transcribe and index all audio/video content on Mises.org
-
Created an open-source project for the Mises.org CMS
-
Create an open source control repository for Mises.org
-
Set up a Mises.org bittorent server
-
Setup an Austrian Economics progress metric to track growth of mises.org community and web traffic
-
Book/media rental subscription service (like Netflix)
-
At least for books that are freely downloadable, for those that would rather pay a little money to read a hard copy rather than read it on a computer screen, but don't want to, or can't afford to, buy the book
-
Organize the supporting arguments of Austrian economics as a directed graph or network (some nodes representing propositions that are either premises or conclusions of arguments) and the arcs connecting the nodes on the computer screen representing things like a logical supporting relationship. One could then browse through the logic of Austrian economics in a graph (network) format.
-
create mobile version of mises.org like m.mises.org
-
Have RSS/ATOM feeds for the Mises.org media content split up by year (or quarter) first released. My rationale is that for those of us who want the whole firehose of media content, having a time organized split will make it easier to manage as the past time feeds will never change.
-
Gradually move Mises.org, in part or in full, to an open-source .NET CMS platform. Lots of things could be done better code-wise, and lots of it has already been done in existing platforms. Looking at the back-end domain model, N2 CMS (http://www.n2cms.com/) might be very useful.
-
Pros: Deferring development of core CMS functionality to a third-party product leaves more dev time for other things. Functionality which does not exist yet, might be implemented in an existing CMS.
-
Cons: Adapting the codebase might take some time. (It could probably be done step-by-step though. Refactoring the Blog and Daily sections would probably be very fast. Literature and Media sections would take some more analysis and backend development.)
-
Move IRC channel to server that allows web clients other than its own (a.k.a. leave freenode for not allowing completely free access)
-
Put more media collections on Itunes U. Make media collections easier to find on the site.