I'm aware of trac, before making a feature request there I'd figure I'd get the temperature here. Simply - so many sites these days turn comments off, and there's a cottage industry around blocking comment spam besides, does WordPress even need comments as a core feature? I feel it might be better to move the functionality off into a plugin that ships with WordPress in 8.0, and then maybe even remove it entirely from core in 9. Thoughts?

I've been away from Drupal too long, sucked into WordPress. My company has an ongoing problem with the org chart - specifically it's advertising. I think I can use Drupal to manage this, but I have a lot of rust and haven't worked intensely with it in years (when 8 was current).

The Database I've sketched out uses a UUID approach to coordinate it's contents with outside databases it must stay in sync with, including the aforementioned WordPress site which I will be getting post information from. I'm trying to keep fields on only one table if feasible.

I'm going to go over some of the structure I designed without considering Drupal as the administrating program, so I am open to letting this change as long as I can get the same end result. Note also that this design is informed by schema.org entries for Medical Organizations - of which my company is one (and a fairly large one)

Everything is an Entity. This is the only table with an autoincrement field. Any entry created on any other table starts with an entity entry. For example, if I'm adding a provider the Entity table holds the mappings to the other databases, the entry name and a schema.org description, the person table contains information about the provider's name (given name, surname, which comes first since we have providers with Asian names, gender, etc), and the provider table contains information on whether they accepting new patients, the URL to their scheduler, their NPI (think social security number for medical professionals).

The provider table also cross-references with locations with additional information about which days the provider is at that location and which one is their primary. Another cross reference is which hospitals they have admission privileges to, and another maps which organizations they belong to. Yet another details their education, and their certifications, and the insurances they accept.

The UUID comes into play because hospitals also have insurance company contracts. So that table needs to be joinable with providers or hospitals.

So when I have an edit view of a provider I want the form to present this information cleanly without the user needing to go through multiple forms

I think Drupal can do this out of the box. If not out of the box I have written modules before, but in that event why use Drupal instead of just standing this up in Laravel or Symfony? I'm looking something that is resilient, but I don't want to spend more than a month on this if I can help it.

I have been tasked with rebuilding a rather huge Intranet site with my company. The core of the current Intranet is on WordPress, but huge swathes are in SharePoint and there are multiple endpoints I need to pull data from and present on certain pages using GraphQL. My company is in the healthcare sector, so HIPPA compliance must be met.

The two front runner proposals in my mind at the moment is Gatsby to just pool the data off the existing servers, and eventually remove the WordPress sites entirely and migrate their content to Drupal.

(EDIT: I've been notified that Gatsby is more or less dead).

My proposal is to either use Drupal directly, having it replace the WordPress sites and link up to the SharePoint hive with the Sharepoint Connector module, or go to a headless arrangement with a presentation server of some sort in front of all these service servers, and then replace WP with Drupal at a later date.

I'm familiar with Drupal and prefer it to WordPress, but I have to convince stakeholders. I've never done a proposal this large before. I'm looking for case studies and examples to build my case. I've already combed through a few of the cases linked on the Drupal Healthcare pages.

The thought of pushing Gatsby first and then bring in Drupal to headlessly back it has occurred to me and I'd be interested in hearing thoughts on that configuration as well.

Thank you for your time.