HelpIndex
Revision as of 02:10, 8 March 2008 by 198.36.178.141 (talk) (→A: Accout, create lik changed from tutorial to stand-alone page)
Account
- AddCategory
- Address, removal
- Advanced Editing (metawikipedia)
- Adult content
- Anchors (metawikipedia)
- Alerts for page changes. See Changes
- Article. See Page
- Automatic page generation. See Bot
Contents
B
- Badge, AboutUs
- Basic formatting
- Big text
- Boldface
- Bot
- Breaking lines of text
- Bugs, report a bug or error
C
- Capitalization of page name. See Page
- CamelCase
- Carriage return
- Categories
- Categories, add a category
- Categories, detailed help (metawikipedia)
- Characters, special (metawikipedia)
- Characters, unicode
- Changes
- Chat live with AboutUs staff and users. See IRC
- Comments (hidden comments in text) (metawikipedia)
- Community Reviews
- Community Reviews, formatting
- Community Reviews Guidelines
- Complaints. Also see ConcernsFAQ
- ConcernsFAQ
- Configure personal preferences
- Contact AboutUs for help, how to
- Contact information, removal
- Contents, Table of Contents
- Copyright Complaints. See Complaints
- Contributions of a user, listing
- Create a page. See Page
- Create Subdomain
- Custom thumbnails, tagging
D
- Deleting content
- Deleting a page
- Developers, AboutUs software developers
- Domain name disputes
- Domain page capitalization
- Domain page detection query
- Domain, tag non-existent or shut
E
- Edit. Also see Formatting
- Email, protect email address from spam
- Enlarge text
- Error, report a bug or error
- Extensions (MediaWiki)
- Extensions, googlemap (MediaWiki)
- External Links. See Links, External
F
- FAQs (answers to Frequently Asked Questions)
- Featured Pages
- Featured Page, nominating
- Featured image tagging
- File upload to AboutUs
- Flag adult content
- ForgotPassword
- Formatting. Also see Edit
- Formatting, basic
- Formatting, boldface
- Formatting, cheatsheet
- Formatting, comments (metawikipedia)
- Formatting community reviews
- Formatting, fixed-width (typewriter) text (<tt>) (metawikipedia)
- Formatting, headings
- Formatting, HTML tags in (metawikipedia)
- Formatting, indents
- Formatting, italics
- Formatting, lists
- Formatting, sections
- Formatting sections, detailed help (metawikipedia)
- Formatting, strikethrough (metawikipedia)
- Formatting, special characters (metawikipedia)
- Formatting, tables
- Formatting, tables, detailed help (metawikipedia)
- Formatting text
- Formatting, typewriter text (<tt>) (metawikipedia)
G
- Gallery
- Glossary
- Googlemap extension (MediaWiki)
H
- Headings. See Formatting
- Help contacts for AboutUs. Also see IRC
- Help page for user questions
- Help portal
- Hidden comments in text (metawikipedia)
- Horizontal line (metawikipedia)
- Hide address from outside bots. See Bot
- Hide email address from outside bots. See Bot
- HTML tags in wikitext (metawikipedia)
- Home page of AboutUs
I
- Images
- Images, detailed help (metawikimedia)
- Image gallery
- Image positioning
- Image quick help
- Image tutorial (wikipedia)
- Image, size
- Image, thumbnail
- Image, upload to AboutUs
- Indents
- Index of AboutUs (extremely incomplete, just getting started)
- Infringement notice
- Intellectual Property Policy
- Internal Links
- Interwiki. See Links, Interwiki
- IRC (Internet Relay Chat)
- Italics
- Invisible comments in text (metawikipedia)
L
- Line break
- Links
- Linking
- Link to AboutUs
- Links to page or website
- Links, CamelCase
- Links, detailed help (metawikimedia)
- Links, External or Links, External. Also see Links, Interwiki
- Links, Internal
- Links, Interwiki
- Links, Interwiki linking (metawikimedia)
- Links, Interwiki, AboutUs Interwiki map, prefixes
- Links, list of AboutUs links to current page
- Links, plainlinks
- Link spam
- Lists, basic
- Lists, detailed help (metawikimedia)
- Live chat with AboutUs staff and users. See IRC
M
- Map, automatic
- Map, googlemap extension
- Message to another user
- MediaWiki extensions (MediaWiki)
- MediaWiki Handbook (metawikipedia)
- Move vandalism, fixing
N
- Navigation, sidebar
- Navigation, sidebar,site navigation
- New page. See Page
- New page, how to write. See Page
- Non-existent domain, tag
O
P
- Page (Article)
- Page name capitalization
- Page change alerts. See Changes
- Page, create
- Page, fix name
- Page, mark for deletion
- Page, formatting text. See Formatting
- Page, featured, nominating
- Page, how to improve ; also see list of featured sites
- Page, how to write
- Page, personal
- Page, sidebar
- Page, thumbnail image in
- Page, video, adding
- Paragraphs (metawikipedia)
- Password, forgotten password
- Password-required domain, tag
- PersonalPage
- Personal page, overview
- Personal preferences
- Photos. See Images
- Pictures. See Images
- Plainlinks
- Preferences
- Preformatted Text
- Prevent bot from gathering info. See Bot
- Preview edit changes
- Privacy, AboutUs policy
- Protect address from outside bots. See Bot
- Protect email address from outside bots. See Bot
R
- RecentChanges
- Re-creation of page, preventing
- Redirect
- Register. See Account
- Related Domains (section of Domain Page)
- Remove inaccurate AdultContent flag
- Remove info generated by AboutUs bot. See Bot
- Remove address and contact information
- Remove a page
- Report a bug or error
- Report a complaint. See Complaints
- Report a concern
- RSS
S
- Sandbox
- Searching AboutUs
- Sections and headings. See Formatting
- Security through obscurity
- Send a message to another user
- Show changes
- Shrink text
- Shut domain, tag
- Sidebar, adding to page. See Page
- Sidebar, site navigation
- Signature, improving
- Small text
- Software developers, domain page detection query
- Strikethrough (metawikipedia)
- Spam
- Spam, protect email address from spam
- Spam, category spam
- Spam, link spam
- Spam, sites that spam
- Spam, tagging pages of possible spammers
- Special characters (metawikipedia)
- Specific (non-AboutUs.com) website feedback
- Subdomain capitalization
- Subdomain, create a page for
- Suggested edits. See Tagging
- SuggestionBox
- Summary of edit
- Syntax
T
- Takedown notice
- Templates
- Templates, detailed help (metawikipedia)
- Table of Contents
- Tables
- Tables, detailed help (metawikipedia)
- Tags, HTML tags allowed in wikitext (wikipedia)
- Tagging (AboutUs special tags / templates)
- Adult content, flag for
- remove inaccurate Adult content flag
- Tag authorization-required domain
- Tag "coming soon" domain
- Tag improper deletions
- Tag custom thumbnails
- Tag featured image
- Tag fix to get map to work right
- Tag page to delete
- Tag for name of page fix
- Tag for sale domain
- Tag password-required domain
- Tag incomplete hand-created page
- Tag non-existent domain
- Tag for page name fix
- Tag parking lot
- Tag possible spam domain
- Tag spam
- Tag shut domain
- Tag temporary talk page
- Tag test page
- Tag thumbnail, custom
- Talk
- Test, page for testing wiki code
- Test page, tagging for deletion
- Text formatting. See Formatting
- Thumbnail
- Thumbnail, custom, tagging
- Thumbnail, update
- TOC (table of contents)
- TheWikiWay:TopMenu
- Town Pump
- Tutorial on Wikis
- WikiSyntax
U
- Undo Edit
- Unicode characters
- Unwatch a page
- Upload file
- Usage guidelines
- site navigation
- UserContributions
- User home page
- User preferences
- User messages. See Talk
- User talk. See Talk
V
- Vandalism, fixing move vandalism
- Verisign, report logo forgery
- Video Support
- Videos, YouTube
- Volunteer opportunities at AboutUs
W
- Watch pages for changes; Watchlist. See Changes
- Website (non-AboutUs.com) feedback
- Whois services
- Wiki, What is a Wiki?
- What links here
- WikiAnatomy
- WikiLink
- Wiki tour
- Wiki tutorial
- WikiSyntax
- WordPress.org (free publishing platform)
Y
Moving namespaces
Ran across a good potential use for Namespaces. I want to see if HelpIndex links to the pages pointed to by Six messaging areas. Some of those pages are linked to by a huge list of stuff. The What links here pages allow me to limit the list to a particular Namespace. Unfortunately, HelpIndex seems to be in the main Namespace. Would it make sense to move it to the Help namespace so we could more easily see if HelpIndex linked to various pages? What would be the side effects of this move? -- Joe Cohen | Leave me a message 20:09, 10 February 2008 (PST)
- Yes, I have seen that benefit as well. I think it's fine to move it. Help:HelpIndex or Help:Index? The potentially hardest part of that will be checking backlinks for double-redirects, but maybe since HelpIndex is new, there aren't too many redirects to it yet.
- I do suggestion moving this part about the re-naming to HelpIndex before we do it. TedErnst (talk) 05:58, 11 February 2008 (PST)
- Re your question where to move it: Help:HelpIndex or Help:Index? The second is simpler. I like simple but don't have a strong preference. Does one of these work better than the other? Note that because of how Find functions, you must type "Help:Index" into the Find box to have Help:Index returned as a search result. So we must keep HelpIndex (for among other reasons) so that users searching for "Help Index" and the like would generate a hit.
- "What links here" says there are 50 pages that link to HelpIndex. This is a manageable number for checking backlinks for double-redirects. And even 50 appears to be an exaggeration; it appears that many of these pages link to HelpIndex only because they include the CommunityNews template.
-- Joe Cohen | Leave me a message 07:43, 11 February 2008 (PST)
- Joe, I have never been a big fan of namespaces, as Ted knows :-) - I am usually more interested in flattening out the wiki than making it more complicated. What benefit do you see about using the namespace, I see you mentinon What links here - but am still confused. Best, MarkDilley
Mark: What I see isn't a huge benefit; there are workarounds; and I don't know enough about the workings of Namespaces to have an opinion on the tradeoffs. Anyhow, here's what I had in mind as a benefit:
I stumble across (or someone sends me to) a page that includes some kind of help. Is that page already included in HelpIndex? An intuitively easy way to answer this is to look at What links here. But What links here may return a really long list of pages -- in an order that I don't yet understand -- partly because it defaults to listing pages from all Namespaces. If HelpIndex were outside the Main Namespace (e.g., in the Help Namespace), I could display What links here from only the Help Namespace, and tell more quickly if the page was linked to by HelpIndex. That's all I had in mind. -- Joe Cohen | Leave me a message 11:19, 11 February 2008 (PST)
Tasks
-
fix interwiki links ASAP: most wikipedia links should be to meta -
Add all entries from AboutUs Help-
Turn into links, duplicating under different headings as appropriate -
"Formatting" heading
-
Review AboutUs:Basic wiki formatting and add headingsReview WikiTour and add headingsReview Help and add headingsCommentsAdd Link Spam to Linksf ix Alert links to point to EmailAlertsReport a bug, report a concernReview Glossary, add entries as appropriateHere's another list to go through and make sure it's all represented here. Six messaging areas; Done-
Review site navigation toolbar, and make sure represented here.- also would be nice to figure out a place to make recommendations on better site navigation. Right here is fine
break linehorizontal line (I'm having trouble finding this)- paragraphs
- formulas
- advanced / css
- Add entries as appropriate, with multiple headings, if appropriate
- in source text for this section, change <strike> to css
- perhaps create template to be used for links to (metawikipedia)
- Category-style alpha TOC; perhaps best if this could float; but floating is probably incompatible with multiple columns because the index would cover up part of the right-hand column(s). See next bullet point.
- turn the index into multi-columns (takes less time to find right place). But probably incompatible with floating index.
-
add entry for metawikipedia helpadd very short note above or below HelpIndex explaining metawikipedia, MediaWiki.
Idea
Self-assembling help index
- Would the following scheme work?
- Move all Help pages to a special Namespace (e.g., the Help Namespace)
- Now the Help index is simply a (specialized) list of all pages in that namespace. The index is specialized in that it would:
- at a minimum, strip the name of the namespace from each entry. For instance, the index entry for the page named "Help:Bold" would appear in the index as "Bold"
- could also add additional formatting. For instance the index could have formatting like a category page, with entries organized under a letter of the alphabet, put in columns, an alphabetical index appearing at the top of the page.
- Note that in this scheme, you create additional index entries that link to an existing help page is simply to create a redirect page. For instance, if there's a page named (and indexed under) "Bold", and you also want an index entry for "Formatting, bold" that points to that page, you create a new page -- in the Help Namespace -- titled "Formatting, bold" which simply redirects to Bold.
- Cross-reference index entries work the same way (they are just redirects).
- Entries that point to sections of pages work the same way (they are just redirects).
- Advantages of this scheme
- It is automatically complete. I.e., there is at least one index entry per help page. I think this is big deal:
- Manually trying to figure out whether the index is complete takes forever, and isn't guaranteed to work.
- It's automatic. There's one less step to complete (or forget to complete) when someone adds (or deletes) a new help page.
- Adds more organization to help pages. Makes them easier to find. So it would be easier to eliminate or redirect the many pages that are duplicates, empty, or whose substance is covered more completely elsewhere.
- Could benefit the larger wiki community if the scheme is transportable to other wikis.
- It is automatically complete. I.e., there is at least one index entry per help page. I think this is big deal:
- Disadvantages of this scheme
- It takes some development effort. But as it ends up looking much like a Category page, I suspect it's not hard to develop.
- I don't know if I can redirect off-site. This is a big deal.
- The source that creates the entries cannot be edited in one place. In the hand-built index, I can see the source text for the entire index just by editing the HelpIndex page. In the self-generating index, the source is distributed over many pages - one page per entry.
- Harder to fix typos? You would have to re-name a page.
- Theoretically raises the bar to community participation. In the current hand-built index, you can create a new entry with knowledge only of basic editing and wiki formatting. The scheme would require knowledge about Namespaces and Redirects, which requires deeper knowledge of MediaWiki. But, this problem could be ameliorated by appropriate help pages (e.g., how to add a new entry to the help index). Also, I don't know how significant this problem is; how many casual users will try to modify the Help Index. If none or few, we can live with this disadvantage. (We can get a feel for this by seeing who is modifying the current hand-built index.)
- Cannot create custom entries, may lose some information that's currently built in by hand. For instance, where the entry points off-site, I currently add something like "(metawikipedia)". This would disappear. I don't know if there's a work-around. And in the hand-built index, entry text in the form [url] would appear in the hand-built index with a dashed underline. But that information would disappear in the self-assembling version as the entry would point to a page in AboutUs (which re-directs off site).
Discussion
Wow, Joe. Lots to think about here. I have a couple of thoughts right off, and then I'll come back and be more thorough. TedErnst (talk) 08:42, 24 January 2008 (PST)
- We've struggled with the idea of the help namespace because we don't know what goes in it. Maybe this doesn't matter? For example, Bold could redirect to Help:Bold and we get the best of both worlds. I'm not sure.
- Response -- Joe Cohen | Leave me a message 17:36, 24 January 2008 (PST)
- I don't think namespaces generally should matter to site users. And I don't see any problem in the kind of re-direct you mention. But namespaces could have an administrative use that's invisible to most users. Under the proposed scheme the namespace matters only to people who create help pages.
- My larger goal is a help index that assembles automatically (or semi-automatically). Maybe there's a better way to do it. My knowledge of the inner workings of MediaWiki is rudimentary. Maybe someone more knowledgable can propose an alternate scheme.
- Response -- Joe Cohen | Leave me a message 17:36, 24 January 2008 (PST)
- I'm not sure the automated way using the help namespace actually does save a step, because someone still has to know to put the new article in the help namespace. If they mis-name, it's lost, just as in the situation where someone forgets to add a new page to the hand-generated HelpIndex.
- Good point that a help page after implementation of this scheme can still get lost if it's created in the wrong namespace. But -- if it's in the right namespace -- then creation of the help page and an index entry is one step. In contrast, creating a hep page and an index entry under the current scheme is always two separate steps. -- Joe Cohen | Leave me a message 17:36, 24 January 2008 (PST)
- I've thought more about the issue of bold having it's own page, by the way, and am coming more and more to the conclusion that it does, even if it also lives on the BasicWikiFormatting page. See watch and my watchlist for examples. These aren't quite right yet, but maybe it shows the idea I have? This is seperate from your automated idea, but might make things easier in any event. We'd no longer need to use anchors in the manual list, and if we decided to do the automated one, we'd be forced into this scheme anyway, I think. I do like the idea of redirecting for cross-references. We could actually start doing that now. One problem with this is that double-redirects don't work, so if the destination of the redirect moves, we'll have to manually fix all re-directing pages, which is always true.