Extract credits into a dedicated overridable component

[trueberryless]

What version of starlight are you using?

0.39.2

What is your idea?

I would like to propose that we extract the credits code and associated styles into a dedicated new component, which is overridable by the consumer.

Question(s) for discussion

• How do we handle the overlap with the credits configuration option? Should this check stay outside of the new component or be moved inside the new component?

  I see pros and cons for both sides:

  	Pros	Cons
  Check inside	When the user overrides and remove the check, they do not need to set credits to true, which avoids confusion.	The credits option becomes completely useless when the user removes it in their override. And if the user does not override and has credits disabled, we render an empty component.
  Check outside	The component is only rendered if the credits are enabled.	The user might get confused when overriding the component, but it doesn't appear because they have not enabled the credits.

Why is this feature necessary?

If I would like to not only credit Starlight as a documentation framework, but also e.g. Netlify as the deployment platform for my website, I currently have to override the whole Footer component, which includes many other components.

I think it makes sense to extract the credits in their own component because all other elements in the Footer have separate components too, so it also cleans up the footer.

Do you have examples of this feature in other projects?

No response

Participation

• I am willing to submit a pull request for this feature.