https://docs.blender.org/manual/en/dev/editors/uv_image/uv/editing/layout.html#export-uv-layout
is actually an addon but we document it like it is an eternal feature.
This might be a larger question but how do we document add-ons enabled by default.
https://docs.blender.org/manual/en/dev/editors/uv_image/uv/editing/layout.html#export-uv-layout
is actually an addon but we document it like it is an eternal feature.
This might be a larger question but how do we document add-ons enabled by default.
I think addons that are enabled by default should be documented as builtin features. It's basically an implementation detail if it's an addon or not, why should the user care?
The fact that it's an addon only matters in that it can be disabled, but that's not important I think.
I do not have a strong opinion here but I think we should keep this information in the manual. Having it elsewhere can make it harder to find. This, however, would also mean that we should port all the import/export add-ons to the manual. @Vuk Gardašević (lijenstina) @Campbell Barton (campbellbarton) Any thoughts here?
I think that adding a notice box about it being an add-on with the default name / category could be enough. Just in case if for some reason, the user has disabled it.
The inclusion of documenting all the default start-up add-ons could be postponed until the 2.8 finalization.