In step 1, it's better to link to customization page using an tag from the phrase "customization page" rather than leaving a bare link, which as you may note is not auto-linkified, since you are in "No auto-formatting" mode. The same in step 6, and everywhere where you have that link.
In step 3, typo "usally".
In step 4, it might be good to clarify which part to copy (not the whole ). Perhaps highlighting the part to copy in the previous step.
also: ie-based browsers (haven't tested this in version 7) don't display css or js or anything like that in the browser window. it prompts a download of the file. stupid ie.
Seconding kunzite1's comment. IE has been a constant source of frustration. I used to have to ask users to copy the link and post it somewhere, and then right click on it --> save as, to avoid the problem of it automatically opening up in Frontpage or some other program which mangles the stylesheet by dding extra symbols.
I'd suggest adding a warning about using a plain text editor when editing the stylesheet, and not Word etc. Wordpad might also do some mangling but I'm not sure.
Comments 5
Such important stuff is usually mentioned very early.
Reply
Reply
In step 1, it's better to link to customization page using an tag from the phrase "customization page" rather than leaving a bare link, which as you may note is not auto-linkified, since you are in "No auto-formatting" mode. The same in step 6, and everywhere where you have that link.
In step 3, typo "usally".
In step 4, it might be good to clarify which part to copy (not the whole ). Perhaps highlighting the part to copy in the previous step.
Reply
Reply
I'd suggest adding a warning about using a plain text editor when editing the stylesheet, and not Word etc. Wordpad might also do some mangling but I'm not sure.
Also, the stylesheet URL is now in the form(s): http://exampleusername.livejournal.com/res/0000000/stylesheet?0000000000
http://community.livejournal.com/exampleusername/res/0000000/stylesheet?00000000000
Reply
Leave a comment