bmjclark wrote:shubla wrote:- Cool UI
It looks like it was developed by a first year web development student who got straight D's
Well, Im not a webdeveloper or a designer. Feel free to suggest improvements or make a better one.
Glorthan wrote:Why not just use apx's data and make a PR for smoked foods?
I don't see how having disparate datasets is helpful, the idea was that people could write different front ends with a unified source, not just datadump and make a whole new slightly different backend further fragmenting the set of available recipes.
Correct me if I'm wrong, of course.
FWIW I think the site is slightly better than the original, but nowhere near the
original cookbook. Having separate input fields seemed to make it a lot less confusing for less technically inclined people in my experience, and the layout is nicer.
There are a few reasons.
One being smoked food of course, and generally having more control, as AXPEOLOG doesn't seem to update his stuff too often (there were some major problems for a month, it seemed like his site had completely stopped accepting data, actually development of this started during that time when axpeologs site was completely broken, but he happened to fix it before this was released).
The UI that axpeolog made had some bad bugs (Try setting amount of recipes visible to a large number, like 100). In addition to lacking a few interesting features and search syntax.
AXPEOLOG made his thing with vuejs and extensively used some AWS services, something that I'm not familiar with nor too willing to learn for this, so I just made my own.
I perhaps have to agree with the separate text fields being nicer graphically, but I feel like they make using the site a lot slower if you know what you are doing. The search syntax used is quite simple and shouldn't produce problems for too many.
Having separate datasets is for sure a bit sad, but they can be merged quite easily.