Outline Feedback and Next Steps
This lesson is part of the orientation series for potential newline authors. If you've landed on this page - and you're interested in creating a book or course -- you might consider starting back [at the author application page](https://www.newline.co/write-a-book) for context.
Lesson Transcript
[00:00 - 00:10] Okay, we're almost there. By now, you should have a pretty good outline and you should send it to us. To do that, either email me or join our Discord server and then send it to me there, and we can set up a time to meet together and go over it together.
[00:11 - 00:37] I will, of course, have some ideas on how we can shape it, but the most important thing for us to do is to get it in front of real students. We have a list of folks who have signed up to be beta readers and we will reach out to them and ask for our comments on your outline. But our readers shouldn't be the only one who see this. We need to get the outline in front of people, anyone who's interested. So share it with your Twitter followers, share it with your co-workers, and so on. Post on Reddit if you want to. There's no benefit to keeping the outline secret.
[00:38 - 00:46] No one is going to steal our course and the real risk is that we spend months building something that nobody cares about. And that is a running theme in this process. Share your work.
[00:47 - 01:25] If we wait until the course is done, until we share it with anyone, then we've failed on our process. You've got to be talking about your work publicly along this whole process. And so, we'll start with the outline. So your next steps are to review your outline and make sure it's cleaned up for public review. Reach out to me via email and tell me your outline is ready for us to send to beta readers. And book a meeting with me and we'll review your outline. I'll send you a calendar URL when you send me an email. Until we meet, feel free to get started in on the code examples for your first project. By this point, I bet you have a solid idea for the first code example so feel free to start working on it. Talk soon!
[00:00 - 00:10] Okay, we're almost there. By now, you should have a pretty good outline and you should send it to us. To do that, either email me or join our Discord server and then send it to me there, and we can set up a time to meet together and go over it together.
[00:11 - 00:37] I will, of course, have some ideas on how we can shape it, but the most important thing for us to do is to get it in front of real students. We have a list of folks who have signed up to be beta readers and we will reach out to them and ask for our comments on your outline. But our readers shouldn't be the only one who see this. We need to get the outline in front of people, anyone who's interested. So share it with your Twitter followers, share it with your co-workers, and so on. Post on Reddit if you want to. There's no benefit to keeping the outline secret.
[00:38 - 00:46] No one is going to steal our course and the real risk is that we spend months building something that nobody cares about. And that is a running theme in this process. Share your work.
[00:47 - 01:25] If we wait until the course is done, until we share it with anyone, then we've failed on our process. You've got to be talking about your work publicly along this whole process. And so, we'll start with the outline. So your next steps are to review your outline and make sure it's cleaned up for public review. Reach out to me via email and tell me your outline is ready for us to send to beta readers. And book a meeting with me and we'll review your outline. I'll send you a calendar URL when you send me an email. Until we meet, feel free to get started in on the code examples for your first project. By this point, I bet you have a solid idea for the first code example so feel free to start working on it. Talk soon!