Skip to content
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

Initial User Guide Reorg and Introduction of Customer Life Cycles #685

Merged
merged 3 commits into from
Feb 20, 2024

Conversation

vanmaegima
Copy link
Member

@vanmaegima vanmaegima commented Feb 5, 2024

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.

Readiness and adding reviewers as appropriate is required.

All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.

Readiness

  • Merge (pending reviews)
  • Merge after date or event
  • Draft

Overview

This brings a User Guide reorganization based on the customer journey so steps can be approached in a understandable way.

This also brings the Customer Life Cycle view of the docs, which covers a doc view based on journey/personas.

Checklist

  • Run spelling and grammar check, preferably with linter.
  • Avoid changing any header associated with a link/reference.
  • Step through instructions (or ask someone to do so).
  • Review for wordiness
  • Match tone and style of page/section.
  • Run make linkcheck.
  • View HTML in a browser to check rendering.
  • Use semantic newlines.
  • follow best practices for commits.
    • Descriptive title written in the imperative.
    • Include brief overview of QA steps taken.
    • Mention any related issues numbers.
    • End message with sign off/DCO line (-s, --signoff).
    • Sign commit with your gpg key (-S, --gpg-sign).
    • Squash commits if needed.
  • Request PR review by a technical writer and at least one peer.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Signed-off-by: Vanessa Maegima <vanessa.maegima@foundries.io>
@vanmaegima vanmaegima changed the title Customer lifecycle Initial User Guide Reorg and Introduction of Customer Life Cycles Feb 5, 2024
@doanac
Copy link
Member

doanac commented Feb 5, 2024

@vanmaegima
Copy link
Member Author

@mike-scott @kprosise @angolini @caiotpereira Draft view so you can check the compiled page.
I didn't like the initial propose, which made the User Guide view huge:
Screenshot from 2024-02-05 11-04-09
So I'm proposing this new LifeCycle view which will also include personas. I'm still not very happy about it so please provide your feedback.
This is draft only as we are missing several pages (explaining the life cycle, personas, production, etc). If the team agrees this is the best path to go, then I can work on those pages.

@vanmaegima vanmaegima requested review from kprosise, angolini and a team February 5, 2024 16:12
@angolini
Copy link
Collaborator

angolini commented Feb 5, 2024

From the previous discussion, I understood we would replace the part "User Guide" with another part; from the PR, it would be the "Life Cycle / Customer Journey / Good Name Here".

@kprosise, do you know if there is a way we can display levels 1 and 2 on the sidebar?

@angolini
Copy link
Collaborator

angolini commented Feb 5, 2024

Overall, I like the change in the order. But I still don't like the sidebar

@vanmaegima
Copy link
Member Author

@angolini I agree with displaying multiple levels on the side bar, I played with it for a bit but couldn't achieve anything.

@angolini
Copy link
Collaborator

angolini commented Feb 5, 2024

@angolini I agree with displaying multiple levels on the side bar, I played with it for a bit but couldn't achieve anything.

In the past, I have also tried and could not find a way.

@vanmaegima
Copy link
Member Author

I did a sync with Mike on this and from this I will propose a few more changes to this, the biggest one being dropping the new life cycle section. We will cover personas at the top of each section.
I will rework this tomorrow and propose the changes in a few pages so we can check.

@kprosise
Copy link
Contributor

kprosise commented Feb 6, 2024

@angolini @vanmaegima let me look into the side bar levels thing. It should be possible, will likely just require modding the theme a bit. Let me spend a little time today to see what I can come up with.

@vanmaegima
Copy link
Member Author

vanmaegima commented Feb 6, 2024

Updated docs with suggestions from @mike-scott , PTAL.
See pages Factory & Account Management and Custom CI for an example on the suggestion to handle Personas.

@kprosise
Copy link
Contributor

kprosise commented Feb 6, 2024

Re: side bar levels, it will unsurprisingly require a deeper dive into what is going on. All my attempts today at changing anything related to the theme produce nothing. I will spend a bit more time looking into it out of curiosity before moving on for the time being.

@doanac
Copy link
Member

doanac commented Feb 6, 2024

Copy link
Contributor

@kprosise kprosise left a comment

Choose a reason for hiding this comment

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

I am liking this reorganization so far!

@@ -62,7 +75,6 @@ OE/Yocto Project, the Linux microPlatform™ and Docker®.
reference-manual/index
reference-manual/docker/docker
reference-manual/boards/boards
reference-manual/qemu/qemu
Copy link
Contributor

Choose a reason for hiding this comment

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

This can be done after the merge, but for all pages moved to a different section, we should likely add a redirect in source/conf.py

Copy link
Member Author

Choose a reason for hiding this comment

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

@kprosise I'm reworking this PR, can I get an example on what do you mean with this comment? I see the redirects in conf.py but it's not clear for me what it means.

Copy link
Contributor

Choose a reason for hiding this comment

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

Just so that anyone going to latest/reference-manual/qemu/qemu.html and the other pages don't receive a no-such-page error, as the pages will  now be under latest/user-guide/qemu/* , but it's not too important at the moment.

Signed-off-by: Vanessa Maegima <vanessa.maegima@foundries.io>
This aims to improve the top to bottom flow of our documentation.

Signed-off-by: Vanessa Maegima <vanessa.maegima@foundries.io>
@vanmaegima
Copy link
Member Author

@kprosise I reduced the scope on this PR (removed personas and new pages that I'll cover on the next PR per discussion with Mike). Now it only covers:

  • reorganization of UG
  • QEMU section change to UG (with redirect - can you please check if I did it right?)
  • duplication of RM pages in UG for better user experience (need UG specific pages in the future)
    Let me know what you think and what it needs to get it merged.

@doanac
Copy link
Member

doanac commented Feb 20, 2024

@vanmaegima vanmaegima marked this pull request as ready for review February 20, 2024 12:00
@kprosise
Copy link
Contributor

Looks good to me! We can do future tweaks if need be, but I think this is a good step towards the reorganization goal! The redirect works as intended. :)

@vanmaegima
Copy link
Member Author

@kprosise We can merge this whenever you're ready then! I'll send another one after this is merged.

@kprosise kprosise merged commit 340d10c into foundriesio:main Feb 20, 2024
2 of 3 checks passed
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.

4 participants