@ThrowingSpoon re type annotations, I've been thinking we should write the most concise/natural code possible for the examples. If the types are unclear (or if it would be illustrative to show them), they can be explained in comments
of course we're all making this up as we go, that's just my 2¢ :)
It would be awesome if we could get to keep rep earned on the Q & A part of the site, for bug reports and feature requests and such, once docs goes out of beta. Would make it more rewarding to report bugs :-)
It looks like someone removed the versions table from the PHP tag, and as a result, the version box next to the titles of topics is empty, as is the version selector when editing. How do I add it back ? Is it intentional that versions can be removed from a tag ?
Still seems a bit weired from a UI perspective that removing version info makes UI elements show up empty. I think the UI elements should also be hidden in that case:
"versions are pulled off the hello world topic" That means to add them (back), I just add a table to the remarks section of the hello world topic, under a "Versions" heading ?
so i think I have created both http://docs-beta.stackexchange.com/documentation/git/281/merging and http://docs-beta.stackexchange.com/documentation/git/291/merging
(both are "merging" under Git)
wasn't intentional. not sure how to undo the damage.
I also saw that once. Two topics with the same with the same title, consecutive numerical ids. Looked unintentional, too. Can't find anymore though. (@brentonstrine )
I have just added an example to the <html> >Hyperlinks section of the docs.
You can see my example here.
Which is calling a javascript function from an html <a> tag.
The problem is this could fit under both javascript and the html > hyperlink category.
Could we have a way that we could put a...
@KevinMontrose Lets say I am writing an example... In my case how to set the background colour of a div... in the example do we include things like height, and width? or do we leave those things out?
IMHO, yes, since making it visible will help folks understand what's going on.. Exp@aining why you added those details would be good, though @TrevorClarke
Just want to say I'm really excited about the community being able to write documentation for xcode that's comprehensive & useful, and not having to shoehorn it into individual SO questions/answers :D
I guess do it if you want, but I might not bother with it, it's a lot of effort... those kinds of things (lists of possible properties / parameters / etc) are usually already documented well elsewhere @TrevorClarke
@JonasCz tour and help pages will cover some of that, I'll slam out an answer real quick. I disagree, but I don't think you're trying to do anything we don't support.
@TrevorClarke no syntax was fine, parameters should have been cut
I have just added an example to the <html> >Hyperlinks section of the docs.
You can see my example here.
Which is calling a javascript function from an html <a> tag.
The problem is this could fit under both javascript and the html > hyperlink category.
Could we have a way that we could put a...
