diff --git a/docs/changelog.md b/docs/changelog.md index 5c5d4b5..2745297 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -23,6 +23,12 @@ Everything here is listed in reverse chronological order with the most recent up ## 2023 +### November 2023 +- Add "StashDB Moderation Enforcement" by [@AdultSun]{:target="_blank"} in [PR #66]{:target="_blank"} and [approved in this thread on Discord](https://discord.com/channels/559159668438728723/1124860754869366805){:target="_blank"} +- Update homepage by [@AdultSun]{:target="_blank"} in [PR #66]{:target="_blank"} + +[PR #66]: https://github.com/stashapp/StashDB-Docs/pull/66 + ### October 2023 - Add "Animated Scene Covers" by [@AdultSun]{:target="_blank"} in [PR #58]{:target="_blank"} - Add "Animated Performer Images" by [@AdultSun]{:target="_blank"} in [PR #58]{:target="_blank"} diff --git a/docs/faq_getting-started/edits.md b/docs/faq_getting-started/edits.md index b2535d6..b644fec 100644 --- a/docs/faq_getting-started/edits.md +++ b/docs/faq_getting-started/edits.md @@ -29,6 +29,12 @@ parent: FAQ / Getting Started *** +### [Losing Edit Access](moderation-enforcement) + +{: .important } +**At the discretion of an admin, a user’s edit access may be revoked at any time to maintain the integrity of the database and community.** *[See more...](moderation-enforcement)* + + ### [Updating Edits](updating-edits) {: .important } diff --git a/docs/faq_getting-started/edits/asking-for-votes.md b/docs/faq_getting-started/edits/asking-for-votes.md index e55ff05..3290c09 100644 --- a/docs/faq_getting-started/edits/asking-for-votes.md +++ b/docs/faq_getting-started/edits/asking-for-votes.md @@ -1,7 +1,7 @@ --- layout: default title: Asking for Votes -nav_order: 4 +nav_order: 5 parent: 'Edits' grand_parent: FAQ / Getting Started --- diff --git a/docs/faq_getting-started/edits/bulk-edits.md b/docs/faq_getting-started/edits/bulk-edits.md index 1700b8c..6e2e20c 100644 --- a/docs/faq_getting-started/edits/bulk-edits.md +++ b/docs/faq_getting-started/edits/bulk-edits.md @@ -1,7 +1,7 @@ --- layout: default title: Bulk Edits -nav_order: 7 +nav_order: 8 parent: 'Edits' grand_parent: FAQ / Getting Started --- @@ -13,4 +13,8 @@ grand_parent: FAQ / Getting Started --- -Any projects that would affect a large amount of data on StashDB and/or require a high volume of individual edits will need to be approved on Discord first by dropping a question in the **#stashdb-general** channel. If it's in line with the guidelines already established on this website, than a simple "heads up" before starting may be all that is needed from you. More drastic changes may require formal approval as a [guideline proposal]({{ site.baseurl }}/docs/faq_getting-started/stashdb/guideline-proposals/) in the **#stashdb-guidelines** channel on Discord. Projects that would add more than a few dozen edits into the queue at a time may need to be broken up into smaller chunks. All of these points apply to both manual submissions and automated submissions. +Any projects that would affect a large amount of data on StashDB and/or require a high volume of individual edits will need to be approved on Discord first by dropping a question in the **#stashdb-general** channel. If it's in line with the guidelines already established on this website, then a simple "heads up" before starting may be all that is needed from you. More drastic changes may require formal approval as a [guideline proposal]({{ site.baseurl }}/docs/faq_getting-started/stashdb/guideline-proposals/) in the **#stashdb-guidelines** channel on Discord. Projects that would add more than a few dozen edits into the queue at a time may need to be broken up into smaller chunks. + +All of the points mentioned above apply to both manual submissions and automated submissions. However, automated submissions are only allowed with permission from an admin. This requires a special BOT role in your account before edits can be flagged as automated within the edit queue. + +Violating any of these requirements could result in the [loss of edit access]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/#abuse-of-the-edit-system-1). diff --git a/docs/faq_getting-started/edits/cancelling-edits.md b/docs/faq_getting-started/edits/cancelling-edits.md index 4a21cd6..0b8abf2 100644 --- a/docs/faq_getting-started/edits/cancelling-edits.md +++ b/docs/faq_getting-started/edits/cancelling-edits.md @@ -1,7 +1,7 @@ --- layout: default title: Cancelling Edits -nav_order: 2 +nav_order: 3 parent: 'Edits' grand_parent: FAQ / Getting Started --- diff --git a/docs/faq_getting-started/edits/edit-comments.md b/docs/faq_getting-started/edits/edit-comments.md index 2d05b82..0c6332f 100644 --- a/docs/faq_getting-started/edits/edit-comments.md +++ b/docs/faq_getting-started/edits/edit-comments.md @@ -1,7 +1,7 @@ --- layout: default title: Edit Comments -nav_order: 5 +nav_order: 6 parent: 'Edits' grand_parent: FAQ / Getting Started --- @@ -14,3 +14,5 @@ grand_parent: FAQ / Getting Started --- Regardless of what kind of edit you're submitting, always include in the comment field what you are doing and why. Bigger or more drastic changes will likely require longer comments, but simple changes likely won't need much. Also please remember to note what you are using as the source of your edit when appropriate. These notes will be helpful when considering further edits in addition to justifying your actions now to those who will be voting on it. + +Also, please be aware that abusing the comment system in any way could result in the [removal of edit access]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/#abuse-of-the-comment-system-1). Click the hyperlink for examples of what may be considered abuse of the system. diff --git a/docs/faq_getting-started/edits/low-effort-submissions.md b/docs/faq_getting-started/edits/low-effort-submissions.md index ce99ef1..37cbefc 100644 --- a/docs/faq_getting-started/edits/low-effort-submissions.md +++ b/docs/faq_getting-started/edits/low-effort-submissions.md @@ -1,7 +1,7 @@ --- layout: default title: Low Effort Submissions -nav_order: 6 +nav_order: 7 parent: 'Edits' grand_parent: FAQ / Getting Started --- @@ -16,3 +16,5 @@ grand_parent: FAQ / Getting Started Submissions of any kind may be rejected if voters deem them to be "low effort" even if it doesn't technically violate any other guidelines and all of its information is correct. "Low effort" submissions appear rushed and often leave out information that is obvious or easily found. The reasoning behind rejection is that "low effort" submissions will take the same amount of time and effort for others to fix (if not more) as it would have taken the original contributor to make a complete submission in the first place. It will also often be faster and easier for the original contributor to update or cancel/redo their own submission than for somebody else to do it for them. "Low effort" submissions should not be confused with small edits, which are of course welcome on StashDB. If you fear that your edit may appear incomplete to others and could be at risk of downvotes as a "low effort" submission, make sure you explain why your edit may look that way (performer not listed anywhere, couldn't find any details/photos for a performer, waiting for another edit to be approved before you can add something, etc.) Voters won't be inclined to downvote if you acknowledge and explain a sparse edit. Also, please see our related policy on [missing scene performers]({{ site.baseurl }}/docs/scenes/edit/scene-performers/missing-performers/). + +If a user continually makes "low effort" submissions, their actions could be considered repeated violations of the guidelines and may result in the [removal of edit access]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/#repeated-violations-of-the-guidelines-1). diff --git a/docs/faq_getting-started/edits/moderation-enforcement.md b/docs/faq_getting-started/edits/moderation-enforcement.md new file mode 100644 index 0000000..2812be2 --- /dev/null +++ b/docs/faq_getting-started/edits/moderation-enforcement.md @@ -0,0 +1,73 @@ +--- +layout: default +title: Losing Edit Access +nav_order: 1 +parent: 'Edits' +grand_parent: FAQ / Getting Started +--- + +# StashDB Moderation Enforcement + +## Overview + +At the discretion of one of StashDB’s admins, a user’s EDIT and VOTE roles may be revoked ***at any time***. However, know that we have rarely felt the need to take this course of action. Every situation is unique and we strive to only take action ***when absolutely necessary***. + +In short, we ask all contributors to act conscientiously with the best interests of the community in mind. We will exercise our authority and restraint to maintain the integrity of both the database and the community as we see fit. + +--- + +**The following behavior may be grounds for the loss of editing or voting rights:** + +1. ### [Abuse of the edit system](#abuse-of-the-edit-system-1) +2. ### [Abuse of the voting system](#abuse-of-the-voting-system-1) +3. ### [Abuse of the comment system](#abuse-of-the-comment-system-1) +4. ### [Repeated violations of the guidelines](#repeated-violations-of-the-guidelines-1) +5. ### [Technical hacks or exploits](#technical-hacks-or-exploits-1) +6. ### [Any other misconduct considered serious enough to warrant action](#any-other-misconduct-considered-serious-enough-to-warrant-action-1) + +--- + +## Warnings and Restorations + +An admin will almost always attempt to warn a user first when their actions could lead to the loss of their EDIT and VOTE roles. If the warning goes ***ignored or unseen***, continued violations will result in disciplinary action. + +However, an admin may also decide to revoke these privileges ***without warning*** in order to prevent further violations. This decision is most often made to limit the damage of a user in the middle of a run of violations who is not immediately responding to requests to stop. + +A user’s EDIT and VOTE roles may be restored ***exactly one time***, but only if an admin considers it appropriate to the situation. If these privileges are revoked a second time, ***it will be permanent***. We are a small team who are unable to spend an extended period of time dealing with multiple violations/appeals from a single account. ***All decisions are final***. + +{: .note } +The most common reason for losing these privileges is a ***lack of communication***. If we cannot reach you through edit comments or messages on Discord/Matrix to correct continued violations of the guidelines, revoking edit access becomes our last resort to get in touch with you. We understand that tracking edit comments on StashDB can be difficult at this time. That is why we stress to all editors the importance of ***being reachable on Discord/Matrix***. + +--- + +## Expanded Details + +The following provides more specific explanations and examples for violations of the 6 points laid out above. It’s worth repeating though, every situation is unique so all enforcement decisions are entirely up to the discretion of an admin. + +1. ### Abuse of the edit system + 1. Flooding the edit queue [without warning or permission]({{ site.baseurl }}/docs/faq_getting-started/edits/bulk-edits/) + 1. Automated submissions [without permission]({{ site.baseurl }}/docs/faq_getting-started/edits/bulk-edits/) + 1. Repeated submissions of the exact same edit, ignoring rejection/cancellation/failure + 1. Excessive or misleading updates to submissions +1. ### Abuse of the voting system + 1. Excessive downvotes for any reason other than incorrect information or violations of the guidelines + 1. Excessive downvotes with no explanation behind them, not including downvotes that simply agree with another user’s comment + 1. Excessive upvotes with little consideration for obvious guideline violations + 1. Use of multiple accounts to circumvent the typical approval process +1. ### Abuse of the comment system + 1. Verbal abuse, threats, harassment, etc. + 1. Trolling, inappropriate links, etc. + 1. Excessive number of unproductive comments +1. ### Repeated violations of the guidelines + 1. No communication or acknowledgment of guideline violations + 1. Willfully continuing to violate guidelines after being corrected + 1. Not all guidelines are created equal, important ones will be more strictly enforced + 1. [No underage performers, scenes, or images]({{ site.baseurl }}/docs/performers/create/performer-eligibility/) + 1. [No legal names]({{ site.baseurl }}/docs/performers/edit/performer-aliases/eligible-aliases/) + 1. [No banned studios]({{ site.baseurl }}/docs/studios/create/banned-studios/) +1. ### Technical hacks or exploits + 1. Bending and/or breaking the software through atypical usage + 1. Accessing another user’s account + 1. Exposing the private information of users +1. ### Any other misconduct considered serious enough to warrant action + 1. At an admin’s discretion, editing and voting privileges may be revoked for any other misconduct that is not explicitly stated above in order to protect the integrity of the database and the community diff --git a/docs/faq_getting-started/edits/updating-edits.md b/docs/faq_getting-started/edits/updating-edits.md index b6a7dc1..e3b43dc 100644 --- a/docs/faq_getting-started/edits/updating-edits.md +++ b/docs/faq_getting-started/edits/updating-edits.md @@ -1,7 +1,7 @@ --- layout: default title: Updating Edits -nav_order: 1 +nav_order: 2 parent: 'Edits' grand_parent: FAQ / Getting Started --- @@ -13,8 +13,10 @@ grand_parent: FAQ / Getting Started --- -You can update your own pending edits once and only once. The button is a little hidden. You first have to navigate to the page for that individual submission by clicking the heading in the top left of the edit card. It should say something like "Create Scene" or "Modify Performer". You should then see a blue "Update Edit" button at the bottom of the page. You'll then see the edit form in the same state as the current submission. Just remember to leave an additional [edit comment]({{ site.baseurl }}/docs/faq_getting-started/edits/edit-comments/) explaining your new adjustments before clicking "Submit Edit" again. Remember, you can only update each edit exactly once so try not to miss anything. It saves us all the extra time and effort of making additional corrections. +You can update your own pending edits once and only once. The button is kind of hidden. You first have to navigate to the page for that individual submission by clicking the heading in the top left of the edit card. It should say something like "Create Scene" or "Modify Performer". You should then see a blue "Update Edit" button at the bottom of the page. You'll then see the edit form in the same state as the current submission. Just remember to leave an additional [edit comment]({{ site.baseurl }}/docs/faq_getting-started/edits/edit-comments/) explaining your new adjustments before clicking "Submit Edit" again. Remember, you can only update each edit exactly once so try not to miss anything. It saves us all the extra time and effort of making additional corrections. At this time, updating your edit does not reset previously cast votes. This means any "No" votes cast before the update will remain until a "No" voter comes back to change it. The edit's individual page (click the heading) will also show who's voted "Yes" and "No" already. Many users will check back on an edit after downvoting it to see if their requested changes have been made, but you may also contact them [on Discord]({{ site.baseurl }}/docs/faq_getting-started/stashdb/joining-our-discord/) yourself if you're worried about rejection or a long wait time. Their username in StashDB isn't always the same on Discord but a quick search in **#stashdb-invites** should find their request for edit access. Just be polite and respectful while asking them to flip their vote. -If you've already used your one update and still need to change something before your submission can be approved, unfortunately you'll need to resubmit it. First click the red "Cancel Edit" button at the bottom of the edit's page. It'll be right next to the blue "Update Edit" button. There is no way to revive a cancelled edit so you'll need start from the beginning again to recreate it. +If you've already used your one update and still need to change something before your submission can be approved, unfortunately you'll need to [cancel]({{ site.baseurl }}/docs/faq_getting-started/edits/cancelling-edits/) and resubmit it. First click the red "Cancel Edit" button at the bottom of the edit's page. It'll be right next to the blue "Update Edit" button. There is no way to revive a cancelled edit so you'll need start from the beginning again to recreate it. + +Also, please be aware that abusing the edit system in any way could result in the [removal of edit access]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/#abuse-of-the-edit-system-1). This includes using the update system in an attempt to circumvent the typical voting process. diff --git a/docs/faq_getting-started/edits/voting.md b/docs/faq_getting-started/edits/voting.md index 8ff5f6b..02d92ad 100644 --- a/docs/faq_getting-started/edits/voting.md +++ b/docs/faq_getting-started/edits/voting.md @@ -1,7 +1,7 @@ --- layout: default title: Voting -nav_order: 3 +nav_order: 4 parent: 'Edits' grand_parent: FAQ / Getting Started --- @@ -15,6 +15,14 @@ grand_parent: FAQ / Getting Started All edit submissions to StashDB will be subject to approval by the votes of other contributors. Voting rights will be granted automatically once you have 10 submissions approved. -Edits considered non-destructive may be approved immediately if they receive three unanimous YES votes. They may also be rejected immediately with three unanimous NO votes. Destructive edits (Merge and Destroy requests, mostly) and non-unanimous vote totals will require a waiting period to pass before it is rejected or approved. This may be 3 days or 7 days, depending on the current vote total. Net totals of 0 votes will still be approved at the end of the waiting period for non-destructive edits but will be rejected for destructive edits. For more details on a particular edit, hovering your cursor over "Voting closes in X days" in the top right corner will show you if it will be rejected or approved with the current vote total as well as the exact day and time the voting period will end. +Edits considered ***non-destructive*** may be approved immediately if they receive three unanimous YES votes. They may also be rejected immediately with three unanimous NO votes. Waiting periods are only required when there are less than 3 votes or when the vote is non-unanimous. This may be 3 days or 7 days, depending on the current vote total. Net totals of 0 votes will be ***approved*** at the end of the waiting period for non-destructive edits. -The ABSTAIN option is only used if you would like to remove your YES or NO vote rather than changing it. The "Save" button will not appear when ABSTAIN is selected unless you have previously saved a YES or NO vote on that edit. +***Destructive edits*** (Merge and Destroy requests, mostly) always require a minimum waiting period to pass before it is approved or rejected. This may be 3 days or 7 days, depending on the current vote total. Net totals of 0 votes will be ***rejected*** for destructive edits. + +For more details on a particular edit, let your cursor hover over "Voting closes in X days" in the top right corner of the edit card. It will show you — based on the current vote total — the exact day and time the voting period will end and if it will be rejected or approved. + +The ABSTAIN option is only used if you would like to remove your YES or NO vote instead of changing it. The "Save" button will not appear when ABSTAIN is selected unless you have previously saved a YES or NO vote on that edit. + +[Asking for votes on Discord]({{ site.baseurl }}/docs/faq_getting-started/edits/asking-for-votes/) in order to speed up the approval process is only recommended in specific situations. + +Also, please be aware that abusing the voting system in any way could result in the [removal of editing and voting privileges]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/#abuse-of-the-voting-system-1). Click the hyperlink for examples of what may be considered abuse of the system. diff --git a/docs/faq_getting-started/stashdb/contributing-to-stashdb.md b/docs/faq_getting-started/stashdb/contributing-to-stashdb.md index 3e54580..6badd74 100644 --- a/docs/faq_getting-started/stashdb/contributing-to-stashdb.md +++ b/docs/faq_getting-started/stashdb/contributing-to-stashdb.md @@ -13,4 +13,8 @@ grand_parent: FAQ / Getting Started --- -Every StashDB account is able to submit fingerprints/hashes from within the Scene Tagger view of Stash. This does not require any additional permissions. However, if you would like to add or edit performers, scenes, studios, or tags, you will need to be granted additional privileges. Requesting edit access is not difficult. Detailed instructions can be found pinned to the **#stashdb-invites** channel on [Discord]({{ site.baseurl }}/docs/faq_getting-started/stashdb/joining-our-discord/). Please note that you will be expected to be reachable on Discord if you become an active contributor on StashDB. This is because there is no messaging or notification system from within StashDB at this time. If we cannot reach you over Discord, your edit rights may be revoked by an admin after repeated violations of our guidelines. +Every StashDB account is able to [submit fingerprints/hashes]({{ site.baseurl }}/docs/faq_getting-started/stashdb/whats-a-phash/) from within the [Scene Tagger](https://docs.stashapp.cc/beginner-guides/guide-to-scraping/#use-the-scene-tagger){:target="_blank"} view of Stash. This does not require any additional permissions. However, if you would like to add or edit performers, scenes, studios, or tags, you will need to be granted additional privileges. Requesting edit access is not difficult. Detailed instructions can be found pinned to the **#stashdb-invites** channel on [Discord]({{ site.baseurl }}/docs/faq_getting-started/stashdb/joining-our-discord/). + +Please note that you will be expected to be reachable on Discord/Matrix if you become an active contributor on StashDB. This is because the comment system is limited with no direct messaging or notification system from within StashDB at this time. We also ask that you [change your nickname](https://support.discord.com/hc/en-us/articles/219070107-Server-Nicknames){:target="_blank"} on our Discord server to match your StashDB username. It makes it easier for other editors to find you in case there are any questions or issues. It also won't change your username or display name outside of Stash's Discord. If you would like to change your StashDB username instead, please contact **@AdultSun** on Discord. + +If we cannot reach you through comments or Discord/Matrix messages, your [edit rights may be revoked]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/) by an admin after repeated violations of our guidelines. diff --git a/docs/faq_getting-started/stashdb/unconfirmed-guidelines.md b/docs/faq_getting-started/stashdb/unconfirmed-guidelines.md index 7133b5b..9840231 100644 --- a/docs/faq_getting-started/stashdb/unconfirmed-guidelines.md +++ b/docs/faq_getting-started/stashdb/unconfirmed-guidelines.md @@ -18,4 +18,6 @@ Early on, many of this website's sections will have this message at the bottom: {: .note } Unconfirmed guideline, subject to change pending formal approval. -All this means is that the language has not been formally approved by the community in our **#stashdb-guidelines** channel on [Discord]({{ site.baseurl }}/docs/faq_getting-started/stashdb/joining-our-discord/) yet. Contributors are still expected to follow these unconfirmed guidelines, but should know that they are subject to change in the near future. +This just means the language has not been formally approved by the community in our **#stashdb-guidelines** channel on [Discord]({{ site.baseurl }}/docs/faq_getting-started/stashdb/joining-our-discord/) yet. Each one represents a working consensus developed organically between contributors over time. + +Contributors are still expected to follow these unconfirmed guidelines, but should know that they are subject to change in the near future. Continually violating them may still result in the [removal of edit access]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/). diff --git a/docs/index.md b/docs/index.md index f84b6e1..fbf16f5 100644 --- a/docs/index.md +++ b/docs/index.md @@ -34,15 +34,12 @@ Some of the content not currently allowed on StashDB can be found on other publi *** -## **Category Overviews** -Guideline sections are organized by each main object type: [Performers]({{ site.baseurl }}/docs/performers/), [Scenes]({{ site.baseurl }}/docs/scenes/), [Studios]({{ site.baseurl }}/docs/studios/), and [Tags]({{ site.baseurl }}/docs/tags/). These parent pages are then split into the actions you can take with each object: **Create**, **Edit**, **Merge**, and **Delete**. These **Edit** pages are broken down further into each available field for that object, reflecting the order in which they appear on StashDB. +## **New Contributors** +For anyone who wants to browse or pull data from StashDB, you will first need to create a StashDB account using an invite token. Instructions found [here]({{ site.baseurl }}/docs/faq_getting-started/stashdb/accessing-stash-boxes/#stashdb). New accounts will be limited to read-only access, but will still be able to [submit fingerprints]({{ site.baseurl }}/docs/faq_getting-started/stashdb/whats-a-phash/) back to StashDB to help others find matches for their files. -Parent pages serve as overviews of the entire category. Sometimes they will include one sentence summaries of each guideline section followed by links to more detailed explanations. All of these can also be found on the left side of this webpage. +In order to fix incorrect info or add missing data, your account will need to be granted edit access. More information can be found [here]({{ site.baseurl }}/docs/faq_getting-started/stashdb/contributing-to-stashdb/) with more detailed instructions in [Discord]({{ site.baseurl }}/docs/faq_getting-started/stashdb/joining-our-discord/) pinned to the **#stashdb-invites** channel. [Voting access]({{ site.baseurl }}/docs/faq_getting-started/edits/voting/) comes later. Make sure to watch for comments/downvotes on your edits and messages on Discord/Matrix alerting you to any issues or possible violations of the guidelines. -- [Performers]({{ site.baseurl }}/docs/performers/) -- [Scenes]({{ site.baseurl }}/docs/scenes/) -- [Studios]({{ site.baseurl }}/docs/studios/) -- [Tags]({{ site.baseurl }}/docs/tags/) +***At the discretion of an admin, a user’s edit access may be revoked at any time.*** This happens very rarely and is only done when absolutely necessary to maintain the integrity of both the database and the community. The most common reason for losing these privileges is a lack of communication. More information on our enforcement process can be found [here]({{ site.baseurl }}/docs/faq_getting-started/edits/moderation-enforcement/). *** @@ -58,3 +55,15 @@ The following **Getting Started** sections are general advice and explanations f - [Drafts]({{ site.baseurl }}/docs/faq_getting-started/drafts/) - [User]({{ site.baseurl }}/docs/faq_getting-started/user/) - [Search]({{ site.baseurl }}/docs/faq_getting-started/search/) + +*** + +## **Guideline Overview** +Guideline sections are organized by each main object type: [Performers]({{ site.baseurl }}/docs/performers/), [Scenes]({{ site.baseurl }}/docs/scenes/), [Studios]({{ site.baseurl }}/docs/studios/), and [Tags]({{ site.baseurl }}/docs/tags/). These parent pages are then split into the actions you can take with each object: **Create**, **Edit**, **Merge**, and **Delete**. These **Edit** pages are broken down further into each available field for that object, reflecting the order in which they appear on StashDB. + +Parent pages serve as overviews of the entire category. Sometimes they will include one sentence summaries of each guideline section followed by links to more detailed explanations. All of these can also be found on the left side of this webpage. + +- [Performers]({{ site.baseurl }}/docs/performers/) +- [Scenes]({{ site.baseurl }}/docs/scenes/) +- [Studios]({{ site.baseurl }}/docs/studios/) +- [Tags]({{ site.baseurl }}/docs/tags/)