shiv | command line utility | Build Tool library

I don't think the functions.php file has anything to do with it - usually HTML structures like this are created in template php files which are in the themes folder - either on the top level of that folder or as "template parts" in an according subfolder. You have to edit those( or actually those among them that are used by the pages you are referring to), changing all

However, since any not-selfmade theme will be updated every now and then, those changes would be overwritten with updated files when available, it would be necessary to create a child theme, which only contains those templates which you want to change (see also https://developer.wordpress.org/themes/advanced-topics/child-themes/). Then again, updated themes might contain template updates which are necessary, so you'd always have to check which details were updated in that particular template file, integrating it into your child theme templates or editing the updated original themes and using them in your child theme.

P.S.: I think the title of your question is a bit misleading: In the question text you are asking about certain title tags in the product pages, not about parts of the menu, aren't you?

As you can see, I don't have a serializer and the code works perfectly fine. So is this a good practice?

Is it mandatory? No, but it is often convenient.

A ViewSet is, as the name already suggests, a set of views. So typically it is not meant to implement only one functionality, but several functionalities. For example retrieve the list of records, retrieve details of a record, create a new record, update an existing record, and delete an existing record. We do not need a serializer for that, but it would require writing a lot of code. If you later add a field to your model, it would require updating most of these functions, which thus requires more effort.

A serializer is a tool to define often a bi-directional mapping between models and their serialized representation. It thus makes it more convenient to retrieve data from a model object as well as creating and updating such object. You thus specify how the mapping works, but you do not need to implement these three functions yourself, or at least most of the logic is abstracted away.

Using serializer thus is meant to reduce the amount of work, and make the software less error-prone.

For finding all the matches for your search word use:

You can basicaly redefine and reorder every grid element in a mediaquery after it. Just adjust the values to your liking

You need to define rules to rewrite URL and point to index.html in your reverse proxy server. Angular is a SPA with its own router. You need to redirect all requests to index.html which will deal with the routing.

This lock is not a transaction lock. As the docs say:

Note that the lock described here is a relatively heavy persistent document lock for file system emulation through WebDAV, not a relatively light transaction lock for database consistency.

https://docs.marklogic.com/xdmp:lock-acquire

Remove display: inline-block; in table should solve the issue.

To get a very close estimation of the number of Usernames per day, just run this (the number won't be accurate, see details here):

You can use np.ravel: