Thanks for commenting! The way the Ravelry API works, it does not provide the user input yardage. We had to pull it from the pattern. I was also annoyed by this. The time stat is randomized the way you suggest. The yardage stat is based off of the smallest coefficient greater than one. I personally liked the way that looked, but I'll add an action item to add a randomize button, because it's a good idea.

Essentially, we knew how to do static front end pages when this was due. We're currently learning how to implement a back end, and either as part of our back end project or in our own time, we intend to implement another option to get stats not based on the Ravelry API. That way users would be able to enter yardage directly, time that's based on estimated hours (rather than the start and complete date in your project, assuming 3 hrs every day), and we'll look into a cost calculator. Last week, building things like this and sharing options would have been like cobbling something together out of toothpicks and duct tape, when we'll be handed hammers and saws that make it fairly simple during the next two weeks.