Rename to repository to 'knitout-to-kcode'?

[ixchow]

This would allow for a slightly cleaner URL if I directly publish with github pages. (But, now that I think of it, I might be able to use submodules in our overall page repository to get things exactly where I want them anyway.)

I.e., it seems like http://textiles-lab.github.io/knitout-to-code/ is a more sensible URL for this tool than http://textiles-lab.github.io/knitout-backend-kniterate.

[ixchow]

Counter-point to myself, I think that knitout-backend-kniterate makes sense for the repository as a whole, especially if it grows to include other tools.

[ixchow]

It is possible to serve this repository as a submodule of the main textiles lab page (the more descriptive URL without needing to change the name of the repository) -- in fact, it's set up like that right now -- but this means that the version served on the main page will need to be manually updated rather than always being the latest in this repository.

[gabrielle-ohlson]

I think knitout-to-kcode sounds good and may make more sense for folks who aren't familiar with the concept of a backend. I personally think it would be fine to change the repository name to that as well,
but I'm not strongly opinionated on it—overall, whatever feels clearer & easier.