Skip to content

Update Hiero artist documentation with new publisher. #309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 9, 2024

Conversation

rdelillo
Copy link
Contributor

Changelog Description

Update Hiero artist documentation with new publisher.

Testing notes:

  1. Built the documentation server locally to ensure all updates and pictures were OK.

@rdelillo rdelillo self-assigned this Nov 27, 2024
@rdelillo rdelillo marked this pull request as ready for review November 27, 2024 18:48
Copy link
Contributor

@MustafaJafar MustafaJafar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The updates make sense.
Let's fix some typos and merge.

Some notes (outside of the scope of this PR):

  • Screenshots in Hiero specific tools shows OpenPype menu
  • Nuke Build Workfile is this section related to Hiero docs? I think it's related to Nuke docs. maybe we can move them to nuke in this PR #307 .
  • Hiero admin docs is almost empty and show images from OpenPype
  • Hiero badge is referring to 0.1.0 and openpype hiero module link.

So, we may create an issue for updating hiero docs to match the next addon release.

Co-authored-by: Mustafa Jafar <mustafataherzaky@outlook.com>
@rdelillo rdelillo merged commit 08bf4fd into main Dec 9, 2024
@rdelillo rdelillo deleted the enhancement/adjust_hiero_pictures branch December 9, 2024 21:36
@rdelillo
Copy link
Contributor Author

rdelillo commented Dec 9, 2024

The updates make sense. Let's fix some typos and merge.

Some notes (outside of the scope of this PR):

So, we may create an issue for updating hiero docs to match the next addon release.

Thanks the review, that sounds good to me. I've created and assigned myself to: #317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants