This is a big caveat about explicitly "seeding" this site by anticipating what people will likely ask. It might sound like a good idea by the suggestion, but you simply do not need that here!
If someone has a question, they will ask it as part of a genuine need. It will include the specifics of their exact problem, and it will become an organic part of the site.
Not to over-state the case too much, but overt seeding of a site (i.e. anticipating what users would likely ask) almost ruined the recently-launched Cognitive Science site (We have too many unanswered questions). Cognitive Science fell to a 49% answer rate when users started seeding the site.
I wrote about the problems of "seeding" extensively in
Asking the First Questions
…but a few key points are most poignant.
I was a bit put off by the context implied by “seeding the site.” The word seeding suggests to me that we’re coming up with questions just for the sake of asking questions. My concern is, if people feel that the author doesn’t really care about the answer, the whole exercise would likely be perceived as a waste of time.
… those hypothetical questions tend to be somewhat pedestrian for an expert Q&A site. When put on the spot to post content, we’re likely come up with uninspired questions that anyone would ask. And they’ve all been asked 100 times before on every other site on that subject.
Users enjoy answering questions when they are helping people, and everyone loves to show off a bit on occasion. But users do not want to be given homework assignments with a bunch of busy work. Even if you answer the question yourself, this "forced" content is going to look forced and sterile.
A last note on "Stack Exchange Jeopardy" where folks answer their own question— That is perfectly appropriate and even encouraged when you come across an particularly intriguing problem that you solved. Surely, share that information with the site at large. But sharing such unique insight is a far cry from searching out and seeding a site with contrived Q&A threads.