You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
layout.tsx uses a hard-coded Site Name in the <title> tag and in the page header. Ideally, that would use the value from Drupal's Site Name config. The design should also probably include the site slogan value from Drupal (like most Drupal front-end themes do).
I'm not sure how to get this data out of Drupal though since json:api is strictly entity-based.
The text was updated successfully, but these errors were encountered:
There is https://www.drupal.org/project/jsonapi_site but it doesn't look like it uses jsonapi properly so I doubt it will plug into openapi natively. For that reason alone, its not likely we'd add it to Acquia CMS unless its infrastructure changed.
I'm wondering if this is one of those features that would be nice for a demo but when people actually build applications, they would just rip it off to reduce complexity. 🤷♂️ The site name config in most cases is something that is configured once and then never changed again.
layout.tsx uses a hard-coded Site Name in the
<title>
tag and in the page header. Ideally, that would use the value from Drupal's Site Name config. The design should also probably include the site slogan value from Drupal (like most Drupal front-end themes do).I'm not sure how to get this data out of Drupal though since json:api is strictly entity-based.
The text was updated successfully, but these errors were encountered: