2026-03-24 00:09:11 +04:00
< div class = "legal-page" >
< div class = "legal-container" >
< h1 > Frequently Asked Questions (FAQ) 📌< / h1 >
< section class = "legal-section" >
< h2 > General Questions< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > What is Marketplace?< / summary >
< div class = "faq-answer" >
2026-07-05 00:51:29 +04:00
< p > Marketplace is an online marketplace where independent sellers list their products and services. Our goal is to provide a convenient and secure shopping environment — we do not manufacture or sell products ourselves.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I register on the platform?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Registration is easy: open our app within Telegram. Your profile will be created automatically as soon as you log in.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Is it safe to buy on the site?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Absolutely! All transactions are protected by modern encryption technologies (PCI DSS and 3D Secure). Your banking details are securely stored separately from our system.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Placing an Order< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I place an order?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p >
1️ ⃣ Find the product you like and add it to your cart.< br >
2️ ⃣ Open the cart and click "Place Order".< br >
3️ ⃣ Enter your delivery address and contact information.< br >
4️ ⃣ Choose a convenient payment method.< br >
5️ ⃣ Review and accept the public offer agreement.< br >
6️ ⃣ Complete the payment for your order.
< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Can I make changes to my order after purchase?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > If the seller has not yet shipped the product, contact our support — we will help adjust the order. However, once the product has been shipped, changes are not possible.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I cancel an order?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Contact us or the seller directly through order chats. As long as the package has not been shipped, cancellation is possible with a full refund.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Payment 💳< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > What payment methods are available?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > We accept:< / p >
< ul >
< li > Bank cards: Visa, MasterCard, MIR,< / li >
< li > Fast Payment System (FPS),< / li >
< li > Electronic wallets: YooMoney, QIWI,< / li >
< li > Cash on delivery (if offered by the seller).< / li >
< / ul >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > When will funds be charged from my card?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > The transaction is processed instantly, but the funds are temporarily held until you receive the product. Once you confirm receipt, the funds are released to the seller.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Why might my payment be declined?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Possible reasons for decline:< / p >
< ul >
< li > Insufficient funds in the account,< / li >
< li > Card transaction limit exceeded,< / li >
< li > Card blocked by the bank,< / li >
< li > Technical issues.< / li >
< / ul >
< p > We recommend contacting your bank for details.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Will I receive a payment receipt?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Yes, an electronic receipt will be sent to your specified email immediately after a successful payment in accordance with Federal Law No. 54-FZ.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Delivery 🚚< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Which delivery services are used?< / summary >
< div class = "faq-answer" >
2026-07-05 00:51:29 +04:00
< p > < strong > Digital products:< / strong > Marketplace automatically sends digital products (licenses, keys, certificates) to your email or personal account instantly after payment.< / p >
2026-03-24 00:09:11 +04:00
< p > < strong > Physical products:< / strong > The seller works independently with leading delivery services:< / p >
< ul >
< li > CDEK,< / li >
< li > Russian Post,< / li >
< li > Boxberry,< / li >
< li > DPD,< / li >
< li > Yandex.Delivery.< / li >
< / ul >
< p > The delivery method for physical products is chosen based on the seller's preferences and destination.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How much does delivery cost?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > < strong > Digital products:< / strong > Delivery is free — the product arrives to your email instantly.< / p >
< p > < strong > Physical products:< / strong > The price is determined by the seller and depends on the weight, dimensions, chosen method, and delivery region. The final cost is displayed at checkout.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > What is the delivery time for my order?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > < strong > Digital products:< / strong > Instant delivery to email (within a few minutes after payment).< / p >
< p > < strong > Physical products< / strong > (estimated times):< / p >
< ul >
< li > CDEK: 2– 7 business days,< / li >
< li > Russian Post: 5– 14 business days,< / li >
< li > Boxberry: 2– 5 business days,< / li >
< li > DPD: 1– 3 business days,< / li >
< li > Yandex.Delivery: same day (if available in your city).< / li >
< / ul >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I track my package?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > You will receive a tracking code via email and can view the order status in your personal account. You can track the package on the official website of the chosen courier service.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > What should I do if the product arrived damaged? ⛑< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Inspect the product in front of the courier. If defects are found, fill out a refusal of acceptance report and immediately notify the seller and support service.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Returns and Exchanges ✅< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Can I return a product?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Yes, the law allows you to return a quality product within 7 days of receipt. Defective items are returned under special rules.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Which products cannot be returned?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Products listed in Russian Government Decree No. 2463 cannot be returned: medications, cosmetics, underwear, activated digital products, and custom orders. See details in the < a [ routerLink ] = " ' / return-policy ' | langRoute " > "Return Policy"< / a > section.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I get a refund?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p >
1. Notify the seller of your intention to return the product.< br >
2. Return the product in its original packaging.< br >
3. The seller will inspect the product and refund the amount using the same payment method (up to 30 days for the refund to process).
< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Who pays for return shipping?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > The buyer pays for return shipping of quality products. If a defect is found, the seller covers the costs.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Warranty 🔧< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Is there a warranty on products?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Most of our products come with an official manufacturer's warranty. The period ranges from 12 to 36 months and is indicated on each product page.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I use the warranty?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Notify the seller of the defect, attaching photos of the damage and the warranty card. The seller will handle repair or replacement of the product.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > What is not covered by warranty?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Mechanical damage, consequences of improper use, unauthorized repair, moisture exposure (if not protected), and natural wear — none of these are covered under warranty.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Security and Privacy 🔐< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do you protect my personal data?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > We use modern SSL/TLS encryption methods, do not store card details, and comply with Federal Law No. 152-FZ on personal data protection. Details are available in our < a [ routerLink ] = " ' / privacy-policy ' | langRoute " > Privacy Policy< / a > .< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > Who has access to my data?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Only your seller for order processing and delivery services. Data is not used by third parties for marketing without your permission.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I delete my account?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > Send a request to our support service to delete your account. The account and personal information will be removed within one month.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Information for Sellers 📋< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I start selling on the platform?< / summary >
< div class = "faq-answer" >
2026-07-05 00:51:29 +04:00
< p > To join our sellers, contact our support service by email at < a href = "mailto:the Contacts page" > the Contacts page< / a > .< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > What is the platform's commission?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > The commission depends on the product type and sales volume. You can find out the exact terms during registration.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > When will I receive payment for a sale?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > The seller receives funds after the customer confirms receipt of the product or two weeks after delivery if the customer has not reported any issues.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Customer Support 💬< / h2 >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How do I contact support?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p >
2026-07-05 00:51:29 +04:00
✉️ < strong > Email:< / strong > < a href = "mailto:the Contacts page" > the Contacts page< / a > < br >
2026-03-24 00:09:11 +04:00
📞 < strong > Phone (Russia):< / strong > < a href = "tel:+79264593157" > +7 (926) 459-31-57< / a > < br >
📞 < strong > Phone (Armenia):< / strong > < a href = "tel:+37494861816" > +374 94 86 18 16< / a > < br >
🏢 < strong > Office hours:< / strong > 10:00– 19:00 (MSK)< br >
❄️ < strong > Technical support is available 24/7.< / strong >
< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< details class = "faq-item" >
< summary > How long does it take to get a response?< / summary >
< div class = "faq-answer" >
2026-03-24 00:09:11 +04:00
< p > During business hours, you will receive a response within two hours. On holidays and weekends, delays of up to 24 hours are possible.< / p >
fix(storefront): premium UX polish for static pages
- faq-{ru,en,hy}.component.html: convert each FAQ entry from an always-
expanded <div>/<h3> block into a native <details class="faq-item">/
<summary> disclosure, reusing the global expander-chevron pattern
already defined in styles.scss (no bespoke accordion component built);
answer body wrapped in .faq-answer for spacing
- faq.component.scss: restyle .faq-item for the details/summary shape
(summary uses tokenized font-size/weight, focus-visible ring, [open]
state gets a stronger shadow instead of the old always-on hover-lift);
hardcoded `all 0.3s ease` replaced with --transition-normal on the
specific properties that change; added a reduced-motion override
- shared-legal.scss: hardcoded `transition: all 0.3s ease` (4 call sites:
info-card, features-list feature, contact-item/contact-link,
contact-email) normalized to --transition-normal on transform/
box-shadow/background; paragraphs and lists get max-width: 70ch so
long-form legal/info text keeps a readable line length within the
wider 900px .legal-container
- static-page.component.scss (CMS-driven static-page renderer): spacing
converted to --space-* tokens; prose now capped at 70ch; added actual
content styling (headings, lists, links, images, blockquote, table)
for arbitrary CMS-authored HTML rendered via [innerHTML], since the
previous rules only styled h2/h3 margins and left every other tag
unstyled; line-height moved to --line-height-relaxed token
Build verified green via `npm run build`.
Out of scope / skipped:
- info/contacts has no contact form (plain link list) - no app-input/
app-form-field polish applicable
- no breadcrumbs/anchor nav exist on any page in scope - nothing to
align focus-visible on
- legal-page/info scss files (about, delivery, guarantee, company-
details, payment-terms, privacy-policy, public-offer, return-policy)
already used design tokens with no hex literals and had no accordion/
form elements - left untouched
- shared-legal.scss's border-left accent on .legal-section/.info-box/
.highlight and the fadeIn entrance animation durations left as-is;
pre-existing sitewide pattern, not a new introduction, changing it is
a redesign call outside this pass's scope
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 12:07:14 +04:00
< / div >
< / details >
2026-03-24 00:09:11 +04:00
< / section >
< section class = "legal-section" >
< h2 > Need Help?< / h2 >
2026-07-05 00:51:29 +04:00
< p > If you have any additional questions, please contact us at < a href = "mailto:the Contacts page" > the Contacts page< / a > — we will promptly resolve any of your questions!< / p >
2026-03-24 00:09:11 +04:00
< / section >
< / div >
< / div >