Skip to content

[UIK-5245][Documentation] Update illustrations#2968

Open
j-mnizhek wants to merge 17 commits into
release/v17from
update-doc-images
Open

[UIK-5245][Documentation] Update illustrations#2968
j-mnizhek wants to merge 17 commits into
release/v17from
update-doc-images

Conversation

@j-mnizhek
Copy link
Copy Markdown
Member

@j-mnizhek j-mnizhek commented May 28, 2026

Motivation and Context

Update to align the new styles:

  • illustrations in documentation
  • svg illustrations on showcase pages

Fixed:

  • ReferenceLine.Background placement in the example to match expected output
    Note for Lera: update screenshot tests for it

How has this been tested?

Manually.

Types of changes

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).
  • Nice improve.

@j-mnizhek j-mnizhek marked this pull request as draft May 28, 2026 12:48
@j-mnizhek j-mnizhek marked this pull request as ready for review May 28, 2026 14:51
Comment thread website/package.json
@@ -90,8 +90,9 @@
"node-watch": "0.7.3",
"picocolors": "1.0.0",
"postcss": "8.4.33",
"sharp": "0.34.5",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ilyabrower I moved sharp to dev deps and updated it to newer version, also added figma rest-api-spec - it's just types

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also I broke the lock file :'(

@sheila-semrush sheila-semrush requested a review from ilyabrower May 28, 2026 20:21
@sheila-semrush
Copy link
Copy Markdown
Contributor

@ilyabrower added you because I changed deps in /website

@sheila-semrush
Copy link
Copy Markdown
Contributor

Updated the figma illustrations script to work faster and to apply scaling only to big pics.
@j-mnizhek can you test it out and see if you're ok with the scaling logic? You can tune the width from which the scaling starts to apply.
We definitely need to run it one more time because on my test run I saw that not all illustrations currently are correct (e.g. in the content section).

j-mnizhek and others added 8 commits May 29, 2026 12:42
…and than set the correct value (#2933)

## Changelog

### @semcore/ellipsis

#### Fixed

- Values ​​with asynchronous initialization are not displayed in text
with ellipses.

<!--- Provide a general summary of your changes in the Title above -->

## Motivation and Context

<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How has this been tested?
I've added a test
<!--- Please describe in detail how you tested your changes. -->
<!--- For example: -->
<!--- I have added unit tests -->
<!--- I have added Voice Over tests -->
<!--- Code cannot be tested automatically so I have tested it only
manually -->

## Screenshots (if appropriate):

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [X] Bug fix (non-breaking change which fixes an issue).
- [ ] New feature (non-breaking change which adds functionality).
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected).
- [X] Nice improve.

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [ ] I have updated the documentation accordingly.
- [ ] I have added new tests on added of fixed functionality.

---------

Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
## Changelog

### @semcore/theme

#### Fixed

- Radii variables.

<!--- Provide a general summary of your changes in the Title above -->

## Motivation and Context

<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How has this been tested?

<!--- Please describe in detail how you tested your changes. -->
<!--- For example: -->
<!--- I have added unit tests -->
<!--- I have added Voice Over tests -->
<!--- Code cannot be tested automatically so I have tested it only
manually -->

## Screenshots (if appropriate):

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Bug fix (non-breaking change which fixes an issue).
- [ ] New feature (non-breaking change which adds functionality).
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected).
- [X] Nice improve.

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [ ] I have updated the documentation accordingly.
- [ ] I have added new tests on added of fixed functionality.

---------

Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
…2958)

Just a small fix in the documentation:

- Added common recommendations to the validation page
- Fixed and refferenced these recommendations in the Content in Modal,
Form and Notice guides
- Updated illustrations
- Removed outdated info from the Validation page (consulted with UX
writers)

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Bug fix (non-breaking change which fixes an issue).
- [ ] New feature (non-breaking change which adds functionality).
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected).
- [x] Nice improve.
await getIllustration(children, category, fileId);
}),
.forEach(async (page) =>
await getIllustration(page, category, fileId),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this won't work as you expexted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants