Okay! First off, thanks for the submission! The first couple of articles are usually a challenge, since SARP has some specific rules about how things should be handled. Here's some links that I keep handy and may reference in my feedback:
You don't need to have all of those memorized, but they all come in handy at different times. Some of them you might not stumble across when filling out your template - I know I didn't.
With that out of the way, let's focus on the submission.
First, because this is a combat drone and can be worn as power armor, I'd recommend using the
Power Armor Template. I'm not sure which template you used, but I
think it's not this one. In particular, the formatting for the Damage Capacity and Weapons systems needs to be preserved so that the article is consistent with other articles like it. You're already using the right language in the article, so I think you've got a solid grasp already - but, if you'd like some help, let me know!
Next, I'd like to understand if this is intended to be widely available or if it's a one-off. We consider the wiki to be 'all-knowing' and representative of how something is intended to be used. References to, "the market version will..", "the current thing is not the finished product...", etc, suggest that this is a one-off prototype - even if it isn't, these references should mostly be contained in the History section.
This could be as simple as saying, "As a prototype, the Usarus..." instead of, "the market version will..". The implication that something
will be true requires me to treat as though it
is true - which would mean treating the article as though it
is the market version.
If you want to make a market version
and Egwene's personal version of the armor, you could skip making a page for her personal version if the differences are primarily cosmetic or loadout based. If you
do want to have your own page, you could modify something like the
Personal Power Armor Template for tracking modifications and loadout of an existing set of power armor. That page wouldn't require approval, so long as everything on it had already been approved and was within the scope of the rules.
If you go with the market version, I'd recommend adding a section at the end for pricing, etc, since the default PA template doesn't have that. You could grab the relevant sections from the
Weapon Template, which is pretty robust on that front. Or, you can use this part that I grabbed for you:
===== Other =====
==== Pricing ====
* (Insert Weapon Name): (Insert Price in KS, DA, etc)
=== Replaceable Parts and Components ===
* (Insert Weapon Part/Component Name): (Insert Price in KS, DA, etc)
=== Optional Attachments ===
* (Insert Attachment Name): (Insert Price in KS, DA, etc)
I had a little trouble picking out the differences between the Mule and Combat versions. It might be nice to have subsections under 'Key Features' to improve the readability/formatting a bit. In the stat sections, where you use:
- Maximum Capacity: 2 (Mule Variant) 5 (Combat Variant)
- Passenger Capacity: 2 (Mule Variant) 5 (Combat Variant)
it may read easier as:
- Maximum Capacity:
Mule Variant: 2
Combat Variant: 5
- Passenger Capacity:
Mule Variant: 2
Combat Variant: 5
(the sub bullets aren't working in the quote very well, but you get the jist)
I spotted some minor spelling and capitalization issues. While you're working on the above, give the article a proofread pass. After that, there's few enough issues that I'm happy to fix anything you might miss.
All in all, a really solid first submission. Keep Char's comments in mind as you're making changes and this should go pretty smoothly.
Thanks!