Post installation

I was pretty good at Drupal 7, but I've been away for a long time now. I'm building a new website, using Drupal 10 and a custom Olivero sub theme. Feels like I'm learning from scratch again.

To create my home page, do I just create a basic page (existing content type), or do I use the Views frontpage view that the default Drupal home page links to? Or are they the same thing? I'm very confused, and I can't find anything in the forums or documentation that covers this. 

Can someone please point me in the right direction? I can take it from there. Thank you all so much!

I have a number of colorbox modals that contain various contact forms. I'm using colorbox simple load and colorbox inline as triggers in most cases.

Hello all - My project will use the same code base to host different sites. The difference between these different sites is minor:

1. For example, if I have a user profile data field (let's call it user_profile_ data1) that is link to a list of taxonomy terms, I want to display user_profile_data1 using taxonomy list1 on site1, but on site2 I want to use taxonomy list2 for the same data field. These lists have mostly the same terms with some minor differences.

What database is best compatible for Drupal website?

We are using MySQL database. Is there any other DB which is giving a better result?

In Drupal CMS I have almost gotten cleared for automatic updates but a folder introduced by the host company which they use to manage their custom plugins, the folder called .nc_plugin has blocked the way.

This is a shared hosting account.

The error message is

Your site does not pass some readiness checks for automatic updates. It cannot be automatically updated until further action is performed.

RecursiveDirectoryIterator::__construct(/home/username/.nc_plugin): Failed to open directory: Permission denied

I installed Drupal CMS with Composer. Which pulled in many recipes, at version 1.0.3. The recipe of note -- drupal_cms_starter -- pulls in the CMS Olivero theme -- drupal_cms_olivero, but somehow locks Olivero at version 1.03.

CMS Olivero is now at version 1.1, and the site nags that the theme is out of date.

Using Composer, per regular procedure, to update the theme alone fails, because the cms_starter recipe has locked the theme at version 1.0.3.