Skip to content

docs: harmonize component documentation#842

Closed
kaljarv wants to merge 4 commits intomainfrom
feat-docs-site
Closed

docs: harmonize component documentation#842
kaljarv wants to merge 4 commits intomainfrom
feat-docs-site

Conversation

@kaljarv
Copy link
Contributor

@kaljarv kaljarv commented Dec 14, 2025

WHY:

Contributes to #322

What has been changed

  • Harmonized all Svelte component documentation
  • Updates to other documentation
  • Gitignore local Claude settings

Check off each of the following tasks as they are completed

  • I have reviewed the changes myself in this PR. Please check the self-review document
  • I have added or edited unit tests.
  • I have run the unit tests successfully.
  • I have run the e2e tests successfully.
  • I have tested this change on my own device.
  • I have tested this change on other devices (Using Browserstack is recommended).
  • I have tested my changes using the WAVE extension
  • I have tested my changes using keyboard navigation and screen-reading
  • I have added documentation where necessary.
  • Is there an existing issue linked to this PR?
  • I have cleaned up the commit history and checked the commits follow the guidelines

@kaljarv
Copy link
Contributor Author

kaljarv commented Dec 14, 2025

@claude, review

@github-actions

This comment was marked as resolved.

Apply these principles to all components:

1. Each property is defined in a separate .type.ts file in a type called
<ComponentName>Props.
2. That file is the prime source of truth for the properties' descriptions
3. The type is imported to the component as $$Props
4. All props are typed using that.
5. At the top of the file, there is a Svelte doc with `@component`
6. The `### Properties` section is generated from the type file such that
`@default` is replaced with 'Default:' and the value is backticked.
7. The element or component onto which $$restProps is passed and which is
the base of the props type, is mentioned last as like '- Any valid
attributes of a `<figure>`
element'
8. Any other prop related headings can be removed along with their contents,
unless they contain relevant information missing from the type, in which case add the info
to the type
9. If the component doesn't follow this paradigm, create the type file,
export it from index.ts and import it to the component

Co-Author: Claude
@kaljarv kaljarv changed the title feat: docs site docs: harmonize component documentation Dec 14, 2025
Base automatically changed from feat-new-admin-ui to main January 4, 2026 19:13
@kaljarv
Copy link
Contributor Author

kaljarv commented Jan 25, 2026

Superseded by #847

@kaljarv kaljarv closed this Jan 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant