Reorg of the table of contents #562
Conversation
1. Edited the page 2. Update the action name on the landing page
I don't think we have bevel faces as a standalone tool anymore. I think it's bevel edges, with the face edit mode selected.
Updated
Updated Bridge Edges and clarified (I hope) what open edges mean.
Since you can now bevel faces from the same tool, I replaced the example
Replaced the example because this tool now does two things
…Technologies/com.unity.probuilder into suearkinunity-DOCATT-5849
Plus two small edits to other pages
Reorder the whole thing
|
Sue Arkin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
suearkinunity
changed the title
My thinking was that a user won't know whether they need a loop or ring selection until they've read the docs. Therefore, those two options need to be directly compared.
Making it match Msater
But I have some questions
I was using a couple of wrong files. Also, I'm killing the Tools vs Actions page. First of all, we can't keep calling them actions because Actions is a category of Actions, and we can't do that to our poor users. Second, this page duplicates information that's better presented in its own context, such as creating meshes and the so-called actions. The conceptual difference between tool and action is really not something users need to worry themselves with.
Got rid of the inset page, because it's just a way to use Extrude
So I removed it
Changing to match 5835's changes to the edit pages, which include merging the tips/common page.
It was wrongly nested
| @@ -0,0 +1,26 @@ | |||
| # Materials, Shaders, Textures, and UVs | |||
There was a problem hiding this comment.
This page still needs to be added to the TOC.
There was a problem hiding this comment.
Replaced by workflow-texture-mapping... not sure why I ended up with three files that have exactly the same content
There was a problem hiding this comment.
Replaced by workflow-texture-mapping... not sure why I ended up with three files that have exactly the same content
|
Something here is very odd. I'm going to have to rebuild this locally and see what's what. |
|
All TOC changes - including all the action ref changes - are now in this PR. |
Purpose of this PR
This PR:
It doesn't reflect the work done on the Actions Reference area in DOCATT-5849, where I also messed with that area and broke it down to chunks. PR 561, currently in draft, shows that. In this PR, I just removed all those pages so I don't have to deal with them in two PRs.
Links
Jira: DOCATT-6821
Comments to Reviewers
This isn't finalised - I didn't check links, landing pages etc. I wanted to agree on a TOC first.