3.1 Documentation Updates

[Millu]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update
• Community Node Submission

Have you discussed this change with the InvokeAI team?

• Yes
• No, because:

Have you updated all relevant documentation?

• Yes
• No

Description

Related Tickets & Documents

• Related Issue #
• Closes #

QA Instructions, Screenshots, Recordings

Added/updated tests?

• Yes
• No : please replace this line with details on why tests
  have not been included

[optional] Are there any post deployment tasks we need to perform?

[lstein]

I haven’t completely reviewed but here are suggestions for the diffusion overview and node editor docs.

[Millu]

Thanks for the feedback @lstein! Docs have been updated to address it

[lstein]

Looks great!

[blessedcoolant]

We've updated the design of the nodes a bit and probably might change a bit more .. but more importantly the order of the sockets have been updated. But that's not a blocker for this PR. Just something to note for docs so they're up to date.

Rest of it seems good to me.

We can either merge this now or we can do this at the very end when we are releasing so it can be fully be up to date.

Squash and merge or retain commit history?

[Millu]

@blessedcoolant I think squash & merge - no need to clutter the commit history with documentation tweaks IMO

I'll make a to-do for myself to get another PR for node updates before this is released