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

Cleanup porting guide #684

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Conversation

kprosise
Copy link
Contributor

@kprosise kprosise commented Feb 5, 2024

Applied style guidelines where possible. Moved the introduction page to the index/ToC page, so as to provide an overview for the section up front.

Checked rendered output in browser, focusing on visual elements. No issues spotted.

This commit addresses FFTK-2995

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

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

@angolini other than merging the introduction with the top level/ToC page, I tried to keep the changes minimal, and most seemed to be related to breaking up sentences. Let me know if I should revert anything, or if you have any other recommended changes.

Applied style guidelines where possible. Moved the introduction page to
the index/ToC page, so as to provide an overview for the section up
front.

Checked rendered output in browser, focusing on visual elements. No
issues spotted.

This commit addresses FFTK-2995

Signed-off-by: Katrina Prosise <[email protected]>
@doanac
Copy link
Member

doanac commented Feb 5, 2024

Copy link
Collaborator

@angolini angolini left a comment

Choose a reason for hiding this comment

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

I don't see anything to comment. LGTM

Introduction
------------

This section provides guidelines and suggestions on how to add support for a machine not already supported by FoundriesFactory.
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we keep this structure, we need to find better names for the different levels. The Porting Guide is not a section. Would it be a document? A "part"? A chapter?

I mean, of course it's also a section, but I'm sure we can decide a better cluster name

@kprosise kprosise merged commit 8db8c70 into foundriesio:main Feb 6, 2024
2 of 3 checks passed
@kprosise kprosise deleted the cleanup-porting-guide branch March 12, 2024 12:29
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