Closed freakwriter closed 3 weeks ago
Name | Link |
---|---|
Latest commit | 7f9bc4b2fc7cf4718ebf2625d482d4ee83ea7b67 |
Latest deploy log | https://app.netlify.com/sites/n8n-docs/deploys/667bc42ed7a5e20008152e83 |
Deploy Preview | https://deploy-preview-2183--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.
Overall readability score: 41.16 (🟢 +0.09)
File | Readability |
---|---|
declarative-style-parameters.md | 62.32 (-) |
index.md | 67.82 (-) |
programmatic-style-execute-method.md | 56.57 (-) |
programmatic-style-parameters.md | 63.44 (-) |
standard-parameters.md | 75.47 (-) |
structure.md | 60.62 (-) |
@StarfallProjects as discussed, I've created a subdirectory and split the h2s out into individual pages. Let me know what you think.
I briefly toyed around with manually adding HTML to achieve something similar to the data transformation functions, but quickly realized that was likely going to be more work than using the .yaml file and plugin, so I backed out those changes. I went back and forth on keeping the programmatic-style execute method as its own page, since the programmatic-style parameters is a pretty small page to begin with. Let me know if you think it would be better to collapse into a single page.
I wasn't 100% certain what metadata to use at the top of each page; I used a couple other pages for reference and did my best, but please review that especially.
I don't think a redirect for the removed single-page is necessary, since the URL ends up being the URL for the subdirectory itself, which feels correct, but let me know if I made any faulty assumptions there.
Includes these updates: