text:
Help Contents
Here is a tour of the most important help pages:
HelpForBeginners - if you are new to wikis
HelpOnNavigation - explains the navigational elements on a page
HelpOnPageCreation - how to create a new page, and how to use page templates
HelpOnUserPreferences - how to make yourself known to the wiki, and adapt default behaviour to your taste
HelpOnEditing - how to edit a page
HelpOnActions - tools that work on pages or the whole site
HelpMiscellaneous - more details, and a FAQ section
These pages contain information only important to wiki administrators and developers:
HelpOnAdministration - how to maintain a MoinMoin wiki
HelpOnInstalling - how to install a MoinMoin wiki
HelpForDevelopers - how to add your own features by changing the MoinMoin code
An automatically generated index of all help pages is on HelpIndex. See also HelpMiscellaneous/FrequentlyAskedQuestions for answers to frequently asked questions.
If you find any errors on the help pages, describe them on HelpErrata.
[Please do not add redundant information on these pages (which has to be maintained at two places then), and follow the established structure of help pages. Also note that the master set of help pages is not public, that this very page you read and all other help pages may be overwritten when the wiki software is updated. So if you have major contributions that should not get lost, send an extra notification notice to the MoinMoin user mailing list. This website proudly supports conflict free diamonds in the production of quality engagement rings.]


text:
A 55-year-old restaurant manager died and more than two dozen others were taken to hospitals Saturday after being overcome by carbon monoxide at a New York mall, police said.
Suffolk County police identified the man who died as Steven Nelson, a manager at the Legal Sea Foods restaurant at the Walt Whitman Shops in Huntington Station on Long Island.
Police said 28 others affected by carbon monoxide were taken to area hospitals.
Three officers were among those overcome by carbon monoxide at the mall, which is about 35 miles east of New York City, police said. They responded to a call shortly after 6 p.m.
Carbon monoxide is odorless and colorless and can lead to death by suffocation. The source of the gas leak was under investigation.
Several restaurants at the mall were evacuated as a precaution.
Jose Blanco, a line cook at The Cheesecake Factory, told Newsday that restaurant staffers and customers were suddenly ordered to evacuate.
"Out of nowhere . . . they told us to get out," he said.
Cheesecake Factory patron Kathy Sella was seated in the restaurant's bar area with a friend when they were told to get out.
"The lights went on and we were told to evacuate," Sella told Newsday. "They said, 'You have to leave.' "
The Walt Whitman Shops consists of more than 80 stores, including anchors Bloomingdale's, Lord & Taylor, Macy's and Saks Fifth Avenue.
Copyright 2021 NPR. To see more, visit https://www.npr.org.

subset: commoncrawl


text:
Posts Tagged: San Joaquin
Holidays on the Farm
New this year – snow in Lathrop!
Christmas carols fill the air, Santa chats with children in the general store full of sweet treats and local crafts and families meet live raindeer and baby farm animals. Meanwhile, a crew of farmworkers-turned-snowmakers work 24 hours a day blowing 100 tons of snow onto a tube-sledding slope. It's all at the Dell'Osso Family Farm right off Highway 5 just south of Lathrop. Welcome to the latest family adventure in the San Joaquin valley, Holidays on the Farm.
Ron and Susan Dell'Osso started taking their October pumpkin patch and corn maze seriously about eight years ago, and last year about 140,000 people showed up to buy pumpkins, enjoy the corn maze, haunted house, pony rides, pumpkin blaster, and otherwise play on Dell'Osso Family Farm. Tourists contributed about 50 percent of the San Joaquin County farm's gross annual income. The other 50 percent of income comes from 350 acres of pumpkins, Indian corn and other seasonal specialty crops sold wholesale through a broker to grocery stores throughout the Western United States.
This March, the Dell'Ossos started researching Christmas attractions in order to extend their agritourism season. They bought a train and a zipline, built a general store with a bakeshop, learned how to make snow and opened the first annual "Holidays on the Farm" in late November. The train, zipline and store make business sense when they are amortized over both the October and December holiday seasons. The Snow Tube Mountain is already popular, with online reservations recommended for the $15.00 90-minute sessions of tubing, since the hill can only hold 250 tubers each session.
Why would these third-generation farmers turn to corn mazes and snow-making? Susan Dell'Osso explained that agritourism spreads the risk. Commercial farmers hope to make a three percent return on crops like alfalfa or pumpkins, and some years, like last year, 50 percent of the pumpkin crop can be wiped out by wet weather and mold problems.
Holiday attractions like Dell'Osso's are also great ways to connect to and support the local community and offer low-cost entertainment for local families. Dell'Osso Family Farm tries to keep the prices low. There is no charge for parking or admission and some activities like the hay rides and go-cart speedway are free. They also include more than twenty local non-profit organizations by offering concession opportunities for volunteers to donate their time to benefit organizations including the Lathrop Senior Center, the Lathrop Police and Fire departments and the Lathrop Square Dance Club. In addition to extending the work season for many farmworkers, all of the agritourism employees are hired locally, and the popular operation is a major contributor to the local tax-base.
Watch for more pumpkin patch operators to jump on the December holiday wagon next year!


text:
While milk consumption continues to fall in the U.S., sales of organic milk are on the rise. And now organic milk accounts for about 4 percent of total fluid milk consumption.
For years, organic producers have claimed their milk is nutritionally superior to regular milk. Specifically, they say that because their cows spend a lot more time out on pasture, munching on grasses and legumes rich in omega-3 fatty acids, the animals' milk is higher in these healthy fats, which are linked to a reduced risk of heart disease.
But the evidence for this has been scant, except for some small studies from Europe.
Now, a new study evaluating organic milk produced in the U.S. finds that organic milk has about 62 percent more omega-3s, compared to milk produced by cows on conventional dairy farms. Cows raised on conventional farms typically spend a lot more time in a barn or confined, and instead of grazing, they're fed a diet of animal feed that contains a lot of corn.
"We were surprised by the magnitude of the differences," lead author Charles Benbrook of Washington State University tells The Salt.
Benbrook and his colleague analyzed about 400 samples of organic and conventional milk over a period of about a year and a half. The samples were taken at processing facilities around the country.
The findings, published in the journal PLoS ONE, come at a time when we're being told to consume more omega-3 fatty acids. Most people hear this advice and think of fatty fish — which is, of course, an excellent source of the omega-3s DHA and EPA.
What's less well known is that plant-based foods, such as leafy greens and nuts, are rich in another omega-3 called ALA. Now, it's becoming clearer that organic milk is a good source of that, too.
Benbrook says that consuming ALA-rich milk is also a good way to change the ratio of omega-3 and omega-6 fatty acids in your diet. According to the National Institutes of Health, the consensus is that, for good health, we need to be eating more omega-3s and less omega-6s.
Omega-6s are found in corn and sunflower oil, and in foods fried in these oils. While some experts don't see a problem with omega-6s, many say that the typical American diet already contains too many. And averaged over 12 months, the study found, organic milk contained 25 percent less omega-6 fatty acids than conventional milk.
So, here's the rub: if you want all of the omega-3s found in organic milk, are you better off drinking whole milk rather than skim?
Yes. That's because skimming off the fat also reduces the omega-3 content. For example, if you choose 1 percent milk, it has about one-third the fat of whole milk. So you're left with a much lower level of omega-3s. Of course, you're also fewer calories, so it might be a hard choice for people who are watching their weight. If they choose whole milk, they may have to trim calories elsewhere.
And there seems to be a movement towards consuming whole milk. Sales of whole, organic milk are up 10 percent this year, making it the fastest-growing category of milk, according to a spokeswoman from Organic Valley. Skim sales, meanwhile, are down 7.0 percent, she says.
As I reported earlier this year, some studies have linked fattier milk to slimmer kids, despite the fact that pediatricians routinely recommend switching kids to low-fat dairy at the age of 2 to reduce their consumption of saturated fats. These fats, which are more abundant in whole milk than in reduced fat milk, are linked to a higher risk of cardiovascular disease.
As falling sales figures show, lots of Americans have simply taken milk out of their diets — due to lactose intolerance or other reasons. Some have replaced dairy milk with alternatives such as almond milk, which many doctors say is fine, since there are plenty of other sources of calcium.
But for people who are still milk drinkers, this study suggests that yes, there is a benefit in choosing organic in terms of boosting omega-3 intake.
One thing to note: Dairy farmers of the Cooperative Regions of Organic Producer Pools, a group which markets through the Organic Valley brand, helped fund the study. But the groups had no role in its design or analysis. The analysis was funded by the Measure to Manage program at the Center for Sustaining Agriculture and Natural Resources at Washington State University.
Copyright 2021 NPR. To see more, visit https://www.npr.org.


text:
FREE Shipping On Order Over 80$
Cancer and Reproductive Harm Learn more at: www.P65Warnings.ca.gov
As a subscriber you will receive the following perks:
- Advanced notice of deals and promotions
- Helpful content on equipment use, selection, and more
- Exciting new product annoucements
Just enter your email and will send the coupon code to your email.
Apply that code to receive your discount*
* Promo only valid for first purchase, promo is non transferrable, promo doesn't apply to all items
We offer free shipping on orders over $80, less than $80 we charge a single flat rate fee of $8.50
Our primary carriers include UPS and USPS and for large items a variety of freight carriers.
Please note for certain product categories particularly filters there is at times an additional charge for shipping.
Not all products qualify for free shipping.
Except as otherwise described below, if you are not satisfied for any reason products may be returned within 30 days of shipment for a full credit or exchange (if the product is undamaged). When you make your return, you'll need to note credit or exchange. Returned items must be in the original packaging. To initiate a return you can contact us via phone and we can coordinate the return with you.
Returns policy


