docs: fix search for tokens

[ninamarina]

docs: fix search for tokens

We discovered that for Android and iOS searching for tokens in figma format would not brung any results.
For example, searching for typography/body/md:

Before

Now

Obligatory GIF (super important!)

🛠️ Type Of Change

These types will increment the version number on release:

• Fix
• Feature
• Performance Improvement
• Refactor

These types will not increment the version number, but will still deploy to documentation site on release:

• Documentation
• Build system
• CI
• Style (code style changes, not css changes)
• Test
• Other (chore)

📖 Jira Ticket

No Jira

[github-actions]

✔️ Deploy previews ready!
😎 Dialtone preview: https://dialtone.dialpad.com/deploy-previews/pr-218/

[github-actions]

✔️ Deploy previews ready!
😎 Dialtone preview: https://dialtone.dialpad.com/deploy-previews/pr-218/

[yorbi-dp]

This looks great! Thanks a bunch for the quick fix.

[iropolo]

Okay so...

type of searches:

1. typography body md
2. typography/body/md
3. typography-body-md

Before:
CSS: 1,2,3
Android: 1
IOs: 1

Now:
CSS: 1,2,3
Android: 1,2
IOs: 1,2

---

Seems like there is no / or - tokens in Android and IOs, but there is - tokens on CSS.
What I suggest is remove / and just let 1 and 3 method.

CSS: 1,3
Android: 1,3
IOs: 1,3

I see it more naturally. Or, add - to Andoroid and IOs too to be consistent.

But this is a design decision probably, I'm not sure why we decide to use / to separate words.

There is also a noticed lag on switching to Token page, we should investigate it to improve. Technical improvement or Design Decision by splitting into sections.

[yorbi-dp]

But this is a design decision probably, I'm not sure why we decide to use / to separate words.

This is how Figma currently displays the style names. Hopefully, we will get an update soon to show the actual token name in the Figma UI.

[ninamarina]

There is also a noticed lag on switching to Token page, we should investigate it to improve

Yes, this is because the list is really long. The performance issue is in the render phase, so it's tricky to improve it, but we talked about if we can do some "lazy rendering" and add a loading state. I don't think pagination is possible since we have the table of contents with the anchor links.