Thanks Cyril, I’ll do that tonight.
I’m drafting the documentation, do you prefer « devices » or « equipment »?
I can’t use « speaker » because the Sonos Port and Amp can also be added.
Appareils is the term most commonly used in Gladys.
Still talk about speakers, I think we need to be specific, the purpose of these tutorials is to rank on Google for specific keywords related to home automation topics, and I think talking about « speaker » is the right keyword ![]()
« Device » is super vague for this article…
I have just finished writing the documentation, feel free to provide feedback.
I’ll open the pull request (PR) afterwards.
Indeed, it’s much more responsive.
I have nothing to add for the moment regarding how the integration works.
Thanks for the tutorial @Tlse-vins, I made a few corrections.
I’m putting my corrections here so others can use them as inspiration for other tutorials ![]()
Title : « Sonos » → « Connect a Sonos speaker to your home automation ». You need a rich, actionable title so that a reader on Google will find this tutorial and then potentially discover Gladys.
Subtitle: « Edit devices » → « Rename/place a speaker in a room » → Concrete title (not abstract)
« Music box » → « Control music on the dashboard » → Same, a concrete title; the title must address a problem.
« box » → « widget ». The term « box » is internal to Gladys; I no longer use it in communications. Now, we say widget, which is the most commonly known term among the general public.
→ There’s a small tutorial missing to explain how to add the widget to the dashboard. Right now the widget just appears in the tutorial without explanation!
Thanks for your feedback, I’ll add that tonight.
It would be good to make the integrations’ documentation consistent.
And use this one as a template, right?
Go ahead!! ![]()
Honestly, don’t ask me for permission before doing things — I’m open to any help, I’ve always said that!
I was thinking about highlighting integrations on the site.
- Page « Integration » with all Gladys integrations using the same logo so that they look identical.
– the integration documentation pages, reproducing almost all of them as previously mentioned
And classify them into categories
So, just to keep a record, I’m waiting for your PR on the site’s GitHub before merging the Sonos integration into master for a first release ![]()
I’m doing this quickly, I’m in the process of doing a complete overhaul of the documentation.
How can I put it…
My first PR for the site — finally, I managed to make it and especially to test if everything was OK.
Here is the link to give you an idea of the new documentation.
It should serve as an example for the next ones.
If you have any feedback, I’m open to it.
The Sonos integration is available ![]()
I’m closing this thread to free up votes!