Half a year ago I’ve looked for elm package categorization site. I could not find any. So I made my own. And then @alexkorban created Elm package catalog. I don’t have as much time as Alex to make it even on par with his site. It’s not even worth to try since this this is already great site which I used a few times.
So now I question existence of Elm finder and what should be it’s purpose. Because currently it’s not worth to invest my time into something that is obviously not worth it and I’m thinking of shutting it down. But I invested some time into this and I want to know if someone would find it useful.
- I can just shut it down and make it permanent redirect to Elm package catalog until domain expires. There are a few places on the web which use link to it so it would be a pity to break those links. Cloudflare can handle that redirect for me so it’s the easiest option.
- Since I have in my DB all elm packages with docs for 0.19 and 0.19.1 I could expose it via REST API. So you would be able to use it for any purpose you would like. This would not be that hard and time consuming.
- Make it good testing place for UI for Elm packages. So I would completely remove categorization thing. This would simplify things a lot and save a lot of time. But this approach has problems. It’s the most time consuming of the three. I also don’t have any idea how better version of Elm packages should look like.
So what do you think? Do you find any of this useful or not? And if you want to know more, here is the source code: https://github.com/martin-jahn/elm-finder.