|
You can already do this on WoWInterface. Just use the "Report" button on your project page to contact a moderator, and type in the box that you want to disable comments.
|
Thanks, I didn't know that but I still think that it's nicer to have an option for that.
Thank you but I didn't ask for solutions.
Extremely subjective, as I personally think the beta site is atrocious. It's pretty much unacceptable for any website designed in the year 2015 to not be responsive (eg. usable on different device/window sizes without a horizontal scrollbar) and it's full of tiny and/or low-contrast text. The beta CurseForge site is a little better about color contrast than the beta WowAce site, but 14px is just not an acceptable size for text on the web.
Even if you have perfect vision and only browse on a large monitor in a maximized window and aren't bothered by the above, it's still missing features that have existed on the site for years (eg. a "dashboard" where you can see an overview of new tickets and comments for all your projects) and many pages appear unfinished (despite them supposedly having worked on this for TWO YEARS!) or are a huge step backward from the current design (eg. in the new localization system you can only see 5 phrases per page! and you have to click and load a new page to edit each translation instead of being able to edit them directly on the listing page).
In fact, their new site is SO bad that if it goes live in its present state, it's very unlikely I will continue using any Curse sites for comments, tickets, or posts, and will only continue hosting my addons there at all if I can do it remotely and never have to use the website.
|
I completely agree, sites need to be designed responsively, regardless, I think that the site itself looks good and in my post I was referring mainly to how it looks, I should have clarified what I meant.
I don't think it's that extreme to have a different taste.
I haven't explored the beta much so I don't have a clue about missing features.
|
The only functional difference this will make is that when I push changes to my remote repository, I just push to "origin" instead of "all", so I don't think it's really as cool as it sounds at first glance.
|
That's certainly one approach to make unmanageable things more manageable but it's still better to have a single repo than pushing to multiple ones.
|
Commit history, I disagree. Commit notes are typically quite terse and technical, so they may not be understandable by the average non-programmer, and there are often many commits which aren't of any interest to users. I think it's much better to write a changelog yourself for public releases, so you can list only the changes that are meaningful to users, and describe them in a way that's understandable by non-programmers.
|
Commit notes doesn't have to be terse or technical but I get what you're saying, I'm a programmer but authoring addons is not my daily day job, I do that on my free time and so I cut corners when I can and this is a corner I'd definitely cut in favor of other things.
|
Milestones... I think it's fine for this to stay on a developer site. For one, WoW addons are small and purposed enough that very few addons are going to benefit at all from milestone tracking. Even for larger addons, it's still probably easier to keep track of planned features using issues. For another, it's unlikely users of a WoW addon are going to bookmark your milestones page and check back periodically to see what's coming next in the addon... they're just going to install updates as they become available. I'd guess that the large majority of addon users don't even read changelogs.
|
Yeah maybe but go figure maybe they will once they will realize they can.
|
Wiki... if your addon is so complicated it needs a wiki, you're probably doing it wrong. If you have optional "tips and tricks" pages or "advanced usage" tutorials, just put links to them in your addon's description. I don't think there needs to be a dedicated "Wiki" link on addon pages.
|
An addon doesn't have to be big or complicated to warrant a wiki page or multiple wiki pages.
Sure, I can do that myself but when a developer renames the pages or post new pages she needs to go to each site whether it's Curse/WoWInterface and add/edit these links and not everyone have time to do it, again, a corner I'd cut.
I honestly appreciate that you actually took the time to give me solutions and write your POV but the point of this post is not about me looking for solutions to my problems but about improving the overall experience of WoWInterface, if it was about me then I'd write I need help with something but I wrote about how I feel and why I favor CurseForge over WoWInterface.