[tempestn]

Another approach is to make it backward compatible with something else. For example, if you wanted to make a new site/network similar to StackExchange (but presumably with some revolutionary changes; not just a "me too" copy), you could start by adding an interface layer using the StackExchange API and adding some of your new smarts to give your users some of the benefit of your tool, on top of the StackExchange content. Most likely you wouldn't be able to add all the new goodness there though, so you would also do as other comments have suggested to build up your own content. Maybe even incentivize users to add stuff based on StackExchange answers they find (assuming some manual intervention is necessary to make the answers suitable for your site - and also assuming you comply with terms of use and such).

It's hard to give exact examples without knowing what you plan to do of course, but that's the general idea. Make it backwards compatible with whatever the closest thing is out there already, so that even in cases where you don't have any of your own content to return for a user, you at least have something. Then do everything you can to ramp up your own content asap.

[balor123]

Does that work in most cases? Most communities don't provide APIs. A few will provide RSS feeds - not clear if you can legally reuse them like that?

[greenjello]

StackOverflow, Wikipedia, and other creative commons sites provide good starting data sets because all you need to do is attribute to them. No expensive licensing things, or anything like that.

Often you can write a pretty good bot using their data, and emulate user interactions. Enough users won't notice the site is run by bots that it's better than nothing if you don't have funding :-)