This suggestion is pretty much just as the title says.  Users of DDB should be able to integrate their Discord servers.  I am actually quite surprised that you can no do this, especially since there is some (is basic) integration with Slack.

Standard Discord integration

This would be pretty easy to do - simply duplicate the Slack text field on the profile page and rename it Discord, then set the content to be a clickable hyperlink rather than a username.  Users would then be able to have clickable invite links for their Discord servers publicly available on their profiles.

(link should open in a new tab)

It would take like 30 mins (tops) to add this feature.

Advancement of the above

An advancement of the above would be allowing users to integrate specific Discord servers with their campaigns - allowing players and DMs to connect to a campaigns specific Discord server from the campaign page - thus eliminating the need to have multiple windows open or apps running at once.  

This would involve the development of a specific web-app that was integrated into campaign pages and used the Discord api to connect to servers, so this would involve more dev time than the above standard option.

TD;LR

Users should be able to have clickable invite links to their Discord servers on their profile pages and possible Discord integration with specific campaigns, allowing players and DMs to connect to the campaigns discord server from the campaign page - eliminating the need to have multiple windows,pages or apps open.

Quote from Stormknight >>

It's certainly a lot more than 30 mins work though, as there are other concerns than just adding a field to the profile. :)

Okay, so I agree that if you are looking for actual integration rather than just a clickable link, then yes; that could be more work but just adding a field to the profile page for people to drop hyperlink text into and then have it display as a hyperlink, would not take more than 30 minutes. Even creating it from scratch and not just duplicating the Slack field and changing the acceptable content type and then writing the styling in whatever styling language DDB uses to style its pages in, wouldn't take more than 30 minutes.

Then assuming that the profile pages are built dynamically from a database, once the field was added to the source, the column would need created in the relevant database and the field associated with that column (half a day) then say half a day for git merges and stuff (max).

Add testing and so on to make sure that it displayed and worked correctly and didn't cause any problems with the page layout and you are looking at a further 2 days.  That would be one person actually writing the source and styling code and one person doing the necessary DB work, then a group of people testing out.

So you have the following

• Planning
• Writing the source
• Styling
• Creating column in DB
• Assigning field to relevant column in DB
• Testing
• Git merges
• Site maintenance time
• Go live

Basically, 2 and 3 from above wouldn't take more than 30 mins.  Add in the rest of the items and you have a 3 day cycle.  It could be done over a weekend quite easily.

I agree though, if you were going for proper full integration then that would take considerably longer as there are security implications there that would need to be dealt with and resolved and that could take weeks if not months depending on how major they were.

In the meantime though, while full integration was being worked on, we could get a basic field to enter out Discord server hyperlinks into and as above, that wouldn't take all that long at all, since everything is already in place and the security implications wouldn't be any more than having a Slack field - and those should already have been taken care of and would be easily ported to a Discord field.

I do agree with you @Stormknight - please don't take my post as me knowing anything about DDBs actual development system

I don't know how DBB actually develop their resources neither do I or have ever worked for them.

My post was very generalised and I don't pretend to know whether I am even close to the way DBB does stuff.  There could be very good reasons why they can't or why doing so would take much, much longer or be even quicker (perhaps its just putting a tick in something) I really don't know.

I don't know what technologies DBB uses specifically (though I could make a decent guess)

Please don't think that I am telling the team how to do their jobs.  I was just being very generalised about how this could be achieved.  I just felt that I needed to reply to your post so that anyone coming in the future knows that I am specking very generally based upon my experience elsewhere.

Maybe I shouldn't have made that reply, it just came naturally to me as someone who works on open source projects.  Quite often its a good idea on such projects to give at least a basic layout of how things might work and in this case, I was giving an example about how the dev cycle might work and I did not mean my comment to be taken as the way things are actually done.  Just a very basic over view of maybe this, this and this is what would happen and this is a time based upon  this, this and this.

I would do an example of how such a field would look and how it would work. to back up my claims - but DBB isn't open source as far as I know and would not appreciate me doing so LOL.

But again, you are correct and I will avoid doing so in the future.