See, that reads wrong to me. It is the technical term -- going all the way back to journalism and print layout using type -- so even if people aren't as aware of it, that is what it should be called. It's also what other sites that allow the feature, like Word press, call it, so...
Technical term or not, it is confusing, especially as it is something that
other sites of our variety don't have. That being said, I think the body of
the FAQ Explains fairly clearly what a slug is. If we run into a lot of
confusion down the road then we can reevaluate. Fair?
I agree with this FWIW, I know exactly what the term means but others were completely clueless, while people using the update page may see the feature if they select customise and see the option, I suspect most will come to it trying to figure out how to do what their friends have already done or similar, and if they don't know what a slug is in the first place...
I second that. I don't know if the term is used enough that it's newbie-friendly but I highly doubt it's non-native-speaker friendly as it's very jargon-y. Before I googled it the only slugs I knew were either animals or bullets. And the interface doesn't help understand what this is about. Like at all. How about a double title like for cuts? This way more people can understand what the FAQ is about and find it via search.
The APIs are a horrible mess and there are many other things that need to go into them. At this point we're not really taking suggestions unless accompanied by a patch until and unless somebody adopts the project and is willing to be the one to step up and a) have the unified vision and b) get the shit done, because we don't have anybody dedicated to working on it and piecemeal updates without that unified vision are worse than no updates at all, as they'd break things constantly. It actually sucks less to have the APIs be "here there be dragons" until they can be fixed than to have them constantly in flux.
That makes sense-so basically need to find someone that's likely to be able to understand what's needed and work on it. Or learn a huge amount of stuff in a language I can't get my head around...
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
no subject
no subject
no subject
"slug" is what it's called in the update page pane, though, so if someone sees that, "slug" is what they'll be ctrl-Fing on the FAQ list to find.
no subject
no subject
See, that reads wrong to me. It is the technical term -- going all the way back to journalism and print layout using type -- so even if people aren't as aware of it, that is what it should be called. It's also what other sites that allow the feature, like Word press, call it, so...
no subject
Technical term or not, it is confusing, especially as it is something that other sites of our variety don't have. That being said, I think the body of the FAQ Explains fairly clearly what a slug is. If we run into a lot of confusion down the road then we can reevaluate. Fair?
no subject
Sounds good.
no subject
no subject
no subject
no subject
There is not, it has to be done through the new update page.
no subject
no subject
The APIs are a horrible mess and there are many other things that need to go into them. At this point we're not really taking suggestions unless accompanied by a patch until and unless somebody adopts the project and is willing to be the one to step up and a) have the unified vision and b) get the shit done, because we don't have anybody dedicated to working on it and piecemeal updates without that unified vision are worse than no updates at all, as they'd break things constantly. It actually sucks less to have the APIs be "here there be dragons" until they can be fixed than to have them constantly in flux.
no subject
no subject
The good news is, there were a few people at YAPC who expressed interest!