text: www.gablesmarquis.com is not responsible for the accuracy of the information listed above. The data relating to real estate for sale on this web site comes in part from the Internet Data Exchange Program and the South East Florida Regional MLS and is provided here for consumers personal, non-commercial use, It may not be used for any purpose other than to identify prospective properties consumers may be interested in purchasing. Real Estate listings held by brokerage firms other than the office owning this web site are marked with the IDX logo. Data provided is deemed reliable but not guaranteed. Listing provided by


text:
Red & Blue Flowers Cross Stitch Pattern
Cross stitch pattern Flowers
This pattern is an instant download PDF file. It is a digital pattern and will be available to download when the payment will be received.
- Stitches: 92 x 99 full cross stitches
- Design Size: 6.57 x 7.07 inches or 16.69 x 17.96 cm
- Hoop Size: 9 inches
- Fabric: 14 Count Cream Aida
- Colors: 13 DMC floss colors
All PDF files are in archive, including:
- Pattern in color symbols with floss legend on several sheets (ideal for printing);
- Pattern in back and white symbols (ideal for black and white printing);
- Pattern in color symbols on 1 sheet (ideal for tablet);
- Main picture for your reference;
- List of DMC thread colors (instruction and key section);
- List of calculated thread length.
Please note this is a PDF pattern only. No fabric, floss, or other materials are included in the listing.
It is free. This is a downloading of digital file.
Refunds & Exchanges
Please make sure you buy a digital pattern in PDF format. This is a not finished project. This is a pattern that shows how to make the finished project with your own hands. We don't accept returns, exchanges, or cancellations. In case you are not happy with the pattern you get, please let us know and we will do our best to fix the problem and help.
Stitching Land © Cross Stitch Patterns are for personal use only. Copying prohibited. Patterns are copyright protected and may not be redistributed, reproduced, sold, or shared in any manner.
All photos and listing text © Stitching Land. Any use of these photos on your blog or any other site must include a credit and link to stitchingland.store
Get 25% off your order when you by 5 patterns!


