Congrats! Some quick thoughts, then I've got a few questions for you...
Let's face it, there are many platforms out there already which are ideal for publishing a programming course. There are obviously pros and cons with each.
I'm glad to see Slip has such a straightforward and open revenue model. Some course platforms work on a royalty model where you are paid by minutes of your course videos watched... which can make it difficult to estimate how much you'll earn for all your hard work.
It's also nice to see that you're handling taxes and VAT obligations. Few do that. Udemy springs to mind as a platform that also handles tax, but there are others. I think going forward that more and more platforms will need to help their merchants handle tax, so kudos to you for thinking about it from the start.
Some of the platforms like Scrimba.com, Tuts+ and egghead.io are invite-only. I'm really glad to see you didn't go that route. However, those platforms will tell you they do it to ensure course quality and happier outcomes for students.
Which brings me to my questions...
Q1) Since you've created an open course marketplace, how do you plan to ensure course quality?
Q2) In the spirit of openness and transparency, I'm not seeing any links to terms of use, privacy policy, or policies that apply to instructors (licensing, payouts, dispute resolution, etc). For example here's Udemy's Instructor Terms (https://www.udemy.com/terms/instructor/) which references their promotions policy and various instructor obligations. Are your versions of those documents still in the works? If they already exist, are they only visible after you register (that would be an anti-pattern, but maybe there's a good reason)? Are you planning to make those viewable before someone signs up to the service?
Q3) Programmers aren't always natural course creators and effective teachers. Are you planning in the future to offer educational materials to help guide programmers on best practices for planning, producing, and publishing their course?
Q1) Right now, we're manually approving/denying courses for publishing based on a subjective quality bar. Our aim is to be more of a premium course marketplace for career developers.
Q2) Ah yeah we have a ToS, i'll add it to the home page rn. It's still evolving.
Q3) Yup we want to help more developers realize they can be teachers. Figuring out how to better take a dev from Never teaching -> Making money while creating real progress in their students, is a big goal
Let's face it, there are many platforms out there already which are ideal for publishing a programming course. There are obviously pros and cons with each.
I'm glad to see Slip has such a straightforward and open revenue model. Some course platforms work on a royalty model where you are paid by minutes of your course videos watched... which can make it difficult to estimate how much you'll earn for all your hard work.
It's also nice to see that you're handling taxes and VAT obligations. Few do that. Udemy springs to mind as a platform that also handles tax, but there are others. I think going forward that more and more platforms will need to help their merchants handle tax, so kudos to you for thinking about it from the start.
Some of the platforms like Scrimba.com, Tuts+ and egghead.io are invite-only. I'm really glad to see you didn't go that route. However, those platforms will tell you they do it to ensure course quality and happier outcomes for students.
Which brings me to my questions...
Q1) Since you've created an open course marketplace, how do you plan to ensure course quality?
Q2) In the spirit of openness and transparency, I'm not seeing any links to terms of use, privacy policy, or policies that apply to instructors (licensing, payouts, dispute resolution, etc). For example here's Udemy's Instructor Terms (https://www.udemy.com/terms/instructor/) which references their promotions policy and various instructor obligations. Are your versions of those documents still in the works? If they already exist, are they only visible after you register (that would be an anti-pattern, but maybe there's a good reason)? Are you planning to make those viewable before someone signs up to the service?
Q3) Programmers aren't always natural course creators and effective teachers. Are you planning in the future to offer educational materials to help guide programmers on best practices for planning, producing, and publishing their course?