How to change color

[EtienneC30]

In the CUSTOMIZE.md file it is written here that

A variety of beautiful theme colors have been selected for you to choose from. In v1.x, theme tokens are gem-owned by default. To customize colors locally, either use _config.yml theme settings (for light/dark scheme selection) or create local _sass/_themes.scss and _sass/_variables.scss override files in your starter repo (these override gem defaults).

But there are no instructions about how to choose a color theme or what the scss files should look like. After a lot of looking I found corresponding files in my computer which I overrode as indicated I think but it did not apply the changes (when I pushed it did not even trigger the deploy job). But I feel like there should be a simpler way so I probably missed something. Any help appreciated 🙏

[krotname]

[EtienneC30]

Thank you very much for the quick reply! I am quite puzzled though that the deploy does not work, as I did push the files with the right names and locations. However the comment-integration-tests fails with

Starter style contract check failed:

• Starter must not own core component path _sass; move ownership to the corresponding gem.

Maybe that's relevant? In any case, by changing the about.md file the site got deployed and the changes got applied!! Thank you.

[krotname]

Small correction to my earlier answer: creating _sass/... in the starter repo was not good advice for the current v1 starter.

The failing check is real: test/style_contract.js explicitly forbids the starter from owning _sass, _includes, _layouts, etc. Those paths belong to the gem side. So the deploy failure was not a generic Pages trigger problem; it was the starter contract rejecting the local _sass override I suggested.

The confusing part is that docs/QUICKSTART.md still says to edit _config.yml and search for theme_color, while the current _config.yml does not appear to expose that key. So I would treat this as a docs/theme-contract gap rather than something you should work around by adding _sass to the starter.

Since your about.md change deployed, the Pages workflow itself is fine. For palette changes in v1, I would wait for/ask for a supported starter-level override or change the corresponding gem/theme source, not keep local _sass in the starter.

[EtienneC30]

That's what I understood, but I find it strange that things are so complicated when CUSTOMIZE.md says

This template was specifically designed to be accessible to academics and researchers from all backgrounds. You can create a fully functional website by simply editing configuration files and adding content in Markdown, no coding required.

It seems to me that there is stuff to do to adapt the v1 to this claim. I have no idea how I can "change the corresponding gem/theme source".

[jenna-jordan]

I would also like to change the color. I have read the docs. I have absolutely no idea how to change the colors. The docs are, furthermore, inaccurate or out of date.

In the Quickstart, it states:

Theme color: Edit _config.yml, search for theme_color

But theme_color appears nowhere in _config.yml.

In Customize, this:

Changing theme color
A variety of beautiful theme colors have been selected for you to choose from. In v1.x, theme tokens are gem-owned by default. To customize colors locally, either use _config.yml theme settings (for light/dark scheme selection) or create local _sass/_themes.scss and _sass/_variables.scss override files in your starter repo (these override gem defaults).

... Is a whole bunch of gobbledy-gook.

Changing the color is one of the most basic and first things most people want to do to customize the site. It makes me concerned that this this theme and the docs were written by AI and are no longer usable. As long-term user of this theme who has decided to update to the latest version, it makes me quite concerned.

[krotname]

You are right that the current docs are inconsistent here.

For the current v1 starter, I would not follow the _sass override wording unless a maintainer confirms it. The starter tests reject owning _sass, _includes, _layouts, etc., so the documented color-customization path conflicts with the starter contract.

The actionable issue is probably: either restore a supported starter-level theme_color / palette setting in _config.yml, or update the docs to say color changes require changing the gem/theme package rather than only editing the starter repo. Right now I do not see a clean no-code starter-only color switch.

[danialzivehdadr]

شرمند یه چیزی تغییر کرده حالت استاندارد شکل میگیره