kalamuna / kalastatic

:electric_plug: Facilitate the front-end experience through Styleguides and Prototypes
https://kalamuna.github.io/kalastatic/
41 stars 14 forks source link

Page identifying information in Drupal Context #407

Open thiagodemellobueno opened 7 years ago

thiagodemellobueno commented 7 years ago

This is more of a "kalamuna drupal theme" issue, but seems good to discuss with team kalastatic in the kstat project space.

Invariably small edge cases in projects have us wanting to target things at a page level.

"Hide the support bar on the support page" or even "in the support page, and it's children"....

A tiny task, that is easy to acheive if say, we have identifying information printing in the template that isnt .page-node-6 which can vary between environments. But blooms into a larger issue when we need to bounce it back to a dev (who's really busy with other seemingly more pressing needs).

I propose ever page have the following information (where applicable) templateType (eg. landing page, article page, article-video' etc) page-slug (eg. support, prenatal-care) parent (when applicable, eg. womens-health)

now maybe not everything gets this treatment, but it seems like small overhead, for fluidity of process. It comes up at least once in every project, and I would like default behaviors of our tech that smooths out these recurring pain-points.

Thoughts?

andrewmallis commented 7 years ago

This sounds like a kalatheme issue @soniktrooth but what happens when we don't use it, like in D8 builds of late?