Template:Use mbox
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [1](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [2](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [3](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [4](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [5](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [6](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [7](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [8](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [9](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [10](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [11](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [12](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [13](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [14](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [15](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [16](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [17](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [18](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [19](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [20](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [21](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [22](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [23](https://www.investopedia.com/terms/b/bullmarket.asp) and [24](https://www.investopedia.com/terms/b/bearmarket.asp)
Template namespace` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [25](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [26](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [27](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [28](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [29](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [30](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [31](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [32](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [33](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [34](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [35](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [36](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [37](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [38](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [39](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [40](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [41](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [42](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [43](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [44](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [45](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [46](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [47](https://www.investopedia.com/terms/b/bullmarket.asp) and [48](https://www.investopedia.com/terms/b/bearmarket.asp)
Template namespace` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [49](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [50](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [51](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [52](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [53](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [54](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [55](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [56](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [57](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [58](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [59](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [60](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [61](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [62](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [63](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [64](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [65](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [66](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [67](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [68](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [69](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [70](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [71](https://www.investopedia.com/terms/b/bullmarket.asp) and [72](https://www.investopedia.com/terms/b/bearmarket.asp)
Template namespace` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [73](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [74](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [75](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [76](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [77](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [78](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [79](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [80](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [81](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [82](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [83](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [84](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [85](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [86](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [87](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [88](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [89](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [90](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [91](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [92](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [93](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [94](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [95](https://www.investopedia.com/terms/b/bullmarket.asp) and [96](https://www.investopedia.com/terms/b/bearmarket.asp)
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [97](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [98](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [99](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [100](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [101](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [102](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [103](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [104](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [105](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [106](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [107](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [108](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [109](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [110](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [111](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [112](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [113](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [114](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [115](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [116](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [117](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [118](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [119](https://www.investopedia.com/terms/b/bullmarket.asp) and [120](https://www.investopedia.com/terms/b/bearmarket.asp)
Template namespace` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [121](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [122](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [123](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [124](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [125](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [126](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [127](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [128](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [129](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [130](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [131](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [132](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [133](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [134](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [135](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [136](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [137](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [138](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [139](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [140](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [141](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [142](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [143](https://www.investopedia.com/terms/b/bullmarket.asp) and [144](https://www.investopedia.com/terms/b/bearmarket.asp)
Template namespace`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`
- Template:Use mbox
Template:Use mbox is a crucial element for maintaining consistent and informative messaging across a wiki regarding potentially problematic content, specifically content flagged for deletion or needing improvement. This article provides a comprehensive guide to understanding and effectively utilizing this template, targeting beginners with no prior experience in MediaWiki templating or content moderation. We will cover its purpose, syntax, parameters, common use cases, best practices, and troubleshooting tips. Understanding this template is vital for anyone contributing to or moderating a wiki, as it directly impacts the quality and reliability of the information presented.
What is Template:Use mbox?
The `Template loop detected: Template:Use mbox` template is a standardized message box system used to display notices related to the status of a page. Unlike simple text warnings, `Template loop detected: Template:Use mbox` offers a visually distinct and categorized way to communicate issues such as:
- **Deletion Proposals:** Indicating a page is nominated for deletion.
- **Content Disputes:** Highlighting disagreements about the content's accuracy or neutrality.
- **Copyright Concerns:** Flagging potential copyright violations.
- **Maintenance Tasks:** Requesting specific improvements, like adding citations or expanding sections.
- **Policy Violations:** Alerting users to breaches of the wiki’s rules.
The template’s strength lies in its consistency. By using a predefined structure, it ensures that all warnings and notices are presented in a uniform manner, making them easily recognizable and understandable for all users. This avoids confusion and promotes a more collaborative and transparent environment. It integrates seamlessly with other wiki features like watchlists and recent changes, ensuring that relevant users are notified of these issues.
Syntax and Parameters
The `Template loop detected: Template:Use mbox` template utilizes a specific syntax with several parameters that control its appearance and message. Here's a breakdown of the key parameters:
- **`type` (Required):** This is the most important parameter. It defines the category of the message box and determines its visual appearance (color and icon). Common `type` values include:
* `deletion`: For pages nominated for deletion. Deletion policy is relevant here. * `contentdispute`: For pages with significant content disagreements. * `copyright`: For pages suspected of copyright infringement. * `cleanup`: For pages needing general cleanup or improvement. * `policy`: For pages violating wiki policies. * `speedy`: For pages eligible for speedy deletion. * `technical`: For pages with technical issues, like broken links. * `notability`: For pages failing to demonstrate notability.
- **`text` (Required):** The main text of the message. This should clearly and concisely explain the issue. Keep it neutral and objective.
- **`date` (Optional):** The date the message was added. If omitted, the current date is used automatically. Using the `date` parameter is useful for archiving purposes.
- **`user` (Optional):** The username of the user who added the message. If omitted, it's automatically added.
- **`talk` (Optional):** Specifies whether a link to the talk page should be included. Defaults to `yes`. Set to `no` if discussion isn't desired.
- **`category` (Optional):** Allows specifying a custom category for the message box. Generally, the `type` parameter handles categorization automatically.
- **`image` (Optional):** Overrides the default icon with a custom image. Use with caution and ensure the image is appropriate.
- **`small` (Optional):** If set to `yes`, the message box will be displayed in a smaller size. Useful for less critical notifications.
Example Usage:
```wiki Template loop detected: Template:Use mbox ```
This example creates a deletion message box with the specified text, date, and username. It also implicitly links to the talk page for discussion.
Common Use Cases
Let's explore some practical scenarios where `Template loop detected: Template:Use mbox` is invaluable:
1. **Nominating a Page for Deletion:** When a page doesn't meet the wiki’s inclusion criteria, tagging it with the `deletion` type is crucial. Link to the relevant deletion policy and the deletion discussion page. This alerts other users to the proposed deletion and allows for discussion. Consider using AfD (Articles for Deletion) as a process.
2. **Addressing Copyright Violations:** If you suspect a page contains copyrighted material without proper attribution, use the `copyright` type. Clearly state the suspected violation and provide evidence if possible. This triggers a review by administrators. Understanding fair use is particularly important.
3. **Requesting Content Improvements:** If a page lacks citations, is poorly written, or is incomplete, the `cleanup` type is appropriate. Be specific about the requested improvements. For example: “This article lacks citations. Please add reliable sources to support the claims made.” Referencing Wikipedia:Manual of Style can be helpful.
4. **Highlighting Content Disputes:** When users disagree about the accuracy or neutrality of content, the `contentdispute` type can be used to signal the issue. Encourage constructive discussion on the talk page. Understanding neutral point of view (NPOV) is essential.
5. **Flagging Policy Violations:** If a page violates a specific wiki policy (e.g., personal attacks, spam), use the `policy` type. Clearly identify the violated policy. Refer to the site's rules.
6. **Technical Issues:** If a page has broken links, formatting errors, or other technical problems, use the `technical` type. Be specific about the issue.
7. **Notability Concerns:** If a subject lacks sufficient coverage in reliable sources, flag it with the `notability` type. Providing examples of where notability is lacking is helpful.
Best Practices for Using Template:Use mbox
To ensure maximum effectiveness and avoid creating unnecessary friction, follow these best practices:
- **Be Clear and Concise:** The message should be easy to understand. Avoid jargon and ambiguity.
- **Be Neutral and Objective:** Avoid accusatory language or personal attacks. Focus on the issue, not the user.
- **Provide Specific Details:** Instead of saying “This article needs improvement,” specify *what* needs improvement.
- **Link to Relevant Policies:** Whenever possible, link to the wiki policies that are being violated or the guidelines that are not being met.
- **Use the Appropriate `type`:** Choosing the correct type ensures that the message is categorized correctly and displayed appropriately.
- **Engage in Discussion:** Don’t just add a message box and walk away. Respond to any questions or concerns raised by other users on the talk page.
- **Consider the Severity:** Use `small=yes` for minor issues. Reserve more prominent message boxes for serious concerns.
- **Don't Overuse:** Avoid adding multiple message boxes for the same issue. Consolidate the information into a single, comprehensive message.
- **Respectful Tone:** Always maintain a respectful and collaborative tone, even when addressing serious issues.
Troubleshooting & Common Issues
- **Message Box Not Displaying:** Ensure the syntax is correct. Double-check the parameter names and values. MediaWiki is case-sensitive.
- **Incorrect Type:** If the message box is displaying with the wrong color or icon, you’ve likely selected the wrong `type`.
- **Link to Talk Page Not Working:** Verify that the `talk` parameter is set to `yes` (or omitted, as it defaults to yes).
- **Date Not Displaying Correctly:** Ensure the `date` parameter is in the correct format (YYYY-MM-DD). If omitted, the current date will be used.
- **Conflicting Message Boxes:** If multiple message boxes are overlapping or causing layout issues, try using the `small` parameter or consolidating the information.
- **Template Errors:** If you see an error message indicating a problem with the template itself, it may be a bug in the template code. Report the issue to the wiki administrators.
Advanced Usage and Customization
While the standard parameters cover most use cases, you can customize the appearance of the message box further by:
- **Using Custom Icons:** The `image` parameter allows you to replace the default icon with a custom image. However, ensure the image is relevant and appropriate.
- **CSS Styling:** Experienced users can modify the appearance of the message box using CSS (Cascading Style Sheets). This requires knowledge of CSS syntax and the wiki's CSS rules.
- **Creating Sub-templates:** For frequently used message boxes with specific configurations, you can create sub-templates that inherit from `Template loop detected: Template:Use mbox`. This simplifies the process of adding the message box in the future.
Relation to Other Wiki Features
`Template loop detected: Template:Use mbox` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [145](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [146](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [147](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [148](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [149](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [150](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [151](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [152](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [153](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [154](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [155](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [156](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [157](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [158](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [159](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [160](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [161](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [162](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [163](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [164](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [165](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [166](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [167](https://www.investopedia.com/terms/b/bullmarket.asp) and [168](https://www.investopedia.com/terms/b/bearmarket.asp)
Template namespace` doesn’t work in isolation. It’s closely integrated with other wiki features:
- **Talk pages:** Message boxes often prompt discussion on the talk page.
- **Watchlists:** Users watching a page will be notified when a message box is added.
- **Notifications:** Users may receive notifications about message boxes added to pages they’ve contributed to.
- **History:** The addition of a message box is recorded in the page’s history.
- **Categories:** The `type` parameter automatically categorizes the message box, making it easier to find pages with specific issues.
- **Recent changes:** The addition of a message box appears in the recent changes feed.
Resources for Further Learning
- Help:Templates: General information about templates in MediaWiki.
- Help:Message Boxes: Detailed documentation on message boxes.
- Wikipedia:Manual of Style: Guidelines for writing high-quality articles.
- Wikipedia:Deletion policy: Rules and guidelines for deleting pages.
- Wikipedia:Copyright violations: Information on copyright issues.
- **Technical Analysis:** [169](https://www.investopedia.com/terms/t/technicalanalysis.asp)
- **Moving Averages:** [170](https://www.investopedia.com/terms/m/movingaverage.asp)
- **Relative Strength Index (RSI):** [171](https://www.investopedia.com/terms/r/rsi.asp)
- **MACD:** [172](https://www.investopedia.com/terms/m/macd.asp)
- **Bollinger Bands:** [173](https://www.investopedia.com/terms/b/bollingerbands.asp)
- **Fibonacci Retracement:** [174](https://www.investopedia.com/terms/f/fibonacciretracement.asp)
- **Candlestick Patterns:** [175](https://www.investopedia.com/terms/c/candlestick.asp)
- **Support and Resistance:** [176](https://www.investopedia.com/terms/s/supportandresistance.asp)
- **Trend Lines:** [177](https://www.investopedia.com/terms/t/trendline.asp)
- **Chart Patterns:** [178](https://www.investopedia.com/terms/c/chartpattern.asp)
- **Elliott Wave Theory:** [179](https://www.investopedia.com/terms/e/elliottwavetheory.asp)
- **Ichimoku Cloud:** [180](https://www.investopedia.com/terms/i/ichimoku-cloud.asp)
- **Volume Analysis:** [181](https://www.investopedia.com/terms/v/volume.asp)
- **Stochastic Oscillator:** [182](https://www.investopedia.com/terms/s/stochasticoscillator.asp)
- **Average True Range (ATR):** [183](https://www.investopedia.com/terms/a/atr.asp)
- **Parabolic SAR:** [184](https://www.investopedia.com/terms/p/parabolicsar.asp)
- **Donchian Channels:** [185](https://www.investopedia.com/terms/d/donchianchannel.asp)
- **Head and Shoulders Pattern:** [186](https://www.investopedia.com/terms/h/headandshoulders.asp)
- **Double Top/Bottom:** [187](https://www.investopedia.com/terms/d/doubletop.asp)
- **Triangles (Ascending, Descending, Symmetrical):** [188](https://www.investopedia.com/terms/t/triangle.asp)
- **Gap Analysis:** [189](https://www.investopedia.com/terms/g/gap.asp)
- **Market Sentiment:** [190](https://www.investopedia.com/terms/m/marketsentiment.asp)
- **Bearish vs Bullish Trends:** [191](https://www.investopedia.com/terms/b/bullmarket.asp) and [192](https://www.investopedia.com/terms/b/bearmarket.asp)