|
|
|
|
|
by newusertoday
2957 days ago
|
|
write about the requirements of your side-project, why you started it? what would be the use of it etc.
Blog about every feature that you develop and how to use it.
This will help in documentation when your prototype is ready and you might be able to attract audience who are interested in your prototype and might help you with beta testing/refine the features. You can also get early feedback without finished product.
For technical posts look at your commit log and pick the one that you think is most complex and describe it. It is possible that it may not be to the level of your satisfaction and you can refine it in second pass until you think it is ready to go. Idea is that is is easier to refine than writing from scratch. my 2 cents! |
|
>For technical posts look at your commit log and pick the one that you think is most complex and describe it
Thanks so much. This is exactly the kind of entrypoint I was looking for.