When I first built Ozigi (initially WriterHelper), the goal was simple: give content professionals in my team a way to break down their articles in...
For further actions, you may consider blocking this person and/or reporting abuse
lol I just came from the previous post 🤣
All the feedback I gave - you have already incorporated it. It works really well. this is exactly what I wanted: giving it the necessary context so it can create posts in my preferred style.
edit: add demo video to the repo if you can, it will be really useful.
😁 This is great feedback for me honestly. I'm glad your suggestions were incorporated, even before you suggested them. 😅
I'm thinking of adding the video, and then a sort of documentation on what the app does exactly. It's actually a general use app and you don't have to be a dev/content professional or DevRel person to use it.
Anyone who posts insights on sm is the perfect user.
yeah, just make the ux super smooth because that's what a lot of people care about. I would say use #discuss tag in your posts if you want the feedback from the community here -- it targets entire devto community.
Thanksssss. I already made a lot of improvements. You can check it out.
oh, there's a v3 roadmap as well! Waiting for it!
Thank youuuuuuuuu.
Have you tried the V2?
not yet, I've high fever. I just go through the blog. Will try soon.
I did try the 1st version.
I'm so sorryyyyyyy.
Get well soon! <3
no need to sorry. virus should apologize.
This is so neat.
Looking forward to being able to publish directly to sm platforms 🚀
Thank you so much, Chris! I appreciate it.
This is the kind of changelog I trust because it is not just features, it is pain you removed. Pulling auth, calls, and UI out of one growing file into single responsibility components is one of those moves that feels boring until you have done it, then you cannot unsee the difference.
Centralizing types is also underrated. A strict core shape that the rest of the system has to obey is how you stop the quiet rot.
Curious about the localStorage dashboard state. How are you handling versioning and reset when the schema changes, so people do not get stuck in a weird state after an update