Although we want to include similar features mainly in the Editor feature [core], it is probably easier if the Media support is presented as a separate feature to make it clearer in the documentation.
The editor should be capable to make use of the HTML 5 extension and allow video and audio directly in a website. However, this may not always be a good option for you in case you do not want (do not have) to offer the type of bandwidth that such requires you to have to provide videos and sound tracks directly on your websites.
The HTML canvas will be used to offer the Image Editor feature [core].
The editor will allow for uploading and fully defining a flash animation object tag without the need for end users to know anything about the technicalities.
We should also support linking to a flash animation on antoher server. In this case, we want to make sure that file remains available.
The editor will allow for specifying a video URL and generate the necessary HTML to get the video to play (or not play) in the page as if the user was on YouTube.
The video identifier should be enough to get to add it to your website. Making it as easy as possible (i.e. the id as in v=<id>).
YouTube also has an API so we could look into offering more such as browsing your history or finding out whether a video was removed under the feet of the user. If possible, we should even allow for videos to be uploaded from the client's website directly to YouTube.
The editor will allow for specifying a soundtrack URL and generate the necessary HTML to get the sound to play (or not play) in the page as if the user was on SoundCloud.
The track identifier should be enough to get to add it to your website. Making it as easy as possible.
SoundCloud has a REST API which can be used to also list all the favorites, manage tracks in an account, and users.
Snap! Websites
An Open Source CMS System in C++
