Skip to content

set up rationale for theme gallery additions #1121

@12rambau

Description

@12rambau

In the documentation, we have a dedicated page to show projects that are using our documentation. There are currently 18 projects referenced and building them takes a huge part of the documentation process (so much that we prevent it in the CI).

In recent weeks some extra projects wanted to be added to the list and my fear is that people use it as an advertisement page for their project. For me, this page is more of a list of fancy examples to guide new users in customizing their projects. I'm not sure adding extra vanilla pydata-sphinx-theme is going to help anyone.

What do you think if in this gallery we split the images into 2 lists:

  • the pydata projects: the theme is initially dedicated to them, they should, by all means, be listed here
  • the custom one: a list of carefully selected projects that embed interesting customization (extra navbar, map background, translation) to guide the users in the customization process

I would also like to update our documentation to specify that docs referenced in the gallery need to have a "little something" 😄

What do you think?

PS: Of course, early adopters will be kept because we love them very much

Metadata

Metadata

Assignees

Labels

impact: block-releaseShould block a release from happening. Only use if this is a critical problem we don't want to shiptag: team processTeam process, governance, and guidelines

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions