I’m still having a hard time understanding what you’re after. Based on your last reply, you aren’t looking for documentation, because that would be an explanation, and explanations aren’t needed if the process is intuitive. What would make the process intuitive, in your opinion?
I’ve added a link to that post to the Documentation Index. Perhaps @clanmacrae, you want to make that post a “wiki-post” by pressing the vertical dots, so that it can be editted in perpetuity.
I’ve also added a TL;DR section to the top of How to upload modules to the Game Library.
Hopefully, these posts will help.
Yours,
Christian
Perhaps a way to make the interface more intuitive - as in self-explanetory - would be to add short explanetory paragraphs to the form inputs. For example as suggested the posts here, and here. Such paragraphcs could also link to the more elaborate How to upload modules to the Game Library Service. I would love to make a PR against vassal-site-src, but it will be a little hard to test it without a more elaborate set-up (backend DB and server).
Yours,
Christian
I made a video of suggestions to help users create a page / upload modules.
I hope this helps.
We had endless complaints about how complicated and error prone it was to add modules to the old wiki. It’s surprising to hear from someone who thought it was easy. You might be the first person I’ve heard say that in a dozen years.
What do you think of the instructions here? They’re intended to be conceptual, aimed at answering the questions you had about what should go into the fields by explaining how the fields relate to one another.
I think I get it - you don’t want to read the manual. Wonder how you got through the rules of Blackbeard, B-17: Queen of the Skies, or similar - those books are certainly longer than the Howto.
Just to be clear - How to upload modules to the Game Library Service is 11 Letter pages or 10 A4 pages, and that includes examples and comments (which are clearly marked and easily skipped). I think if you boiled it down, it would be no more than four to five pages, which includes information about updating and so on. Oh, and I think most of us understand how HTML pages work.
Most of the feedback I got on How to upload modules to the Game Library Service has been rather positive.
That said, I do tend to agree with some of your suggestions - each input form could have a short explanatory text - as I proposed above. However, your suggestion about drop-down boxes is not really in line with the thinking behind the new module library. Project owners should structure their project into packages as they think best suit the project. Drop-downs would at worst be limiting, and best confusing.
Just to be clear - the game library will likely not revert to the old Wiki type, so it is pointless to wish for that.
Yours,
Christian
Perhaps we’re not referring to the same instructions for the old wiki. The page I remember was not short.
True. The old wiki served its purpose, but it’s worth noting that the old wiki was very moderator dependent which added countless hours of moderator time I’m sure to handle the numerous requests and for the module creator, at least a day’s wait before the module or file updates would appear on the page. The new library is much more user friendly and grants the project owner a lot more control. Having used both, and gone through the learning pains of learning both, the new library is by far the more user-friendly one.
Rule books are not like reading a Tech Manual.
Tech Manuals are dry and VERY boring to read threw. Makes me sleepy or worse yet, board out of my mind!
Rules are easy and fun to read, they lead to playing games, and all sorts of fun things.
But a Tech Manual. I think I’d rather sit on a cactus in summer, in the desert. (You get the idea).
What would you rather read?
A game rule book or a Tech Manual on .lua files?
Also when I put the HTML link in Word, I got 14 pages, hence why I kept saying 14 pages.
That’s 14 pages of dry, sleep inducing pages of pure boredom, that I cant choke down.
Well I do understand HTML a lot better than Tech Manuals.
Surprising to hear you say that most people had a hard time with it… but I guess we all have our own vises.
The instructions you linked…
All well and good but again not intuitive. There is no “HELP” on the page that “suggests” what goes there.
Pull down menu’s not possible, I get that, can you have some other type of “helpful info” there?
Maybe even examples? I dont know, I’m just tossing out ideas.
But it needs something that suggests what goes in these fields, on the creation page.
I do hope something will come of this, and thank you for listening to me and my suggestions, even if not possible.
I’ve added placeholder text indicating what should go into the release creation input, and a tooltip explaining the package sort key input.