from retail

.editorconfig

@@ -0,0 +1,24 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[{babelfish.lua,ForAllIndentsAndPurposes.lua}]
+indent_style = space
+indent_size = 4
+
+[.luacheckrc]
+indent_style = tab
+indent_size = 4
+
+[{*.pkgmeta,*.pkgmeta-classic}]
+indent_style = space
+indent_size = 2

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: "\U0001F3A8 Feature Request"
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at staneck@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,104 @@
+# Contributing to WeakAuras
+
+## Code Standards
+
+There are a few things which we require in any contribution:
+
+- This repository comes with a `.editorconfig` file, so the following requirements will be taken care of if you have [EditorConfig](https://editorconfig.org/) installed:
+  - Tabs consist of 2 spaces.
+  - Files end with a newline.
+  - No trailing whitespace at the end of a line.
+- All user-facing strings (`names` and `desc` fields in AceConfig tables, mostly) must be localized:
+  - We use a locale scraper to find translation phrases and automatically export them to CurseForge for translation. This scraper parses the addon files, looking for tokens that look like: `L["some translation phrase"]`. You must use double quoted strings, and name the localization table (found at `WeakAuras.L`) `L` in your code for this to work properly.
+- When writing a new file, avoid using semicolons. When modifying code in an existing file, try to be consistent, but err on the side of no semicolons.
+- New features should be indicated by concatenating `WeakAuras.newFeatureString` onto the associated translation phrase. We will remove the new feature indicator approximately 3 months after the first release.
+
+## Pull Requests
+
+If you want to help, here's what you need to do:
+
+1. Make sure you have a [GitHub account](https://github.com/signup/free).
+1. [Fork](https://github.com/WeakAuras/WeakAuras2/fork) our repository.
+
+1. Create a new topic branch (based on the `main` branch) to contain your feature, change, or fix.
+
+    ```bash
+    git checkout -b my-topic-branch
+    ```
+
+1. Set `core.autocrlf` to true.
+
+    ```bash
+    git config core.autocrlf true
+    ```
+
+1. Set `pull.rebase`to true.
+
+    ```bash
+    git config pull.rebase true
+    ```
+
+1. Set up your [Git identity](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup) so your commits are attributed to your name and email address properly.
+
+1. Take a look at our [Wiki](https://github.com/WeakAuras/WeakAuras2/wiki/Lua-Dev-Environment) page on how to setup a Lua dev environment.
+
+1. Install an [EditorConfig](https://editorconfig.org/) plugin for your text editor to automatically follow our indenting rules.
+
+1. Commit and push your changes to your new branch.
+
+    ```bash
+    git commit -a -m "commit-description"
+    git push
+    ```
+
+1. [Open a Pull Request](https://github.com/WeakAuras/WeakAuras2/pulls) with a clear title and description.
+
+### Keeping your fork updated
+
+- Specify a new remote upstream repository that will be used to sync your fork (you only need to do this once).
+
+  ```bash
+  git remote add upstream https://github.com/WeakAuras/WeakAuras2.git
+  ```
+
+- In order to sync your fork with the upstream WeakAuras repository you would do
+
+  ```bash
+  git fetch upstream
+  git checkout main
+  git rebase upstream/main
+  ```
+
+- You are now all synced up.
+
+### Keeping your pull request updated
+
+- In order to sync your pull request with the upstream WeakAuras repository in case there are any conflicts you would do
+
+  ```bash
+  git fetch upstream
+  git checkout my-topic-branch
+  git rebase upstream/main
+  ```
+
+- In case there are any conflicts, you will now have to [fix them manually](https://help.github.com/articles/resolving-merge-conflicts-after-a-git-rebase/).
+- After you're done with that, you are ready to force-push your changes.
+
+  ```bash
+  git push --force
+  ```
+
+- Note: Force-pushing is a destructive operation, so make sure you don't lose something in the progress.
+- If you want to know more about force-pushing and why we do it, there are a two good posts about it: one by [Atlassian](https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing) and one on [Reddit](https://www.reddit.com/r/git/comments/6jzogp/why_am_i_force_pushing_after_a_rebase/).
+- Your pull request should now have no conflicts and be ready for review and merging.
+
+## Reporting Issues and Requesting Features
+
+1. Please check our [issue tracker](https://github.com/WeakAuras/WeakAuras2/issues) for your problem since there's a good
+   chance that someone has already reported it.
+1. If you find a match, please try to provide as much info as you can,
+   so that we have a better picture about what the real problem is and how to fix it ASAP.
+1. If you didn't find any tickets with a problem similar to yours then please open a
+   [new ticket](https://github.com/WeakAuras/WeakAuras2/issues/new/choose).
+    - Be descriptive as much as you can.
+    - Provide everything the template text asks you for.

README.md

@@ -1,4 +1,11 @@
-# WeakAuras 2 WotLK (3.3.5a)
+<div align="center">
+
+# WeakAuras WotLK (3.3.5a)
+
+![Discord](https://img.shields.io/discord/259362419372064778?style=flat&logo=discord&label=Discord&link=https%3A%2F%2Fdiscord.gg%2FUXSc7nt) ![Wiki](https://img.shields.io/badge/wiki-grey?style=flat&logo=github&link=https%3A%2F%2Fgithub.com%2FNoM0Re%2FWeakAuras-WotLK%2Fwiki) ![GitHub Issues](https://img.shields.io/github/issues/NoM0Re/WeakAuras-WotLK?link=https%3A%2F%2Fgithub.com%2FNoM0Re%2FWeakAuras-WotLK%2Fissues) [![PayPal](https://img.shields.io/badge/Buy_me_a_coffee-100000?style=flat&logo=PayPal&logoColor=white&labelColor=3b7bbf&color=grey)](https://streamelements.com/noom0re/tip)
+
+![Logo](https://i.imgur.com/wwbxeCG.jpeg)
+</div>
 
 WeakAuras is a powerful and flexible framework that allows the display of highly customizable graphics on World of Warcraft's user interface to indicate buffs, debuffs, and other relevant information. This addon was created to be a lightweight replacement for Power Auras but has since introduced more functionalities while remaining efficient and easy to use.
 
@@ -18,6 +25,31 @@ WeakAuras is a powerful and flexible framework that allows the display of highly
 
 To open the options window, type `/wa` or `/weakauras` into your chat and hit enter or use the minimap icon.
 
+## Extensions
+
+* [WeakAuras Companion](https://weakauras.wtf): This application adds the missing link between Wago.io and the World of Warcraft addon, enabling you to update your auras in a convenient fashion. (Folder Structure: `World of Warcraft/_retail_/Wow.exe` and backup WTF)
+* [WeakAuras_StopMotion](https://www.curseforge.com/wow/addons/weakauras-stop-motion): This addon adds a new region type to WeakAuras that allows for stop motion animations. Stop Motion textures contain each frame of the animation as a separate image. The addon ships with a number of animations and it supports custom textures.
+* [SharedMedia](https://github.com/bkader/SharedMedia) for more bar textures.
+* [SharedMediaAdditionalFonts](https://drive.google.com/file/d/1xDCpDpStRbXdSBKYOeZHpYBt_dRDqb3g/view?usp=sharing) for more fonts.
+* [ColorPickerPlus](https://drive.google.com/file/d/1ymNYizWp2TxIS1a6hLg7bT9YoJ3E-8Na/view?usp=sharing) for a better version of the WoW color picker that includes class color templates and a copy and paste function.
+
 ## Documentation
 
-For in-depth documentation, see the [wiki](https://github.com/WeakAuras/WeakAuras2/wiki) page.
+For in-depth documentation, see the [wiki](https://github.com/NoM0Re/WeakAuras-WotLK/wiki) page.
+
+## Examples
+
+For some examples of what WeakAuras can do, take a look at [wago.io](https://wago.io/search/imports/wow/all?q=3.3.5) where tons of people upload their creations and even feature complete interfaces utilizing WeakAuras!
+
+## Problems
+
+* Please see the [wiki](https://github.com/NoM0Re/WeakAuras-WotLK/wiki) page.
+* If you've discovered something that's clearly wrong, or if you get an error, please create a [ticket](https://github.com/NoM0Re/WeakAuras-WotLK/issues).
+* You're a programmer yourself and want to contribute? Check out our [contributing guidelines](CONTRIBUTING.md) to get started!
+* Feel free to join our [Discord Community](https://discord.gg/UXSc7nt) to talk, get help and discuss everything WeakAuras!
+
+## Support
+
+If you want to help out with development without providing code yourself, you can always donate to the WeakAuras project maintainers using PayPal or become a Patreon:
+
+[![WeakAuras on PayPal](https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif)](https://paypal.me/WeakAuras)  [![Become a Patreon!](https://c5.patreon.com/external/logo/become_a_patron_button.png)](https://www.patreon.com/bePatron?u=3216523)