Josh,
I just ran a test on 1000 children of a single item. It didn't go off without a hitch. The view renders fine and all pages where accessible for edit, delete, etc... The only issue I currently see is that drag & drop re-ordering of the pages fails. I don't see any reason why the error I'm getting can't be avoided so I am creating an issue in Git Hub so hopefully we can clear up this hurdle and you can develop your project on BigTree. If you want I can keep you posted when the issue is resolved.

Curt

I think it could be labeled better. If you want to take a stab at it, or contribute in other ways follow the instructions on gitgub in the the readme.md file: https://github.com/bigtreecms/BigTree-CMS

Here is a summary of the instructions.

1. Fork it.

2. Create a branch (git checkout -b 4.0_philp_branch)

3. Commit your changes (git commit -am "labeled unused fields drop down menu")

4. Push to the branch (git push origin 4.0_philp_branch)

5. Create an [Issue][1] with a link to your branch

Thanks!
Curt

I think BigTree will excel at managing the type of system you described. It sounds to me like you would want to run the core "tumblr-like" content off of a single module. You could design the module entries a couple of different ways.

The easier to code, but harder to maintain method would be to make simple blog-like module entries that have a single HTML content field and handle the media through html embeds.

The more elegant method would be to design a module that has a separate field for each media type. There are built in field types to handle news (html text), image galleries (photo gallery), quotes (text and text areas) and the ones that don't exist would be easy to make (read about custom field types at the bottom of this article). For video I would probably just store a youtube or vimeo ID in a textfield and then do the heavy lifting of constructing the embed in the template code. This method would normalize the input and allow you to sort and categorize based on the existence of content types rather than having to manually categorize the post based on the content it contains.

Regardless of which method you use for the module, you will probably want to power the front end with a single routed template. With a routed template you can construct routes based on post categories, post titles etc... to serve the results of various queries without being tied to a physical page tree structure.
I would definitely poke around the example site, it makes use of techniques you will find useful like routed templates, generating url slugs for module entries, etc.

I hope you find this response helpful, as always if you get stuck or we are missing something in the documentation ask away.