report necessary docs changes here
With Bugzilla defunct (RIP), we're still talking over what the process will be for reporting docs-related bugs, since they won't quite belong in the replacement system (Github Issues) we'll be using for code bugs. In the meantime, as you spot FAQs that need to be updated (or added), leave a comment here just so we don't forget them before we work out the replacement.
no subject
Edit: Oh wait. Swapping community names? http://www.dreamwidth.org/support/faqbrowse?faqid=214
http://www.dreamwidth.org/support/faqbrowse?faqid=77
no subject
Mention why members list is disabled somewhere.
If docs can clarify the profile message (disabled why?) if would be nice too.
no subject
<kaberett> something to go in the docs post...?
<V_PauAmma_V> (to kaberett) You mean http://dw-docs.dreamwidth.org/33984.html ?
<kaberett> yep
no subject
I think this is no longer true now (we always get inbox notifications?)
no subject
no subject
To edit or remove tags, you can go to Manage Tags from the "Organize" menu on any of the site-schemed pages. Here you may remove tags, rename tags, create new tags, and set the security level on your tags.
You can't set the security level of your tags on this page. You can *see* it.
Also may be add merge tags, and turn rename and merge into a link to http://www.dreamwidth.org/support/faqbrowse?faqid=209.
Also I realize that how the security level is private by default then dependent on the entry set isn't explained in the FAQ so maybe a few lines about this would be useful. It's not super intuitive as a process.
Depending on which journal style you've chosen (not all styles support this feature), your complete collection of tags will display in the sidebar of your journal as either a list or a cloud.
All our styles support this feature. Maybe rephrase 'not all styles'?
no subject
.setting.display.journalentrystyle.option says 'site skin' but .setting.display.journaliconstyle.label and .setting.display.journalentrystyle.option.comm say 'site layout'.
no subject
#178: How do I turn a personal account into a community?
The page can now be found at https://www.dreamwidth.org/communities/convert and can no longer be accessed through Create Community.
no subject
:)
ETA: oh I see that
no subject
Relevant support req is here: http://www.dreamwidth.org/support/see_request?id=28924
Inbox questions
I was looking for this in the Notifications FAQs and couldn't find any info about it (please tell me if I've missed it). I could find the answer to my first question in http://www.dreamwidth.org/support/faqbrowse?faqid=4 but I think it would be nice to mention limitations in a specific FAQ or add it to http://www.dreamwidth.org/support/faqbrowse?faqid=72.
Icons
http://www.dreamwidth.org/support/faqbrowse?faqid=16
http://www.dreamwidth.org/support/faqbrowse?faqid=240
per Anaraine's comment.
Why do I get a bad UTF-8 input error message? FAQ
Rephrasing the error message ("Bad Unicode Input
Your browser sent some text which isn't recognised as valid text in the UTF-8 encoding. This might happen if you forced your browser to view the previous page in some encoding other than UTF-8. It may also indicate a bug in the browser. If you can't get around this error, contact us.") might be useful as well as it doesn't mention the most common source of the problem (ie c/p from MS Word and other similar RT sources).
Can I undo deleted Inbox content?
This is a fairly frequent ticket question, so updating http://www.dreamwidth.org/support/faqbrowse?faqid=72 to say that message deletion is permanent might be a good idea; it's not mentioned anywhere that I've seen.
Mention http://www.dreamwidth.org/openid/options.bml somewhere
If not http://www.dreamwidth.org/support/faqbrowse?faqid=62 might be a good place for it although I think its own FAQ would be better if the title of FAQ #62 isn't edited as well.
Edit: actually #62 is a bad place for it since it talks about it the other way around. A whole new FAQ about using your DW ID to log into other sites would be nice I guess.
http://www.dreamwidth.org/support/faqbrowse?faqid=4 confusing
I think it's a very important FAQ and could use a fresh coat of paint to make things clearer (and as I think some things are missing from the list as well).
Re: http://www.dreamwidth.org/support/faqbrowse?faqid=4 confusing
Layer quotas not mentioned. Style quotas could be explicit. Don't think numbers are mentioned anywhere else (even in the repo config file). I had to find it out by creating layers.
Missing info about banning
I think missing info should be added to http://www.dreamwidth.org/support/faqbrowse?faqid=38 or everything could go in a new FAQ (What is 'banning'?).
General Getting Started FAQ
no subject
<./li>
in FAQ 131.no subject
no subject
http://www.dreamwidth.org/support/see_request?id=30365
Might be useful to mention that asking for a reset email does not reset your password until you've clicked on the reset link so if you remember it before that it will still work.
no subject
no subject
Sometimes, if the incorrect answer is given the first time and you go back to fix it, the CAPTCHA won't recognize any additional answers (whether they are correct or not). To pass the CAPTCHA, just do a hard refresh on the page to get a new question. On most browsers, that is CTRL+F5.
no subject
Looks good to me, stick it under Troubleshooting?
no subject
no subject
Well, that would certainly be a unique FAQ ...
no subject
We must assume the best of all intents
But sadly there are bots autonomous
and Google's rules they aim to circumvent.
For CAPTCHAs to prevent the spamming trash,
if answer first received is wrong, will fail.
An answer given twice will trigger cache
and will not recognize that ship set sail.
To make it through the tor'trous field of woe
and get your comment posted on the page
A hard refresh will brand new query show
With different answer crave'd on the stage.
To do this thing and pass through lock-ed gate
a doubled keypress needed to unlock
Control and function five will wipe the slate
Just hold together to turn back the clock.
And if there is an error to report
Just take a breath, and kindly ping Support.
no subject
no subject
ahahahaha i love you. post this to your journal. :)
no subject
no subject
Current: doesn't mention tag navigation
Proposed:
You can easily move between entries in the same journal or community with the same tag. Select the
no subject
Proposed:
Dreamwidth is working to support https on all pages. If you experience weirdness that might be caused by https issues, please let us know about it by contacting Support.
no subject
Current:
You can use the Leave a comment link to add a comment to an entry. The exact text label for this link may be different in different journals. This link opens a form with a text box where you can enter your comment. In some journals, the reply form will open on the same page, but in others, the link will take you to a new reply page.
Proposed:
You can use the Leave a comment link to add a comment to an entry. The exact text label for this link may be different in different journals. This link opens a form with a text box where you can enter your comment. In some journals, the reply form will open on the same page, but in others, the link will take you to a new reply page. On the reading page, the reply form will open on the same page. You can use the Read X Comments link to read other comments which have been left already.
no subject
no subject
Can someone point me in the right direction?
no subject
Anyway! Hi! Welcome! We'd love to have you working on docs, even though we still need to clean up the process!
For now: Check out the manual of style and the Documentation category on the wiki -- some of the stuff in the category is old (it's been a while since I've had the time to go through the wiki and flag stuff that's no longer current or in need of update) but it's good background. Then, download and read the Contributor Licensing Agreement, sign the last page, and send it back to me.
(The CLA basically says you keep the rights to any of your contributions but grant us a permanent license to use and redistribute them; it establishes that we can't hold you responsible in the future if something goes Horribly Wrong and, like, your code causes a rift in the space/time continuum; and it binds us to always offering your contributions to our free-software-licensed repos under a license that's at least as permissive as the one in force when you submitted it -- in other words, we promise that we'll never take the source entirely closed as long as we're still operating the site. It's basically to cover our asses and the asses of our contributors in case of a future dispute.)
Once you've sent in a CLA, create a Github account (and let me know the username, so you might want to do that before sending the CLA) and bookmark/watch the dw-free repo. When you see a FAQ that should be changed/expanded/rewritten, or identify a FAQ that should exist but doesn't, open an issue and add your suggested text or changes to the issue; one of us will take it from there.
(We don't have a complete list of "docs changes that need to be made", so if you want to make "making that list" a first priority, you can also log docs issues without also writing the new copy!)