Doc 1021 Node overhaul: Google Sheets

[ayatnkw]

Changes

• Added detailed description for each operation and associated options

[netlify[bot]]

✅ Deploy Preview for n8n-docs ready!

Name	Link
🔨 Latest commit	216f80ae3cbb1056a0546ed9b32d92f5c095e795
🔍 Latest deploy log	https://app.netlify.com/sites/n8n-docs/deploys/66e0aad694049a0008f1f055
😎 Deploy Preview	https://deploy-preview-2333--n8n-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions[bot]]

Overall readability score: 43.8 (🟢 +0.06)

File	Readability
node-options.md	72.33 (-)
document-operations.md	61.58 (-)
index.md	61.2 (-)
sheet-operations.md	85.16 (-)

View detailed metrics

🟢 - Shows an _increase_ in readability 🔴 - Shows a _decrease_ in readability File | Readability | FRE | GF | ARI | CLI | DCRS --- | --- | --- | --- | --- | --- | --- [node-options.md](https://github.com/n8n-io/n8n-docs/blob/216f80ae3cbb1056a0546ed9b32d92f5c095e795/_snippets/integrations/builtin/app-nodes/googlesheets/node-options.md "_snippets/integrations/builtin/app-nodes/googlesheets/node-options.md") | 72.33 | 58.38 | 8.13 | 8.7 | 9.79 | 7.35   | - | - | - | - | - | - [document-operations.md](https://github.com/n8n-io/n8n-docs/blob/216f80ae3cbb1056a0546ed9b32d92f5c095e795/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/document-operations.md "docs/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/document-operations.md") | 61.58 | 42.88 | 7.55 | 12.3 | 13.96 | 6.75   | - | - | - | - | - | - [index.md](https://github.com/n8n-io/n8n-docs/blob/216f80ae3cbb1056a0546ed9b32d92f5c095e795/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/index.md "docs/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/index.md") | 61.2 | 58.18 | 9.33 | 11.4 | 11.82 | 8.05   | - | - | - | - | - | - [sheet-operations.md](https://github.com/n8n-io/n8n-docs/blob/216f80ae3cbb1056a0546ed9b32d92f5c095e795/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/sheet-operations.md "docs/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/sheet-operations.md") | 85.16 | 67.76 | 6 | 8.5 | 9.85 | 5.04   | - | - | - | - | - | - Averages:   | Readability | FRE | GF | ARI | CLI | DCRS --- | --- | --- | --- | --- | --- | --- Average | 43.8 | 35.2 | 11.53 | 14.79 | 14.3 | 8.49   | 🟢 +0.06 | 🟢 +0.05 | 🟢 +0.01 | 🟢 +0.01 | 🟢 +0.01 | 🟢 +0

View metric targets

Metric | Range | Ideal score --- | --- | --- Flesch Reading Ease | 100 (very easy read) to 0 (extremely difficult read) | 60 Gunning Fog | 6 (very easy read) to 17 (extremely difficult read) | 8 or less Auto. Read. Index | 6 (very easy read) to 14 (extremely difficult read) | 8 or less Coleman Liau Index | 6 (very easy read) to 17 (extremely difficult read) | 8 or less Dale-Chall Readability | 4.9 (very easy read) to 9.9 (extremely difficult read) | 6.9 or less

[ayatnkw]

I played around with the formatting and thought about maybe having the Options section as a table instead, what do you think? @freakwriter @nik8n

• Here's the original format
• Here's the options as tables

[freakwriter]

@ayatnkw Options are handled somewhat inconsistently across nodes. Things I like about your table approach:

• The Options section has its own subheading. I'd do this whether you're using a table or not.
• The different options for Recalculation Interval as a separate sub-list rather than stuck in a paragraph of text. I'd similarly use this format whether you're using a table or not, for easier scanning/reading. (I'd also suggest using this format for the options for Locale.)

One of the advantages to the table could be splitting out the description of what the option's used for from the actual options you can choose from and/or having some kind of "Related resources" section that could contain the links to relevant external docs. I might try playing around with that to see if we can make the table do even more than it's currently doing, something like:

| Option | Description | Configuration | Related resources |

To me, that takes it from just a change of presentation to one of really making the most of the format change to convey more information faster, so the format does more for us. Do you want to try that? Should I try adding a suggested commit to show what I'm thinking in more detail?

[nik8n]

Wouldn't we move the operation details to a different page here as well? Just like we did with Telegram?

That would probably have a few advantages:

1. The site would be cleaner and easier to scan
2. We could allow options to be a header on the sub-page without cluttering it too much.

In any case, I think I slightly prefer the table since it feels a little cleaner. But I think we should always have sub-pages for the operation details.

[freakwriter]

I hadn't looked at the overall length here, but I suspect Nik's suggestion is a good one, to play around with the subpage layout for Document vs. Sheet Within a Document operations...that might give us some more visual space to work with and then having the subheading for Options isn't going to feel as overwhelming. @ayatnkw maybe this would be a good one for us to work together on to play around with that, and then we can see if this number of operations feels like it's close to the cutoff for having the subpage format??

[ayatnkw]

Thanks for the comments, I'll put the operation details in separate pages and play around with the table formatting.

One thing I'm uncertain about with the table formatting is how well the AI assistant will read it. I'm also not so sure about having too many columns because of the limited width on the docs page (I'd say max 3 columns) I'll play around a bit and maybe @freakwriter and I can talk about it on Monday.

[ayatnkw]

@nik8n @freakwriter made suggested changes, would be great if you could take another look!

[nik8n]

Looks good to me. Two pieces of feedback:

1. I think we could still add a little more "FAQ" to the page.
2. On Append an Array I would mention the AI transform node and the split out node, no? Both of these options seem much easier than using a code node. And maybe we also want to get a little more into detail here and provide examples or a how-to? (kinda like the cookbook pages we sometimes have)

[freakwriter]

@nik8n I've incorporated some of my own edits plus added the nodes you mentioned. A more detailed set of examples/cookbook would likely be good long-term, but in the interests of trying to get some changes out the door, I've just provided brief summaries for now. Let me know what you think.