(no title)
sephoric | 7 years ago
I've been writing Autumn on and off for a few months, because there's something really satisfying and rewarding about automating something you do often, and then using that to automate more, and building upward in a cycle.
That, plus I wanted to see how close to building a "legit IDE" I could get while completely faking it with WKWebViews. So Autumn kind of grew from those two principles and I'm really happy with how it turned out.
I'd be glad to answer any questions, I'll be here for a few more hours. (I don't have internet at home so I use the library's wifi for stuff like this, and it closes early today.)
snek|7 years ago
It would be nice if the documentation was available without having to download this, so people could see what the API is like.
It would also be super duper epic if this supported ESM properly.
sephoric|7 years ago
Regarding online documentation, good idea, thanks! I'll try to add that this week. Although, the app is so much more than its API, which is what makes it so unique, and I think if people just look at the API itself, they don't quite get to feel the experience of using Autumn to create their own automation workflows, which is what I'm most proud of about Autumn.
sephoric|7 years ago
sephoric|7 years ago
kiliancs|7 years ago
Things I noticed right a way:
- The logo and the title font. There's nothing wrong about them, but they don't reflect much about the application - Scrolling, there are a few elements that appear over the header bar
tptacek|7 years ago
It's hard for me to evaluate how useful this would be to my workflow without seeing the API, and it looks like I have to actually run the app to do that. It might be worth putting a copy on the website.
zsprackett|7 years ago
https://productforums.google.com/forum/#!topic/webmasters/pV...