I'm a full stack web developer who has been freelancing for the last 20 years. I write about everything from development to production and also have video courses on my site!
Hey, thanks a lot for reading. Reply back here with your feature list (if it's not sensitive info). I'd love to take a look to see how others apply it.
I'm a full stack web developer who has been freelancing for the last 20 years. I write about everything from development to production and also have video courses on my site!
A document would be represented as a URL like https://example.com/${postID}, similar to how Medium works and can be viewed by anyone provided with the link.
If the owner views it, they can edit it however they'd like. If anyone else views it, they can only read the markdown.
Since I'm not too concerned about other users using this app I'd start with just #1, then allow for #3, and eventually #2.
My priorities revolve around anything that'll reduce friction in my own dev/writer experience.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Awesome guide, I'll be applying this to the project im starting on right now :D
Hey, thanks a lot for reading. Reply back here with your feature list (if it's not sensitive info). I'd love to take a look to see how others apply it.
Yeah sure. It's basically a cloud markdown editor so that I can edit and a future blog post from anywhere, be it mobile or my mac.
I would like to:
That's a good start. Have you thought about how to break down sharing an unpublished post into smaller steps?
Yeah, ideally I'd have 3 levels of permissions:
A document would be represented as a URL like
https://example.com/${postID}
, similar to how Medium works and can be viewed by anyone provided with the link.If the owner views it, they can edit it however they'd like. If anyone else views it, they can only read the markdown.
Since I'm not too concerned about other users using this app I'd start with just #1, then allow for #3, and eventually #2.
My priorities revolve around anything that'll reduce friction in my own dev/writer experience.