EDK-Tech

Not sure how difficult this would be to implement but.
For the CMS/Pages application: The ability to choose different schema types for different databases and pages, such as an about page, using to json-ld generator. 
Also since different schema types have different properties, the ability to match/ choose schema properties with custom field types. 
This is similar to how yoastSEO and similar WordPress SEO plugins works.
I'm not sure if this is fully possible with the Google data layer but that seems a bit complicated to implement.

Not sure how difficult this would be to implement but.
For the CMS/Pages application: The ability to choose different schema types for different databases and pages, such as an about page, using to json-ld generator. 
Also since different schema types have different properties, the ability to match/ choose schema properties with custom field types. 
This is similar to how yoastSEO and similar WordPress SEO plugins works.
I'm not sure if this is fully possible with the Google data layer but that seems a bit complicated to implement.

Not sure how difficult this would be to implement but.
For the CMS/Pages application: The ability to choose different schema types for different databases and pages, such as an about page, using to json-ld generator. 
Also since different schema types have different properties, the ability to match/ choose schema properties with custom field types. 
This is similar to how yoastSEO and similar WordPress SEO plugins works.
I'm not sure if this is fully possible with the Google data layer but that seems a bit complicated to implement.

Not sure how difficult this would be to implement but.
For the CMS/Pages application: The ability to choose different schema types for different databases and pages, such as an about page, using to json-ld generator. 
Also since different schema types have different properties, the ability to match/ choose schema properties with custom field types. 
This is similar to how yoastSEO and similar WordPress SEO plugins works.
I'm not sure if this is fully possible with the Google data layer but that seems a bit complicated to implement.

Not sure how difficult this would be to implement but.
For the CMS/Pages application: The ability to choose different schema types for different databases and pages, such as an about page, using to json-ld generator. 
Also since different schema types have different properties, the ability to match/ choose schema properties with custom field types. 
This is similar to how yoast works. 
I'm not sure if this is fully possible with the Google data layer but that seems a bit complicated to implement.

Are you using the recent version?

It depends on your server. As long as those directories are writable by the software, then you will be fine regardless of what the actual permissions are.

You can remove the ID for specific pages if you wanted to do that, but you cannot remove them for pages in general. For example, if you wanted to add a FURL without an ID to a specific topic you would be able to do that, but you cant automatically make one for every topic that is created. This is because the ID is required to identify that item.
With regard variables, you wil be able to see the variables that are being used by the current furls as an example of what can be used. So for example if you edit the one for the forum links, you will see 
forum/{#id}-{?}
The ? is always the position of variable that do not appear in the real URL. In this case the forum name, but it could be the topic name in a topic link for example. The #id of course is the ID.
There is no list available as such