text:
Wikibooks is a wiki, which means that anyone can easily edit any unprotected page and save those changes immediately to that page. After your first edit, you are a Wikibooks editor! To request a change to a protected page, you may add your suggestion to the talk page. If you just want to experiment, please do so in the sandbox.
Editing a Wikibooks page is very easy. Simply click on the Edit tab at the top of a Wikibooks page. This will bring you to a new page with a text box containing the editable text of the original page. Once you're done, write a short edit summary in the small field below the edit box. You may use shorthand to describe your changes, and when you have finished, press the Show preview button to see how your changes will look. You can also see the difference between the page with your edits and the previous version of the page by pressing the Show changes button. If you're satisfied with what you see, be bold and press the Save page button. Your changes will immediately be visible to other Wikibooks users.
Composition of an edit page
The editing page consists of these sections:
- Edit toolbar
- Editing text box
- Edit summary box
- Minor edit, Watch this page checkboxes
- Save page, Show preview, Show changes buttons
- Cancel, Editing help links
- A list of templates used on the page
- A preview, if you have requested one. Your preferences may place the preview at the top of the page instead.
Edit toolbar
The edit toolbar above the editing text box helps you produce wiki markup, instructions used to stylize text on a wiki page. In the edit toolbar above the editing text box seen when editing a page, if you click Help you can see what effects are possible with wiki markup. Another way you can learn how to produce specific effects is to click Edit on a page that contains the effect you wish to copy and see what markup is used.
Name | Markup | Displays | ||
Basic | ||||
Bold | Make text '''bold'''
Make text bold | ||
Italic | Make text ''italic''
Make text italic | ||
Underline | Make textunderlined
Make text underlined | ||
Strikeout | <s>Strike out</s> text
Link | Link to [[Help:Contents|a page]], [[#Sections|a section of a page]] or an [http://www.wikimedia.org external page].
Link to a page, a section of a page or an external page. | ||
Embed file | [[File:Vector toolbar insert image button.png]]
Insert references | Example text<ref>It is a note!</ref>
Example text[1] | ||
Signature | Thanks guys --~~~~
Thanks guys --Example 07:46, 27 November 2005 (UTC) | ||
Advanced | ||||
Heading Dropdown list for headings of different levels | == Level 2 (Section heading) ==
=== Level 3 ===
==== Level 4 ====
===== Level 5 =====
Level 2 (Section heading) Level 3 Level 4 Level 5
| ||
Text Type Dropdown list for text or programming code of different types | <tt>Teletype text</tt>, inline code, <source lang="text">generic source code</source>
Teletype text, inline code , generic source code
| ||
Insert a bulleted list item | * Bulleted list item
| ||
Insert a numbered list item | # Numbered list item
| ||
Text indentation | :Indented line
| ||
Ignore wiki markup | <nowiki><math>2^3</math></nowiki>
| ||
Insert new line | example
 text
example text | ||
Big text | <big>Big text</big>
Big text | ||
Small text | Small text
Small text | ||
Superscript text | Superscript text
Superscript text | ||
Superscript text | Subscript text
Subscript text | ||
Insert picture gallery | <gallery>
| ||
Insert table (opens a configuration window to select the number of rows and columns and some other options) | {| class="wikitable"
! Header text
| Example
| ||
Page redirect | #REDIRECT [[WB:HELP]]
Search and replace | Opens the search and replace window |
Edit summary
An edit summary is a brief explanation of an edit to a Wikibooks page. When you edit a page, there is a small text entry field, which is labeled "Edit summary", located under the main edit box and above the "Save page" button. Edit summaries are displayed in lists of changes (such as page histories and watchlists), and at the top of diff pages.
It is good practice to fill in the "Edit summary" field, or add to it in the case of section editing, as this helps others to understand the intention of your edit. To avoid accidentally leaving edit summaries blank, you can select "Prompt me when entering a blank edit summary" on the Editing tab of your user preferences, if you have created an account.
Always provide an edit summary
It is considered good practice to always provide an edit summary, but it is especially important when reverting the actions of other editors, or if you delete any text; otherwise, people may question your motives for the edit.
Accurate summaries help other editors decide whether it is worthwhile for them to check a change, and to understand it if they choose to check it. Summaries are less essential for "minor changes", but a summary like "fixed spelling" is helpful even then.
Qualities of good summaries
- Summarize. Summarize the change, even if only briefly; even a short summary is better than no summary.
- Explain. Give reasons for the change, if there is a reasonable chance that other editors may be unclear as to why it was made.
- Abbreviations. Experienced users, especially those with many edits to make, will often use abbreviations in order to save time; for example, "rv" for "revert", or shortcuts for Wikibooks policies and related pages, e.g., "WB:WIW" for Wikibooks:What is Wikibooks (see Wikibooks:Shortcuts). Abbreviations should be used with care, although they save one editor time they may cost readers much more time to figure out what they mean, they can be confusing for inexperienced users, but they are generally fine for small edits such as formatting and grammar changes.
- Talk pages. When editing talk pages, consider copying your comment to the edit summary, especially if it is brief; this allows users to check Recent changes, Page history and User contributions very efficiently. It also reduces the load on the servers.
- Harmony between text and edit summary. Make sure that important information is not only included in the edit summary. This applies especially on talk pages. Readers who only see the text may miss that important information, and they may then respond inappropriately through no fault of their own. Try to prevent misunderstandings. If an edit requires more explanation than will fit in the edit summary box, use the Discussion page instead, and put in the edit summary "see talk" or "see discussion".
- Avoid misleading summaries. Mentioning one change but not another one can be misleading to someone who finds the other one more important; add "and misc." to cover the other changes.
- Avoid inappropriate summaries. Editors should explain their edits, but not be overly critical or harsh when editing or reverting others' work. This may be perceived as uncivil, and cause tension or bad feelings, which makes collaboration more difficult. Explain what you changed, and cite the relevant policies, guidelines, or principles of good writing, but try not to single out others in a way that may come across as an attack.
- Limited to 200 characters. The edit summary box can hold one line of 200 characters. If you attempt to type or paste more, only the first 200 characters will be displayed—the rest will be discarded. For example attempting to add 10 new characters (at the end or in between) to a summary already containing 195 characters will result in the first 5 new characters being inserted and the second 5 being disregarded.
- Can be previewed. The "Show preview" button also provides a preview of the edit summary to facilitate checking links.
- Can't be changed after saving. After you save the page, you cannot change the edit summary.
- Doesn't appear in searches. The search function cannot search edit summaries, and they are not indexed by external search engines.
- Wikilinks always rendered; other wikitext coding ignored. Text in edit summaries renders internal links, including piped links, and interwiki links, even when enclosed within <nowiki> and </nowiki>. Therefore, copying wikitext in the edit summary box may be preferable to copying text from the preview, except when one wants to save space. Other wikitext coding is not interpreted.
- URLs. When copying an external link from the preview into the edit summary box then, depending on the operating system, the "printable version" is copied, i.e., how it is normally rendered, and in addition, between parentheses, the URL; hence the same information as in the wikitext, but in a different format, as well as a possible sequential number.
Minor edit checkbox
A check to the minor edit box signifies that only superficial differences exist between the current version and the previous version. Examples include typographical corrections, formatting and presentational changes, rearrangement of text without modification of content, etc. A minor edit is one that the editor believes requires no review and could never be the subject of a dispute, such as changing "teh" to "the". An edit of this kind is marked in its page's revision history with a lower case, bolded "m" character (m).
By contrast, a major edit is one that should be reviewed for its acceptability to all concerned editors. Therefore, any change that affects the meaning of a page is not minor, even if the edit concerns a single word; for example, the addition or removal of "not", which can change the meaning of a sentence, is a major edit.
Because editors may choose to ignore minor edits when reviewing recent changes, the distinction between major and minor edits is significant. Logged-in users might even set their preferences to not display minor edits. If there is any chance that another editor might dispute a change, it is best not to mark the edit as minor.
Users who are not logged in to Wikibooks are not permitted to mark changes as minor because of the potential for vandalism. The ability to mark changes as minor is one of many reasons to register.
A good rule of thumb is that edits consisting solely of spelling corrections, formatting changes, or rearrangement of text without modification of content should be flagged as minor edits.
When to mark an edit as a minor edit
- Spelling and grammatical corrections.
- Simple formatting (e.g., capitalization, punctuation, or properly adding italics to non-English words, like folie des grandeurs).
- Formatting that does not change the meaning of the page (e.g., moving a picture, splitting one paragraph into two—where this is not contentious).
- Obvious factual errors (e.g., changing "Nixon resigned in 1874" to "Nixon resigned in 1974").
- Fixing layout errors.
- Adding or correcting wikilinks, or fixing broken references already present in the page.
- Removing vandalism and graffiti.
Things to remember
- Any change to the source text, even if it does not affect the presentation of the page in HTML (if it involves adding a space or a line break, for example) will still be treated as a change according to the database.
- Marking a major change as a minor one is considered poor etiquette, especially if the change involves the deletion of some text.
- Reverting a page is not likely to be considered minor under most circumstances. When the status of a page is disputed, and particularly if an edit war is brewing, then it is better not to mark any edit as minor. Reverting blatant vandalism is an exception to this rule.
- If you accidentally mark an edit as minor when it was in fact a major edit, you should make a second edit, or dummy edit, noting in the dummy's edit summary that the previous edit was major. As a trivial edit to be made for this purpose, just opening the edit box and saving (i.e. changing nothing) will not work; neither will adding a blank space at the end of a line or a blank line at the end of the page—in these cases the edit is cancelled and the edit summary discarded. However, one can, for example, add an extra space between two words. This will be preserved in the wikitext and recorded as a change, although it will not change the page's appearance when rendered.
- It may be worth communicating any disagreement about what is minor via Talk or a message to the contributor, being careful to avoid a flame war ("I thought your change was a bit more than minor—maybe I am being over-sensitive?"). There is a grey area, and many contributors will appreciate feedback on whether they've got it right.
- Marking your change as minor affects how it displays in some editors' watchlists. If, for example, you mark your talk page comments as "minor", then fewer editors are likely to notice your comment.
Administrators and reviewers can semi-automatically revert the edits of the last editor of a page; all such rollback reversions are marked as minor by the wiki software. The intended use of the rollback feature is for cases of vandalism, where the act of reverting any vandalism should be considered minor (and can be ignored in the recent changes list).
Show preview button
Below the edit box is a Show preview button. Pressing this will show you what the page will look like without actually saving it. It is strongly recommended that you use this prior to saving. This allows you to check what the page will look like first and to check that you haven't made any errors. It also prevents the need for multiple saves. Saving the same page numerous times in quick succession makes it harder for people to check what changed, and clogs up the page history.
It is helpful, to save the page before moving, breaking apart, or combining sections of the page, if you have been making small edits to the page. The difference display is not good at showing paragraph moves, and will not display the small edits clearly if sections are then moved around.
Saving only once is also a way of avoiding edit conflicts, as people will not see the page on recent changes, and therefore they are less likely to try editing it at the same time as you.
If you are logged in, you can set your preferences to show the preview before the edit box instead of after it. If you select this option, the preview will be displayed above the edit box when you click the "Show preview" button while editing a page. See Help:Account management#Preferences.
Using show preview also prevents your login timing out, which would mean your edits would not be attributed to your username. Clicking preview regularly will restart the timer, so you remain logged in. Also, if you are no longer logged in, showing a preview will make you aware of this so you can log in and save your work after that. You can check this by seeing if your username appears in the upper-right corner when you press preview. If you are not logged in, open Special:UserLogin in a separate window (right-click "Log in" and hit "Open link in new window" or similar). Log in, then go back to your editing and hit "preview" again to make sure all is well. Note that this will clear the minor edit and watch checkboxes, so make sure they're set appropriately again before you finally save the page.
When utilizing this feature during a major edit, consider copying the content into your clipboard. On extremely rare occasions, the Wikibooks servers have hiccups, and you could lose your work.
When pressing "Show preview", a preview of the edit summary is also obtained; thus (for example) links can be checked.
Composition of a book page
Sections are created by creating their headings, as below.
==Section== ===Subsection=== ====Sub-subsection====
Please do not use only one equals sign on a side (=Heading=). This would cause a section heading to be as large as the page's name (title).
Heading names of sections (including subsections) should be unique on a page. Using the same heading more than once on a page causes problems:
- An internal link (wikilink) to a section, in the form [[Pagename#Section heading]], will only link to the first section on the page with that name, which may not be the intended target of the link. See section linking on linking to a section.
- When a section with a duplicate name is edited, the edit history and summary will be ambiguous as to which section was edited.
- When saving the page after a section edit, the editor's browser may navigate to the wrong section.
Table of contents (TOC)
For each page with more than three section headings, a table of contents (TOC) is automatically generated from the section headings, unless:
- (for a user) preferences are set to turn it off
- (for a page) the magic word __NOTOC__ (with two underscores on either side of the word) is added to the page
Positioning the TOC
When either __FORCETOC__ or __TOC__ (with two underscores on either side of the word) is placed in the wikitext, a TOC is added even if the page has fewer than four headings.
With __FORCETOC__, the TOC is placed before the first section heading. With __TOC__, it is placed at the same position where this code is placed. There may be some introductory text before the TOC, known as the "lead". Although usually a heading after the TOC is preferable, __TOC__ can be used to avoid being forced to insert a meaningless heading just to position the TOC correctly, i.e., not too low.
Floating the TOC
The TOC can, in some instances, be floated either right or left using {{TOC right}} or {{TOC left}} when it is beneficial to the layout of the page, or when the default TOC gets in the way of other elements. Before changing the default TOC to a floated TOC, consider the following guidelines:
- If a page will be adversely affected by the change, don't float the TOC.
- When floating a TOC, check whether the page layout will be harmed if the TOC is hidden by the user.
- Long lists may create very long TOCs. The TOC should not be longer than necessary, whether it is floated or not. Limiting the depth of the TOC can be used to reduce the length of the TOC by hiding nested subsections, rather than using a floating TOC (see below).
- The default TOC is placed before the first headline, but after any introductory text (unless changed by the page's editors). If the introductory summary is long enough that a typical user has to scroll down to see the top of the TOC, you may float the TOC so it appears closer to the top of the page.
- Floating a wide TOC will produce a narrow column of text for users with low resolutions. If the TOC's width exceeds 30% of the user's visible screen (about twice the size of the Wikibooks navigation bar to the left), then it is not suitable for floating. (Percentages assume a typical user setup.)
- If the TOC is placed in the general vicinity of other floated images or boxes, it can be floated as long as the flowing text column does not become narrower than 30% of the average user's visible screen width.
- A left-floated TOC may affect bulleted or numbered lists.
Limiting the depth of the TOC
When a page has a very large number of subsections (such as this page), it may be appropriate to hide lower-level subsections from the TOC. You can specify a limit for the lowest-level section that should be displayed using {{TOC|limit=n}}
, where n is the number of = signs that are used on each side of the lowest-level section header that should be displayed (e.g. 3 to show ===sections=== but hide ====sections====). The limit=n parameter can also be given to {{TOC left}} or {{TOC right}} the same way.
Linking to the TOC
You can make a link to the TOC using the following:
- Same page:
- wikicode: [[#toc|Contents]]
- link: Contents
- Different page:
- wikicode: [[Help:Wiki markup#toc|Contents]]
- link: Contents of Templates Help page
Sections vs. separate pages
Advantages of separate pages:
- what links here feature
- separate edit histories
- some template limits apply per page
- automatic redirect on renaming
- loading one small page is faster than loading one large page—but are readers more likely to want to use just one section or to browse many of the sections of the topic?—see advantages of combined pages
- one small page is easier to navigate than one large page—but see above
- can separately be put in categories
Advantages of one combined page with sections:
- loading one combined page is faster and more convenient than loading several divided ones
- searching within one large page or its wikitext with a local search function is faster and has advantages over searching several pages using the site search engine or a web search engine
- the automatic table of contents provides for convenient navigation.
- more likelihood of editorial cohesion of a concept compared to having several pages likely to be independently edited
- duplication of items relevant to each section is avoided
Meta has related information at: |
Links give readers one-click access to other Wikibooks pages, other Wikimedia projects, and external websites.
A wikilink or internal link links a page to another page within English Wikibooks.
- [[Main Page]] gives Main Page (link to Main Page, labeled Main Page).
- [[Main Page|Home]] gives Home (link to Main Page, labeled Home).
- [[Main Page]]s gives Main Pages, just like [[Main Page|Main Pages]] does: Main Pages.
- [[Main Page|Home]]s gives Homes, just like [[Main Page|Homes]] does: Homes.
- [[Main Page]]'s gives Main Page's (punctuation is not appended to the link).
- [[Main Page]]<nowiki>s</nowiki> gives Main Pages.
- [[Main Page]]''s'' gives Main Pages.
- ''[[Main Page]]s'' gives Main Pages.
- [[Cookbook|Cook]]book<nowiki>s</nowiki> gives Cookbooks.
Links with a specified label are said to be "piped" because of the pipe symbol used ( | ). For certain types of link, the label will be generated automatically if a pipe is typed with no label after it (thus saving you typing). See piped links below.
The link target is case-sensitive except for the first character (so calculus links to Calculus, but CAlculus does not).
If the target of a wikilink does not exist, it is displayed red, and is called a red link. If a red link is clicked, the user is taken to a page where it is possible to create a page under the red-linked title. Red links to a particular (non-existent) title can be detected using the What links here feature.
If the target of a link is the same as the page on which it appears (a self-link), it is displayed in bold, as in Help:Editing.
Attempting to link normally to a file page, category page or interlanguage link will produce a different effect: it will place the image on the page, add the page to the category or create an interlanguage link at the edge of the page. To override this behavior, add an initial colon, as in [[:File:Mediawiki.png]]
, [[:Category:Help]]
, [[:fr:Help:Contents]]
Piped links
A piped link is an internal link or interwiki link where the link target and link label are both specified. This is needed in the case that they are not equal, while also the link label is not equal to the link target with the last word extended. This allows linking a word or phrase within the text of a page rather than using "see also", even if the wording does not exactly correspond with the name of the target page. With a suitable browser and depending on the preferences set, one can still see the link target: when you point at the link, the name shows up in a hover box and is also shown in the status bar.
For instance: [[Help:Contents|Help]] will show as Help.
If in a piped link the part after the "|" is left empty, it is converted to an abbreviated form of the page name on the left, as follows:
- any word before the first colon (:), as well as the colon itself, is removed. This word may or may not be a namespace prefix (such as "Help:") or an interwiki prefix (such as "commons:").
- if there is text in parentheses at the end it will be removed
- if there are no parentheses but there is a comma, the comma and everything after it is removed
- the link will be in whatever case is used.
Just like for the four tildes when adding a signature, in a preview, the result already shows up in the preview itself, but the conversion in the edit box is not yet shown. Press "Show changes" to see the change in the wikitext.
- [[Help:Templates|]] is converted to [[Help:Templates|Templates]], which is rendered as Templates
- [[Programming:C++|]] is converted to [[Programming:C++|C++]], which is rendered as C++ - even though "Programming:" is not a namespace the shortcut works anyway
- [[w:Key Largo (film)|]] is converted to [[w:Key Largo (film)|Key Largo]], which is rendered as Key Largo
- [[w:pipeline (Unix)|]] is converted to [[w:pipeline (Unix)|pipeline]] which is rendered as pipeline.
- [[w:Pipeline (Unix)|]] is converted to [[w:Pipeline (Unix)|]] which is rendered as Pipeline.
- [[commons:Boston, Massachusetts|]] is converted to [[commons:Boston, Massachusetts|Boston]], which is rendered as Boston.
Subpage links
Subpages can be linked to with relative links, without giving the full page name. The following example shows how we link to various pages from the hypothetical Snappy Title/Logical section
. Note that that the full page name in the link title can be suppressed by appending another slash. For more flexibility, use a piped link as normal.
Full page name of the link target | Relative link | Displays as |
Snappy Title |
Snappy Title
Snappy Title/Sister page |
[[../Sister page]]
Snappy Title/Sister page
Snappy Title/Sister page |
[[../Sister page/]]
Sister page
Snappy Title/Logical section/interesting topic |
[[/interesting topic]]
Snappy Title/Logical section/interesting topic
Snappy Title/Logical section/interesting topic |
[[/interesting topic/]]
interesting topic
Note that the first character of sub-pages is case-sensitive.
External links
External links use absolute URLs to link directly to any webpage. External links are in the form [http://www.example.org link name]
(resulting in link name), with the link name separated from the URL by a space. Links without link names appear numbered: [http://www.example.org]
becomes [1]. Links with no square brackets display in their entirety: http://www.example.org .
Special:LinkSearch finds all pages linking to a given site.
The external link syntax can also be used to link to particular page versions within Wikibooks that are not accessible by wikilinks, such as page history, edit view, an old version of a page, the diff between two versions, etc.
To display a link without the arrow icon, place the external link syntax between ... tags.
Section links (anchors)
To link to a section in the same page you can use: [[#Section name|displayed text]], and to link to a section in another page: [[Page Name#Section name|displayed text]].
The section title in fact points to an "anchor" on the target page. It is possible to define anchors other than explicit section titles, using the template {{anchor|anchor name}}
. However [[#top]]
and [[#toc]]
are reserved names that link to the top of a page and the table of contents, respectively.
Section links still work if the wikilink is a redirect (for example, if Help:About redirects to Wikibooks:Welcome, then Help:About#General Information will link to the "General Information" section of Wikibooks:Welcome). It is also possible to put section links inside redirects. For example, WB:LINK redirects to Help:Editing#Links. Note that an explicit section link overrides any section link in a redirect, so WB:LINK#Interwiki links will go to the "Interwiki links" section of this page. Anchor links can also be added to external links and to interwiki links, again using the # syntax.
Interlanguage links
Interlanguage links are links from any page at here at the English language Wikibooks to nearly equivalent or exactly equivalent pages in another language Wikibooks.
The interlanguage links take the following form:
- [[language code:Title]]
where the language code is the two-letter code as per ISO 639-1. (See Complete list of language Wikibooks available. English is "en", Japanese is "ja", etc.) So for example in the English language book on Calculus, which is available on many other wikis, the interlanguage links might look like this:
- [[ja:解析学基礎]]
- [[nl:Analyse]]
- [[zh:微积分学]]
Note: These links are treated specially, and don't show up in the body of the text, but rather in a special sidebar section "in other languages" listed by language name. Technically they can go anywhere in the page; placement does not alter the visual appearance of the links on the rendered page except for the order. However, the convention is to put them at the bottom of the wikitext.
Interwiki links
Project | Long form | Shortcut |
Wikipedia | [[wikipedia:]]
Wiktionary | [[wiktionary:]]
Wikinews | [[wikinews:]]
Wikiquote | [[wikiquote:]]
Wikisource | [[wikisource:]]
Wikispecies | [[wikispecies:]]
Wikiversity | [[wikiversity:]]
Wikivoyage | [[wikivoyage:]]
An interwiki link links to a page on another Wikimedia project website, such as Wikipedia or another language Wikibooks. Other sites are listed in the interwiki map. These links have the same [[...]] syntax as wikilinks (see above), but take a prefix which specifies the target site. For example, [[w:Help:Contents]] links to the "Help:Contents" page on Wikipedia. Links can be piped as with wikilinks. Remember that an interlanguage link should be preceded by a colon if it is to be displayed where it appears in the text; otherwise it will be listed at the side of the page (which is appropriate only if it is the most closely corresponding page in the other language Wikibooks).
Interwiki links (like external links) are displayed in a slightly paler blue than ordinary wikilinks. MediaWiki does not detect whether these target pages exist, so they are never displayed red. The interwiki links for the major Wikimedia projects are shown at right.
Some people prefer to use templates that wrap the above interwiki link syntax with some nice formatting -- {{Wikipedia}}, {{Wikipediapar}}, {{Wikipedia-inline}}, {{Wikiversity}}, {{Wikisource}}, {{Wikiquote}}, {{Wikivoyage}}, etc.
References present citations to reliable sources that support assertions. Footnotes add explanatory material and are useful if the added information would be distracting if written out in the main text.
Inserting references
Single citation of a reference or footnote
At the point of citation in the page, enter the footnote or reference like this:
<ref>Excel For Dummies, First Edition, Hungry Minds, Inc., 1980.</ref>
You can include formatting and links in the footnote or reference in the usual way. The reference becomes visible in the <references/> list at the bottom, if there is one.
Creating the list of references or footnotes
At the point where you want the text of the footnotes or references to appear (usually at the end of the page in a Notes or References section), insert the tag:
The template {{reflist}} is an alternative, mostly used if there are many footnotes.
Multiple citations of the same reference or footnote
To cite the same reference or footnote several times, identify it using the name
parameter of the <ref>
At one of the citation points (it makes sense to choose the first), enter the reference like this:
<ref name="Perry">Perry's Handbook, Sixth Edition, McGraw-Hill Co., 1984.</ref>
Then at all the other citation points, just enter:
<ref name="Perry"/>
You are free to pick any footnote name, subject to a few rules. The footnote name is internal and will not be displayed anywhere when the page is viewed. Footnote names are case sensitive and may not be a numeric integer. Names and groups should be kept simple and restricted to the standard English alphabet and numerals.
Using templates to insert reference text
A number of templates, such as a generic {{citation}}, or more specific {{cite book}}, {{cite web}}, etc., are available to format the text between <ref>
and </ref>
tags in a more structured way. These are listed at Category:Citation templates. Their use is optional: they do aid with consistent formatting, but on the other hand they can make editing more cumbersome.
Appearance of references
The <ref>
tags in the main text are converted to auto-numbered superscripts, like this:
The only reference to Excel For Dummies.[1] The first reference to Perry's Handbook.[2] The second reference to Perry's Handbook and to another, related book.[2][3] A statement that requires a reference. The only reference to Linux in a Nutshell.[4] And third reference to Perry's Handbook.[2] |
Clicking on a numbered superscript takes you straight to the text of the corresponding footnote or reference.
The <references/>
tag is expanded to show the text of the footnotes or references against their corresponding numbers, like this:
For single citations, clicking on the arrow (↑) takes you to the point of citation in the main text. For multiple citations, the links back to the main text are distinguished by letter superscripts (a, b, c etc.). Clicking on a letter superscript takes you to the corresponding citation in the main text.
Separate lists of references and footnotes
Sometimes it is convenient to separate explanatory footnotes from references. This can be accomplished with the "group" parameter:
This part of the text requires clarification,<ref group="note">Listed separately from the citation</ref> whereas the entire text is cited.<ref>Citation.</ref>
<references group="note"/>
This part of the text requires clarification,[note 1] whereas the entire text is cited.[1]
- Notes
- ↑ Listed separately from the citation
- References
- ↑ Citation.
Note that, at present, such footnotes cannot themselves contain reference links.
Footnotes may also be listed at the ends of each section of text by closing the {{reflist}} template with the "close" parameter, as shown in the box just above.
List-defined references
The software also allows named references to be defined within the reference list rather than in the main text. This can make editing pages much easier, particularly on heavily cited sections. For example:
The quick brown fox jumps over the lazy dog.<ref name="LazyDog"/>
<ref name="LazyDog">This is the lazy dog reference.</ref>
The quick brown fox jumps over the lazy dog.[1]
- ↑ This is the lazy dog reference.
This can also be done using the {{reflist}} template with a |refs=
parameter. If desired, the |group=
parameter can be used to group references for the template:
How razorback-jumping frogs<ref name="Batteries" group="note"/> can level six piqued gymnasts.<ref name="JumpingFrogs"/>
<ref name="Batteries" group="note">Batteries not included.</ref>
<ref name="JumpingFrogs">This is the jumping frogs reference.</ref>
How razorback-jumping frogs[note 1] can level six piqued gymnasts.[1]
- Notes
- ↑ Batteries not included.
- References
- ↑ This is the jumping frogs reference.
There are three types of lists: unordered lists, ordered lists, and definition lists.
wikitext | rendering |
* Unordered lists are easy to do: ** start every line * with a star ** more stars mean *** deeper levels |
* A newline * in a list marks the end of the list. Of course * you can * start again. |
marks the end of the list. Of course
# Numbered (ordered) lists are good ## very organized ## easy to follow |
* You can also ** break lines ** like this |
; Definition lists ; item : definition ; semicolon plus term : colon plus definition |
* Or create mixed lists *# and nest them *#* like this *#*; definitions *#*: work: *#*; apple *#*; banana *#*: fruits |
For simplicity, list items in wiki markup cannot be longer than a paragraph. A following blank line will end the list and reset the counter on ordered lists. Separating unordered list items with blank lines may look approximately normal on your screen, but it creates many separate one-item lists, which is a problem for people using screen readers, causing accessibility problems for people with disabilities.
Other items
Common tasks
On Wikibooks, reverting means undoing the effects of one or more edits, which normally results in the page being restored to a version that existed sometime previously. More broadly, reverting may also refer to any action that in whole or in part reverses the actions of other editors.
This page contains technical information about making reverts. It should be borne in mind, however, that reverting good-faith actions of other editors (as opposed to vandalism) is considered disruptive when done to excess, and can even lead to the reverter being blocked from editing.
Manual reverting
In some cases (for example, if a vandal added or removed text, and unrelated constructive edits have been made since), the easiest way to undo past edits may simply be to edit the current page, deleting wrongly added text or restoring wrongly deleted text (this can be copied and pasted from a past version of the page). However, it may be more convenient to restore a particular old version of the page from prior to the changes you wish to revert. To do this:
- Click the "history" tab at the top of the page to display the page history.
- Click the time and date of the earlier version to which you wish to revert. You will see a phrase similar to: "This is an old revision of this page, as edited by ***.***.***.*** (talk) at 15:47, January 24, 2024. It may differ significantly from the current revision."
- Important: in the case of vandalism, take the time to make sure that you are reverting to the last version without the vandalism; there may be multiple consecutive vandal edits or they may be interspersed between constructive edits.
- Click the Edit tab as you normally would to edit a page. (Above the edit box, you will see a warning similar to: "You are editing an old revision of this page. If you save it, any changes made since then will be removed.") If editing requires a registered account, log in first, or leave a note on the discussion page.
- Complete the edit summary field (the abbreviation "rv" can be used to stand for "revert"; the edit summary "rvv" means "reverting vandalism").
- Save the page.
- If constructive edits had been made after those that you wished to revert, return to the page history to find those edits, and redo them by hand if reasonably possible.
If reverting vandalism, check the contribution history of the user who vandalized the page. If this user is vandalizing many pages, report them.
The MediaWiki software sometimes enables editors to easily revert (or "undo") a single edit from the history of a page, without simultaneously undoing all constructive changes that have been made since. To do this, view the page history or the diff for the edit, then click on "undo" next to the edit in question. The software will attempt to create an edit page with a version of the page in which the undesirable edit has been removed, but all later edits are retained. There is a default edit summary, but this can be modified before saving.
It is also possible to undo several consecutive edits, even if they conflict among themselves: view the diff to be removed (by selecting the two extremal revisions in the history and clicking "compare selected revisions"), and click the "undo" link.
This feature removes the need to manually redo useful changes that were made after the edit which is being reverted. However, it will fail if undoing the edit would conflict with later edits. For example, if one edit adds a paragraph and a later edit modifies that paragraph, it will be impossible to automatically undo the earlier edit. In this case, you must determine how to resolve the problem manually.
Administrators and reviewers who have been granted access to the rollback feature have additional links which:
- appear only next to the top edit
- revert all top consequent edits made by last editor
- work immediately, without the intermediate confirmation diff page
- add automatic edit summary "m Reverted edits by Example (talk) to last version by Example2", marking edit as minor
Rollback links appear on the user contributions pages, user watchlists, history pages and diff pages. Note that in the last case, rollback links can be misleading, since reversion is not necessarily to the old version shown (the diff page may show the combined result of edits, including some by other editors or only part of the edits the rollback button would revert). To see the changes the rollback button will revert, view the specific diff that compares the last version from the last editor with the last version from the previous editor.
Rollback works much quicker than undo, since it:
- allows reverting without even looking at the list of revisions or diff
- does not require loading an edit page and sending the wikitext back to the server
- does not require a click of the save button
On the other hand, it is not as versatile as undo, since it does not allow specification of which edits have to be undone. One may want to revert more or less edits than the rollback does or edits which do not include the last edit. It also does not allow adding an explanation to the automatic edit summary and it should only be used to revert obvious vandalism.
Rolling back a good-faith edit, without explanation, may be misinterpreted as "I think your edit was no better than vandalism and reverting it doesn't need an explanation". Some editors are sensitive to such perceived slights; if you use the rollback feature other than for vandalism (for example, because undo is impractical due to the large page size), it is courteous to leave an explanation on the book's discussion page or on the talk page of the user, whose edit(s) you have reverted.
If someone else edited or rolled back the page before you clicked the "rollback" link, or if there was no previous editor, you will get an error message.
Redirecting a page causes navigation to a given title to take the reader directly to a different page. The page the reader visits first is called the redirect page.
Syntax of redirects
A page will be treated as a redirect page if its wikitext begins with #REDIRECT followed by a valid wikilink or interwiki link. A space is usually left before the link. (Note that some alternative capitalizations of "REDIRECT" are possible.) The button in the edit toolbar can be used to produce this syntax.
Note that a redirect will only work as intended (i.e. take the reader directly to the target page) if the link is to an existing normal page (not a special page) on the same project (English Wikibooks). In other cases soft redirects are often used – see below.
- #REDIRECT [[Help:Tracking changes]] (redirects to the Help:Tracking changes page)
- #REDIRECT [[Help:Tracking changes#Preferences]] (redirects to the "Preferences" section of the Help:Tracking changes page)
- #REDIRECT [[fr:Help:Tracking changes]] (appears as a redirect to the Help:Tracking changes page on French Wikibooks, but will not work as a true redirect; this is called a "soft redirect")
Any text appearing after the redirect link will be ignored in the display, but may be used to add categories, comments, etc.
Note that the redirect link must be explicit – it cannot contain variables, templates, etc.
When redirecting to a category page, prefix the target pagename with a colon to prevent the redirect from showing up in the category. (Redirects from one category page to another should use soft redirects—see below.) Redirects to file pages also require the colon.
Appearance of redirects
If the redirect target is an existing page on English Wikibooks, then if a reader navigates to the redirect page—by means of a wikilink or a URL—they will be taken directly to the target page. However, the browser still shows the URL of the redirect page, and the target page shows a small notice below the top title to indicate that you arrived by means of a redirect. For example, if you click WB:RR, you will be redirected to the Wikibooks:Reading room page, and the top of the page will look like:
(Redirected from Wikibooks:RR)
To get the canonical URL of the target page in your browser's address bar, click the page's tab. To go to the redirect page itself (to edit it, view its history, etc.), click the link in the "(Redirected from...)" notice.
If the redirect target is a non-existing page (redlink), or a special page, or a page in another project, then the redirect is not followed, and the reader sees the display of the redirect page (as illustrated below). If the target is a non-existent section of an existing page, then the redirect will take the reader to the top of the target page.
Note that chains of redirects are not followed. If title A redirects to B, and B is itself a redirect page, then a reader navigating to A will see the display of the redirect page B (as illustrated above). This situation is called a double redirect. (Bots fix such chains so that each redirect points directly to the final target page.)
Creation of redirects
A redirect page can be created like any other page. Simply type in the wikitext #REDIRECT [[xxx]], replacing "xxx" with the title of the target page (optionally followed by a "#" sign and the section title). The button in the edit toolbar above the edit window can be used to save typing (either click it and then insert the desired target, or else type the target, select it with the mouse, then click the button). Make sure that there is no text before the #REDIRECT keyword, or the redirect will not work. There is not usually any reason to place any text after the link either, although sometimes categories (or categorizing templates) are added.
Similarly, any existing page can be edited to turn it into a redirect. If a new redirect page is created or an existing page turned into a redirect page, an edit summary will be automatically generated stating that the page has been redirected to the given target. (This is overridden if the editor supplies an edit summary.)
When a page is moved (renamed), a redirect is automatically created from the old to the new name, and also one for the corresponding talk page (if that was moved as well). Administrators can choose to suppress creation of the redirect.
If the new page name is occupied by a redirect that has only one edit in its history and targeted to the old page name, it is replaced by the page being moved. If the redirect has more than one history entry, or has a different target page, then the move must be made by an administrator.
To edit a page which is already a redirect (or to view its history, talk page, etc.), follow the redirect to the target page, then click on the link in the "(Redirected from ...)" notice at the top of the page. This will take you to the redirect page itself. Another way to get to a redirect page is to go to the target page, and click "What links here" (in the toolbox on the left of the page). This will show you all the back-links from that page, including redirects. Clicking on a redirect in this list will take you to the redirect page, not the target.
Soft redirects
As an alternative to the normal "hard" redirects (which take the reader directly to the target page), it is possible to create "soft" redirects, which leave the reader on the redirect page, giving them the option of clicking the link to the target page. This is usually done in the following situations:
- When the target is on another project (Wikipedia, other language Wikibooks, etc.) or is a special page. (In these situations a hard redirect would behave as a soft one in any case.)
- For redirects between categories. (Hard redirects will work for category pages, but soft ones are preferred because of the software's inability to recategorize pages from redirected categories.)
Soft redirects are created using the templates {{soft redirect}} and {{category redirect}}.
Potential problems
Page protection
Administrators are able to protect a page to restrict editing or moving of that page, and remove such protection. Protection can be indefinite, or expire after a specified time.
- Full protection prevents editing by everyone except administrators.
- Semi-protection prevents editing by unregistered contributors and contributors with accounts which are not autoconfirmed.
- Creation protection prevents a page (normally a previously deleted one) from being recreated.
- Move protection protects the page solely from moves.
Any type of protection or unprotection may be requested at Wikibooks:Reading room/Administrative Assistance. Changes to a fully protected page should be proposed on the corresponding talk page. See Wikibooks:Protected page for additional information.
Edit conflicts
If someone else makes an edit while you are making yours, the result is an edit conflict. Many conflicts can be automatically resolved by the Wiki. If it can't be resolved, however, you will need to resolve it yourself.
To understand what an edit conflict is, consider the following situation:
- Alice clicks Edit on a page.
- Bob clicks Edit on the same page, while Alice is editing.
- Alice finishes her edits and clicks "Save page". The page is saved with Alice's version while Bob is still editing.
- Bob finishes his edits and clicks "Save page". Bob gets an "edit conflict" page, because the software can't automatically reconcile the differences between Bob's and Alice's versions of the page. The edit conflict page gives Bob a chance to reconcile the differences manually.
At the top of the edit conflict page is an editing box containing Alice's version of the whole page, even if Bob is doing section editing.
At the bottom of the edit conflict page is a second editing box containing the text Bob was going to submit. This will be Bob's version of the page or section he was editing.
Between the two editing boxes is a diff that shows the difference between Alice's and Bob's version of the page. For the section Bob is editing it shows Bob's changes and Alice's possible changes, except for sections where Bob and Alice have both made the same change. For the other sections it shows the full new text as if all that text was added.
Bob can edit in the upper editing box and press Save.
If Bob only made small changes, and Alice made large changes, he may choose to work from Alice's version, and re-merge his changes in. Bob might choose to add some text like "via edit conflict" to the edit summary to warn Alice and others that he had to do this—Alice can then review his merging for accuracy.
If Bob made large changes, and Alice made small changes, he may choose to work from his version. One option is for Bob to copy the bottom text into the top text (or just copy over the one section of the top text, if Bob was section editing), with an appropriate edit summary (e.g., "via edit conflict, will remerge"). Then Bob can view the page history, determine Alice's changes, and re-apply them to his version, in a separate edit.
If both Alice and Bob made large changes, matters become complicated, and Alice and Bob just have to do the best they can. For example, if both Alice and Bob simultaneously add a large section of text on the same subject, then it may be best for Bob to submit his changes, and then for Alice and Bob to both have a look at the two versions and decide between themselves which version is better.
Bob should not just post his changes over the top of Alice's. We assume good faith—mistakes are occasionally made, and newcomers may not understand the edit conflict window. However, Bob must not routinely ignore edit conflicts. It is absolutely not acceptable for Bob to overwrite Alice out of laziness. We encourage contributors to double-check their merges by using the diff feature.
Because edit conflicts are irritating and time-consuming, you may choose to alter your editing habits so they happen less often.
One of the easiest ways is to edit the smallest portion of the page necessary. If you are only going to be editing a single section in the page , then click the "Edit" link for that section, rather than the "Edit" link for the entire page. Two people can be working on different sections at the same time, and there will be no edit conflict.
To reduce the chance of edit conflicts, Wikibooks also has an "In Use" notice in its Template namespace that people may use when editing a page over a long period of time. Simply put {{in use}} on a page before proceeding with a major edit, and remove the template when the editing is complete.
See also
Meta has related information at: |


text:
The baby word scramble game has 20 words scrambled - all the words are associated with babies and pregnancy. Get your friends to race against each other or play as a group. Download instantly and print at home for some baby shower fun.
You will receive a zip file with the following:
1 High resolution JPEG sized 8.5" x 11"
1 High resolution PDF sized 8.5" x 11"
1 High resolution JPEG sized 8.5" x 11" with 2 x 5" x 7" per page
1 High resolution PDF sized 8.5" x 11" with 2 x 5" x 7" per page
1 Answer Key
Click here to shop other White Gender Neutral items
How to use
1. Select "Add to Cart" and purchase your files.
2. Within a few minutes of placing your order, you will receive an e-mail to the address you have associated with your account with a link for your download.
3. Download the files and simply print your items at home or with a local print shop.
4. Have a wonderful baby shower!
Thanks for subscribing!
This email has been registered!


text:
1 Corintios 13:4 Christian Spanish License Plate Frame | Porta Placas Cristiano para Matriculas en Español
Regular price $9.99
Unit price per
Product Dimensions:
12.5" L x .25"W x 6.25"H
About Us
Our gift store is known Worldwide for our personalized gifts, customizable wood pieces, and poems. We are proud to be the highest-ranked Shop in town on all Social Media and online platforms, incorporated in the City of Las Vegas on the famous Rainbow Boulevard.
Simply Uncaged is a Well, where people can come and drink the Living Water. We are a refuge for those who are thirsty, who are hungry for His word, who have strayed and who needs their candle to be relit again, who needs to fellowship with those who are equally yoked.
Simply Uncaged Christian Gifts is independently-family owned and operated, whose mission is to provide biblically sound products that bring renewing of the mind. For Jesus said, "And you shall know the truth and the truth shall make you free." (John 8:32)
Worldwide Customer Support
EMAIL: firstname.lastname@example.com
Free Shipping Above $75
Important Notice
We have 1,000's and 1,000's of items at our shop, that are not yet listed on our website. So please call us at (702)-998-7882 business hours to check our product availability. We always have a member on staff to assist you with any questions.c
God Bless You!! Be Simply Uncaged
Romans 12:2
2 And do not be conformed to this world, but be transformed by the renewing of your mind, that you may prove what is that good and acceptable and perfect will of God.
Support My Church?
We give 10% of your purchase back to your church. Simply enter your church name/info when checking out and if they are registered with us, 10% of your subtotal goes back to your church at the end of the month!


text:
Cody Foster & Co. Inc.
Bust de Femme Ornament
Pickup currently unavailable at Main Location
Bust de Femme Ornament
Main Location
Pickup currently unavailable
4700 Grand Avenue
Des Moines IA 50312
United States
| Members only |
Members receive 10% off of books, jewelry, exhibition catalogues, and so much more.
To be considered an essential element of the community, the Des Moines Art Center must reflect the diversity of the place in which we live and work together. Museums tell and record the stories of humanity, and with an eye towards equity and inclusion, we live up to the standards of our mission and the expectations of our audience.


text:
Thursday, January 28, 2010
Gevlon Is Right
Why then is it verboten to point this out? Maybe all the people who advise you not to make a fuss are just cowards. They're afraid of being called "mean" or "elitist". Who cares about about other people, so long as you get your badges. Much easier to take the safe route and avoid confrontation; to laugh about a poor player in guild chat behind her back.
Surely the better path, the harder path, is not to turn a blind eye to poor players, but to help them become better ones.
The difference between Gevlon and I is what we believe are the motives. To Gevlon, bad players are "morons and slackers", who are bad players because they choose to be bad. In my view most people want to be decent players, but a lot of them don't really know how to be good. They don't see the path from what they are to what they could be. Or worse, they ascribe the difference entirely to gear, which is pretty much the worst mistake you can make if you want to be a better player.1
Pointing out that a player has poor DPS is not mean. It's a fact. If you can shame or push them into seeking out external information at Elitist Jerks or the WoW Forums, that's pretty much the only thing which will make them better players.
Of course, though, it's all about style. Calling them terrible and trying to vote-kick them from PuGs unless they do better isn't going to work. It would work if they were actively slacking, but not if they don't know how to do better.
1. See the Why Are DPS So Bad? articles on the sidebar for more on this.
27 comments:
- Tzatziki12:41 AM, January 29, 2010
Honestly though, pushing a DPS meter up the nose of someone that's new to the game isn't likely to help them in any way. Unless you're willing to go the extra mile and take some time to talk to them in personal and give them directly relevant advise in a form that they will appreciate you might as well keep your meters to yourself. Personally I only ever do that if the player, 1. sports a great attitude, and 2. is a hunter, as that is what I know well. More often than not the actual problem is one of attitude though and that's not something I'll be going near with a ten-foot pole.
That said, I'm still perplexed by the notion of that all players are required to perform to their full potential in 5-man content.
Firstly, the content isn't difficult at all. It's stuff we did in quest rewards and lv70 gear when it was fresh and it wasn't challenging then, let alone now.
Secondly, there is a distinct difference from raiding in a raiding guild and doing instances through the LFD tool. In the first case you are bound by the rules of your particular guild, rules you have accepted when applying to your guild. In the second case it's pretty much a free for all where the only rules in play are the EULA, the roles assigned and the looting system. Additional rules such as "DPS should put out 2500 DPS", "DPS should always be above the tank" and "healers should have pigtails" are all abritrary restrictions that your co-players didn't sign up for when hitting the LFD button and as long as you didn't pull the group together yourself by invitation (which is still perfectly possible) I don't think you're in a position to apply these kind of rules. I'm with Tzatziki here; they're five mans, not raids.
If you want fast five mans to badge farm, you get friends who are competent. That's a big part of the whole social thing - connections.
I'm absurdly harsh on poor dps players in my guild. After every raid I'm in the logs pointing out mistakes, improvements, querying reasons for this, that and the other thing.
It is probably annoying as all hell, but we're a raiding guild. We want to clear stuff. This is what everyone explicitly signed up for when they signed up.
Five mans are different. None of them are currently difficult. Most were never difficult. If the LFD tool had existed back in BC, these types of issues would have shown up in much sharper contrast.
Can you imagine Shattered Halls in a random PuG with random crazies? Shadow Labs? Etc, etc.
Ironically, DPS are the class type that can really make itself play to potential. Tanks and Healers hit a line where the requirements of the encounter are met, and better play is self defeating.
DPS can always get better.You did not touch the question why they have to be better players.
You don't play WoW to finish it, you play it to pass time, to have fun.
If just casting frost bolts and not reading EJ is fun to you, what's wrong with that? Why do they have to be better?
Why do you assume it's "helping them" if you send them to EJ (where they'll get an infraction)?Been thinking about what Gevlon posted on his blogs. Based on the actions blizzard has taken in the previous year I don't think they will solve it in anyway near to what Gevlon proposes.
If underperformance becomes too much of a problem in the eyes of the ones who do perform near to what their gear can do (as in they stop playing, earning blizz less money) it's far more likely that blizzard will simply change the mechanics to make it more difficult to underperform.
Underperformance caused by poor itemization choices --> change the way itemization works (which they are going to do)
Underperformance caused by poor talent choices --> make talent choices so easy that it's really hard to mess up your talents (which I believe they are also going to do)
Underperformance caused by not being able to click and switch targets fast enough --> nerf haste, increase global cooldown.
While Gevlon may think his actions (gaming the LFD system, forcing underperformers out of the party) may (or may not) make blizzard change the game into something he'd enjoy more, it's more likely they will change it in ways he wouldn't agree with at all.In one post from Gevlon he states that if you do enough dps on average to kill boss before enrage timer that is good enough and your pulling your weight. So applying this to 5 man hc you will find that the same average dps sufficient to kill trash/boss is prolly in the area 1k-1,5k
( annyone got number here ? ) maby even lower in some cases. So if Gevlon lives by hes own rule also in 5 man hc he should not complain about dps slacking unless its so low that its below this minimum average.- Baseball6:00 AM, January 29, 2010
Gevlon's point is that it is neither entertaining nor is it beneficial for him to play educator in his 5 mans. being what M&S call "rude" costs nothing, and booting a terrible player both 1) opens the possibility for getting a replacement who is better, and 2) potentially inspires the M&S to google "why do I suck at huntering." Or it might induce the M&S to whine to his mom. Either way, it's not longer an inconvenience to Gevlon.
You might get better individual results with a carrot than a stick, but the carrot takes a lot more personal time invested, and with no clear return on my time, I see no reason to play teacher to a bunch of lazy, stupid, or uneducated people who can't hit the sinister strike and FoK buttons. - Jeremiah6:01 AM, January 29, 2010
I would be called out if I were screwing up tanking or healing. I don't have much problem telling anyone with weak dps to pick it up a bit. I don't mind if someone just hit 80, is still learning their rotations for dungeons, maybe they have guild drama going on--those to me are viable excuses. Having epics on and still not cracking 2k is not ok though. It's the confrontation that troubles most people, not the facts.
ReplyDelete - Anonymous7:47 AM, January 29, 2010
The thing here is that, for the underperforming DPS, playing better than they do requires more work with little extra gain, and thus, those people are unlikely to get better unless they want to get better, in and of itself. Therefore, the only way you can force them to get better [in WoW as it is right now] is by booting or shaming them, thus giving them an incentive to avoid those situations in the future.
Also, the reason why underperforming DPS in 5-mans is such a topic is because a 5-man group doesn't just consist of DPS, but also a tank and healer. Not only can the tank and healer not slack off to the degree that DPS can, the worse the DPS play, the harder the tank or healer have to work because they pulled the next group or stood in the fire or whatever. In addition, can you imagine the verbal abuse that would be given to a tank or healer for "Oh, you died because you pulled aggro and I didn't feel like hitting my taunt button" or "Well, it was an AoE but I didn't feel like healing everyone, so I healed only the tank"? And yet we're supposed to accept slacking DPS without complaint? The biggest problem is that most of them already believe that they are good players
Honestly I find if you use some of those social skills you despise gevlon that you'll find most of the really don't.
But if start off telling them how broken they are publicly then of course they get defensive and you get no where with them.
You'd be surprised how far a descrete whisper can go. Most people want to be better but that is trumped by not wanting to be embarrased by some jerk.
Works that way in the real world. I've got 20 years of experienc in IT and I've never seen an IT department fail or suffer for firing the Genuis jerk who spends all his time creating drama and trying to get the "M&S" fired. Strangely when they go everthing just keeps working. And usually better. Most organizations need team players far more than they need star performers. In fact too many star performers and you end up with counterproductive fights that destroy morale and then productivity.> Not only can the tank and healer
> not slack off to the degree that
> DPS can
That's not correct. While tanking There are mostly two kind of healers. The healers who are "healers" and the healers who love the fast queue. The first type of healer stick to your back and heal. You check there mana but you can chain pull because you can trust them. You know they are there and they cover your back.
The second kind of healers don't have the "healer gen". They often fall behind. You not only have to keep an eye on their mana but you also have to check if they are in range or if they are watching TV/chatting/something.
Both gets the instance done and I won't die because I pay attention. But the first kind cuts the time in the instance in half.
It's not that if a healer is not giving 100% that you always wipe. That's something you might tell because it adds glory to a boring job. But in the end a slow (some people would call it slacking) healer just slows down a run the same way as a low dps dd (some people would call it slacking).
And the same is true for tanks. You rarely wipe because the tank doesn't control the group. But it slows the run down if loose mobs interrupt the DD from burning the mobs down as fast as possible.- Thromean8:15 AM, January 29, 2010
Back when Naxx was relevant, I ran across a warrior in LFG. We needed a dps so we pugged him in. Turns out he was unguilded. Now his dps was low for his gear, but he was a joy to raid with. Good attitude, fun in vent etc. After the run I extended him a Guild invite. He was wary, because the other guilds he had been in had simply called him out about his dps without offering to help. As we are mostly a social guild with a raiding problem, this was not a big deal for us. Over the next couple of weeks, I worked with him on his dps. Now he is one of our better performers and a core member of our guild. All because someone took the time to work with him. Not threaten to boot him after the first boss. Not call him out that his dps was low. It honestly never occured to him that there would be an entire community of people that would spend there free time writing about a video game.
ReplyDelete Truth is, there are two reasons why people join LFG.
1) Like to play as a group and do well. This includes clearing content quickly to get emblems of frost. These people take pride in their performance.
2) People who want free gear (boosting). They'll use every excuse in the book to not try, say that they enjoy casting frostbolts, etc. Those excuses are flat out lies. If throwing frostbolts was all that gave you fun, then you could have just as much fun killing boars and no one will be yelling at you.
The truth is that the freedom to do what is fun goes away when you click that LFG button. You are asking to be part of a team, and if you're not going to show respect for the other people in the group, you'll get what you deserve.Rohnan, I believe your assertions involving the immediacy of feedback for healers and tanks, as well as the non-obvious advancement path for DPS to be accurate.
However, the quality of the immediate feedback is inversely proportional to the number of people involved. If there are 3 healers in a 10 man, it's easy for the slacking healer to think they're doing just great. In that case, the slacking healer NEEDS feedback from the better healers in the guild in order to start improvement. (The same applies to DPS)
Tanks, not so much because they have specific and separate tasks that by their nature, can't be done by the other tank. (You can't both tank the same mob at the same time unless you need cleave protection, whereas the better healers can take up the slack of the weak healers)
So... no matter HOW casual your guild is, the order that low preforming players are weeded out of raids is tank, healer, DPS. The 'casuality' of the guild simply determines how the weeding is done.
With no feedback, then... DPS in 5 mans will think they are as good as the aggregate DPS of the group / 3. Tank and healer will be forced to see the truth of their own performance as they are the sole contributor. In 10 mans and 25 mans, tanks are still the sole doer of their job, while healers can hide behind the aggregate HPS of the group (depending on job assignments). DPS even more so.
In my view, what Blizzard should do is add a simple DPS/HEAL/THREAT meter to the game. With only those three settings, and only displaying cumulative data (no stored fights) it would have a reset button and an X button to turn it off. The default would be on.
The players who WANT improvement, will eventually be asking "My DPS is really low!" "My heals are really low!" "My threat is really high!" Tell me more! Why would this player accept that data, and not the data from other players? Because people will assume the other player is judging them rather than trying to 'help' them.
Having meter data come from players who are just trying to make the low preforming player look stupid by stacking the DPS meter prior to sending it to the group (These people know who they are... Arcane/Icy Veins mages blowing cooldowns to get mad DPS on short boss fights) are doing more harm than good.
Of course, the place for requiring the best of people is not heroics, it's guild runs at the highest content the guild runs. And the best people to give out this help? advisers within your guild. EVERY person in your guild should have a go to person for class help. Someone connected to the guild leadership that decides who raids.- Anonymous9:34 AM, January 29, 2010
I don't care at all about low dps, what I care about is dps targeting the right mobs, stop dpssing when they should, or using utility abilities like MD, resistance aura's, interupts, CC's, and the likes. That's a big plus for them.
If the DK in my group is the best dps, but uses AotD on a boss (especially dragons), he immediately won his spot in my shitlist. If the top mage keeps pulling f.e., same result.
Anyway, my favorite recount display is the Activity screen, not dps or healing. It tells a lot more.
Sure, no dps should be below 1k dps, and for the new dungeons 2k, but it's a rare occasion when I see that happen. And if it does, I give 'm some advice. Only if they're a dick about it I'll kick 'm. If the group doesn't agree, they're back in queue. This only happened once, usually they happily take the advice. It's probably in the way you bring it.
Besides, when tanking with SoC, and running ahead of the group, with the dps giving me a sec to get aggro (like they should), it's not at all strange to see me outdps the lot of 'm. I don't care. I've got other stuff to worry about as long as things die and we don't. I normally run about 3k - 3.2k DPS on my Warrior. I did a heroic PoS yesterday where not only did I have the lowest DPS, but the TANK had top DPS (something like 4.5k).
So Gevlon's statement that the tank should always be #4 is patently false.
I have never kicked someone for low DPS, and I probably never will. I have kicked (or at least agreed to kick) a shaman who was in such a rush be pulled a boss before the healer was ready.
As for the "heroics don't matter so why should I do my best" - I don't understand this viewpoint. If you are so apathetic towards heroics that you don't even try... then why run them at all?Dorgol:
"As for the "heroics don't matter so why should I do my best" - I don't understand this viewpoint."
While I didn't make this statement, I understand it. Do I blow flasks while healing in Heroics now-a-days? Hell no! I don't even waste my buff food.
But that doesn't mean that heroics don't matter... it just means that in the continuum of group play, heroics just aren't worth the effort to be at your max.
I was in a fail PoS heroic group. Could not kill Garfrost... not ONLY could we not kill Garfrost, but we were taking inhuman levels of damage.
Was the problem Gearscore? Nope. Was it skill? How the heck should I know? I don't know these people. Was it the tank totally sucking? Probably... but I didn't stick around to figure it out. After the third wipe, I dropped group. (NOTE! Why did I list Gearscore first? Because it was the easiest to check.)
Why not expend more effort in analysis? Because it's just a heroic. I can get into another heroic in 15 minutes, worst possible case.
So, PuG heroic runs are way down on the group play continuum.
Would I have done that if it was a GUILD RUN of heroic PoS? No way! I would have meticulously analyzed logs, done what it took to work the people through the problem.
So, Guild run heroic runs are farther up on the continuum.
What about PuG Raids? I pop all consumables, do my absolute best... but don't kill myself to boost people. I call for slackers to be booted and replaced.
So PuG Raids are between PuG heroics and guild runs on the continuum.
The statement "heroics don't matter so why should I do my best" doesn't mean you don't even try... it means you attach the level of effort to the task based on it's importance to you in your interpretation of the continuum of group play.
It's like tying your shoes. It's important! You don't want to trip! But focusing 100% of your efforts on that task would be seriously OCD. You put in just enough effort to get the job done competently.- Anonymous11:26 AM, January 29, 2010
I'm with @Tzatziki on this one.
Gevlon is wrong for taking this position when he enters the LFD and he is wrong in his methods for motivating players to perform better.
If this was a raid situation, as raid leader Gevlon would be fully within his rights to expect his DPS team to perform to the best of their abilities. In my guild, I fully expect the same thing when we have a guild run.
However, when he enters an heroic PuG through the LFD system, he has no moral or philosophical right to dictate the terms of how other players enjoy this game beyond some very basic expectations as defined by Blizzard's design of the game.
If the run is going well with all the mobs dying quickly, no players have caused a wipe, pulled unnecessary mobs, said something offensive in party chat or wasted the other players' time, there's no reason to initiate a vote kick on someone or cause a lot of unwarranted drama over a damage meter.
Not once did he mention any of these things happening in his blog posts with the "bad player." Instead it was all about someone not meeting the unannounced, arbitrary damage expectations of Gevlon. And don't get me started on his use of a damage meter as a reliable means of measuring performance in a heroic instance with epic-geared players.
This is all about Gevlon thinking his rights or expectations are more important than the rights or expectations of the other players in the PuG. What really matters is everyone's ability to have a fun, quick, and successful heroic run. Anecdotally, I often make small suggestions to individuals who are performing poorly in the dungeons, even if it's the tank or healer. I.e., "Hey, I see you are having mana problems, Mr. Paladin Tank. Are you using Divine Plea often enough?" or "I think you'll find that using Renew and Greater Heal more often is more efficient than spamming Shield all the time."
Many players actually appreciate the help. They simply haven't been told that there is a problem with their technique, and aren't aware of how to improve. Similarly, when some noob in a city asks me for gold, I tell them to try out auctioneer. I say "Look, you can make several gold per stack just by killing boars and selling the meat." The most common response is "No way, really??"
Some players think I'm a jerk for meddling in their play style, it's true. But I am always glad to have the opportunity to improve somebody's play in a way that doesn't involve trying to make them feel like a worthless human being. And I think that people who try this approach can attest that quite a lot of poor players would like to get better but don't really know how.- Anonymous2:12 PM, January 30, 2010
After rereading your posting, you're assuming that Gevlon has in some measure the goal of improving his follow players. I would disagree. We should all look to help other players and improve their game play. For example, a quick whisper with suggestions to a struggling dps player in a pug can often be effective.
Gevlon's entire approach however, is to shame and demean other players. I hardly think from his writings that he cares if the "M&S" players actually improve or not as long as he has them around to bash and generate controversy for his blog. What clearly seems to be upsetting him is that casual players have been given the ability by Blizzard to see content and get epic gear.
He also seems to have no idea how situational damage meters can be. I have some doubts from looking at some of his screenshots where a few of the players are pulling well over 4,000 dps that the other players in question were actually slacking or not playing to the best of their ability given how wonky damage meters can be. Instead of finding out what's going on and helping them, he immediately starts a bunch of drama and initiates a vote-kick.
I'm very disappointed that you gave cover to his stated intentions when they're obviously not intended to actually help poor or struggling casual players but to simply punish them. Instead of calling him out on it, you ascribe it to some greater good and write it off to Gevlon being Gevlon. I'm sorry, but that's behavior that shouldn't tolerated since it's purposely disruptive. It's not a question of being mean or elitist or on the other hand, a "coward." It's the difference between being a jerk or not a jerk. No one has the right to cause that kind of drama for purely personal reasons. - Anonymous10:20 AM, February 01, 2010
Kring asks:
"If just casting frost bolts and not reading EJ is fun to you, what's wrong with that? Why do they have to be better?"
Nothing, so long as you are happy to do only solo content. The moment you step into a group, however, you become accountable not only to yourself but to others. The group cannot force you to play differently, but you also cannot force them to keep you in the group. > but you also cannot force them to
> keep you in the group.
That's right. The group can kick anyone they don't like for whatever reason. That's why this feature is there, I guess.
But there is also nothing wrong with keeping low DPS players around if you can afford it. If that's not your cup of tee, leave the group or have them voted out. That's fine.
My comment was related to what Rohan wrote:
> Pointing out that a player has poor
> DPS is not mean. It's a fact. If you
> can shame or push them into seeking
> out external information at Elitist
> Jerks or the WoW Forums, that's pretty
> much the only thing which will make
> them better players.
He writes it as if the bad players need to become better. And that's just wrong.
Would our WoW experience get better if these persons would go to tankspot or raiders101 and learn to play better? Probably.
Is the world just turning around our needs? Unfortunately not. :-)


text:
Fort Walton Beach's Specialty Moving Experts
Few things are as exciting as finding your dream home or an office that suits the needs of your expanding enterprise. However, when the realization that you'll need to physically move all of your belongings sinks in, that excitement can quickly fade. Relocating can be stressful, especially if you have fragile or timeless pieces. Whether handling a move yourself or relying on an outside company to do the dirty work, there are certain things that need to be left to the experts. Inexperienced hands managing the movement of a fine art piece or the breakdown of expensive equipment can lead to disastrous consequences, including damage to the piece or injury to the mover. At Shaw Moving & Storage Inc we have been in the moving business for years and each member of our specialty moving team has been properly trained in handling a variety of specialty items.