#Content Converter Registry
1 messages · Page 1 of 1 (latest)
Any particular reason why module development and system development was lumped in together? They do require different skill sets, some of which are transferable, sure, but not everything.
Interestingly enough, they were originally separated but a near universal piece of feedback we got on the initial draft of the form was to only split them on the basis of Creation/Extension.
If you're only interested in modules or game systems that's something you can mention in the Experience question.
Probably a good idea to have an abstraction layer between content owners who are not familiar with Foundry development and developers. I mean, there's headhunters out there making good money making sure they find suited candidates for companies. So it makes sense to offer content owners a service to filter the list of developers for suitable candidates for them.
Exactly. We'll also be helping our publishing partners get up to speed on how Foundry works and answering questions they might have after speaking with some developers. Unlike the headhunters we don't take a cut though
.
@rare finch
does this point just mean setting up the adventure in foundry, or also code work of setting up the module itself?
I think the only code work I would expect from someone who had checked that would be setting up the module.json which should be very simple and not actually require any programming knowledge. We have a "how to" guide that walks through doing such a thing here: https://foundryvtt.com/article/packaging-guide/