Skip to content

Conversation

@hojo-odoo
Copy link
Contributor

This PR restructures the entire Inventory scope, organizing all documentation within three new main categories: "Product management", "Shipping and receiving", and "Warehouses and storage". Each main category also contains multiple subcategories to further organize the documentation within.

@robodoo
Copy link
Collaborator

robodoo commented Aug 31, 2023

@C3POdoo C3POdoo requested review from a team August 31, 2023 19:18
@hojo-odoo hojo-odoo removed request for a team August 31, 2023 19:18
Copy link
Contributor

@jcs-odoo jcs-odoo left a comment

Choose a reason for hiding this comment

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

Hi @hojo-odoo !

Cool work! I know how difficult it can be to reorganize docs and update paths everywhere ^^

⚠️Whenever you have the final structure, create the appropriate redirect rules in the /redirect/ folder at the root of this repository. This PR can't be merged without them.

As for the structure itself, I wrote a few recommendations in the files, but I would also like to give an idea, although I don't know if it would apply well in this case...

To reduce the number of levels and to make it easier to navigate, what if all the sub-categories were categories by removing the three main categories (product_management, warehouses_storage, shipping_receiving). It would mean more head-scratching to get the categories right, but that could be cool :) That's what we did for Accounting.

Another part of the restructuration could be to update some doc titles.

Good luck with this :)

cc @xpl-odoo for the doc structure team

@hojo-odoo
Copy link
Contributor Author

Hey @jcs-odoo,

Thank you for all of your suggestions.

I would like to keep the three top-level categories. The logic behind them was to separate documentation by:

  • Product Management: how products are managed on an individual level.
  • Warehouses and Storage: how products are managed collectively and stored.
  • Shipping and Receiving: how products enter and leave storage.

There are a lot of Inventory documents, and I think organizing them this way makes them easier to parse through.

That being said, I agree with your suggestion about rethinking the "Advanced Operations" subcategories. I will organize those docs into more specific subcategories.

As for making updates to individual docs (changing names, updating content), I'd like to keep this PR focused on updating the structure. This is already a very complicated PR, and I'd rather not get too in the weeds by making changes to individual docs. I think that would be better to do through targeted updates, once the new structure has gone live.

Thanks,
hojo

@hojo-odoo hojo-odoo force-pushed the 16.0-inventory-scope-restructure-hojo branch 2 times, most recently from 9316daa to 085c1d8 Compare November 22, 2023 22:13
@StraubCreative
Copy link
Contributor

Nice work clearing the conflicts @hojo-odoo 👍
Next we'll want to update the redirects.txt file for all of the relevant RST path changes that were made in the PR.
Let's try to merge by end of next week, if possible, so conflicts don't keep piling up.
cc: @samueljlieber

@hojo-odoo hojo-odoo force-pushed the 16.0-inventory-scope-restructure-hojo branch 2 times, most recently from c84a812 to 958e238 Compare November 28, 2023 21:34
@samueljlieber samueljlieber requested a review from a team November 29, 2023 16:27
Copy link
Contributor

@samueljlieber samueljlieber left a comment

Choose a reason for hiding this comment

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

Hi @hojo-odoo! First I want to say awesome job with the restructuring of the inventory scope, I think you did a great job and I am looking forward to seeing this new structure moving forward!

I found a handful of items that could be improved/fixed within this pr:

  • Missing redirects for removed toctree files
  • Can remove unused images that were added
  • Can use :ref:s instead of :doc: links in some places to avoid going over 100 chars

Overall, all of your changes looked really great, so nice job 🙂

That being said, I will push up a second commit with all of my suggestions that you can squash/implement at your discretion.

Thank you for your continued hard work on this PR, once my suggestions are implemented I will approve this technical review.

Copy link
Contributor

@samueljlieber samueljlieber left a comment

Choose a reason for hiding this comment

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

Thank you @hojo-odoo, this PR looks good to me! @StraubCreative this is ready for final review 👍

@StraubCreative StraubCreative requested review from a team and jcs-odoo December 5, 2023 21:25
Copy link
Contributor

@xpl-odoo xpl-odoo left a comment

Choose a reason for hiding this comment

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

Hello @hojo-odoo, great job! 👏

Ideally, don't use the ref markup when you should use the doc markup, and always use relative paths. See the comments inside the PR for some examples 😃

@hojo-odoo hojo-odoo force-pushed the 16.0-inventory-scope-restructure-hojo branch 2 times, most recently from 31f65bf to da64d3d Compare December 7, 2023 18:37
Copy link
Contributor

@samueljlieber samueljlieber left a comment

Choose a reason for hiding this comment

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

Hi @hojo-odoo I caught just a couple more :ref: tags that need to be updated to :doc: tags, other than these 👇 everything else looks good to me! I am approving now, but please make these updates before moving forward. Thank you!

@hojo-odoo hojo-odoo force-pushed the 16.0-inventory-scope-restructure-hojo branch from da64d3d to 1926736 Compare December 7, 2023 19:33
@StraubCreative
Copy link
Contributor

LGTM, all checks pass 🚀

@robodoo r+

@fw-bot
Copy link
Collaborator

fw-bot commented Dec 12, 2023

@hojo-odoo @StraubCreative this pull request has forward-port PRs awaiting action (not merged or closed):

1 similar comment
@fw-bot
Copy link
Collaborator

fw-bot commented Dec 13, 2023

@hojo-odoo @StraubCreative this pull request has forward-port PRs awaiting action (not merged or closed):

StraubCreative pushed a commit that referenced this pull request Dec 13, 2023
closes #5700

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
robodoo pushed a commit that referenced this pull request Dec 13, 2023
closes #5700

closes #6878

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants