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

chore(get-started): formatting of terms and phrases #150

Conversation

aali309
Copy link
Contributor

@aali309 aali309 commented Nov 2, 2023

fixes: #120

@aali309 aali309 added the chore Refactor, rename, cleanup, etc. label Nov 2, 2023
@aali309
Copy link
Contributor Author

aali309 commented Nov 2, 2023

@andrewazores @ebaron please take a look at this and let me know. I checked some other community guides for documentation, this looks so different. i will try to look pattern-fly guide or something from Red Hat

@andrewazores
Copy link
Member

Which other guides did you look at for comparison?

In any case, this is the documentation for the upstream project, so while it would perhaps be nice to have a similar look and feel to other Red Hat-sponsored projects, I don't think it's a requirement. If we do want to go that way it would be a larger change and something to look at in the longer term.

@aali309
Copy link
Contributor Author

aali309 commented Nov 2, 2023

Which other guides did you look at for comparison?

In any case, this is the documentation for the upstream project, so while it would perhaps be nice to have a similar look and feel to other Red Hat-sponsored projects, I don't think it's a requirement. If we do want to go that way it would be a larger change and something to look at in the longer term.

I looked at OpenShift and GutHub. I agree it is a larger change. What do you think of the changes? Should I continue this way? I followed @tthvo comments on the issue

@andrewazores
Copy link
Member

Yes I think what you're doing here is a good improvement to the existing docs as they are. I don't see any particular need to change anything on a larger scale, certainly not in the timeframe for this upcoming 2.4 release.

If you'd like, for the goal of keeping the review loop shorter and easier, we can just retarget this PR from going into main to going into #141 or #148, and in this particular PR just work on updating and reviewing the get-started/index.md as you have done. Once that is merged then you can open a new PR again targeted at #141 / #148 to update the next document, like guides/index.md, then guides/_subsections/navigate-the-dashboard.md, etc.

@aali309 aali309 changed the base branch from main to 143-story-update-written-content-for-240 November 3, 2023 00:12
@andrewazores andrewazores changed the title chore(release): formatting of terms and phrases chore(get-started): formatting of terms and phrases Nov 3, 2023
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
get-started/index.md Outdated Show resolved Hide resolved
@andrewazores
Copy link
Member

@aali309 if you could please wrap up the last couple of review comments here, I'd like to get this merged so I can work on top of it and update the written content for the Agent without making your rebase super annoying

…ntFormating

Signed-off-by: Atif Ali <56743004+aali309@users.noreply.github.com>
@andrewazores andrewazores merged commit 72d6aed into cryostatio:143-story-update-written-content-for-240 Nov 9, 2023
2 checks passed
@aali309 aali309 deleted the consistentFormating branch November 9, 2023 18:45
andrewazores pushed a commit that referenced this pull request Nov 16, 2023
Signed-off-by: Atif Ali <56743004+aali309@users.noreply.github.com>
andrewazores added a commit that referenced this pull request Dec 11, 2023
* chore(get-started): update screenshots (#145)

* chore(get-started): extract Cryostat Agent version property, update (#146)

* chore(get-started): formatting of terms and phrases (#150)

Signed-off-by: Atif Ali <56743004+aali309@users.noreply.github.com>

* chore(guides): formatting of terms and phrases in guides-index.md (#152)

* chore(agent): update Cryostat Agent content (#155)

* chore(guides): update Automated Analysis guide (#158)

* chore(credentials): update guides around stored credentials (#159)

* chore(credentials): correct a formatting error (#160)

* chore(snapshot): update snapshot content (#161)

* chore(custom_target): update custom target content (#163)

* chore(doc): document using Smart Triggers (#169)

* using smart triggers

* using smart triggers completed

* consistency

* resolved issues

* resolved more issues

* chore(get-started): formatting of terms and phrases in guides/_subsections/navigate-the-dashboard.md (#153)

* formatting of terms and phrases

* commited to start use topology view

* custome target updated

* commited to start on event templates

* commited to start on event templates(edit template with JMC)

* commited to start view and download automated Analysis for a recording

* done (first commit)

* updated Add and Edit Recording Metadata Labels

* updated Add and Edit Recording Metadata Labels

* updated archive a recording section

* started updating automated analysis

* automated analysis needs updating

* custome target updated

* updated download-an-active-or-archived-recording.md

* updated Re-Upload a Recording to Archives

* updated screenshots to the right folders

* updated written content to mathc updated screenshots on automated analysis

* configure Graphical Notifications

* configure credentials storage updated

* more updates on store credentials and create an automated rule

* review changes before start topologyview

* reviewed use Topology view

* reviewed create a custom target

* reviewed using the cryostat agent

* reviewed start/stop a recording

* reviewed snapshot a recording

* reviewed archives and related docs

* reviewed event templates and related docs && removed format on clickable links

* reviewed view in grafana

* resolved some comments

* removed download the report in automated-analysis.md

* configure credentials storage reviewed

* create an automated rule updated

* add-and-edit-recording-metadata-labels.md updated

* store credentials reviewed

* upload and download automated rule reviewed

* fixup! Merge remote-tracking branch 'upstream/prepare-240-release' into 143-story-update-written-content-for-240

---------

Signed-off-by: Atif Ali <56743004+aali309@users.noreply.github.com>
Co-authored-by: Atif Ali <56743004+aali309@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Refactor, rename, cleanup, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Task] Consistent formatting of terms and phrases
2 participants