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

Revamp documentation for updated Unix commands in Polykey CLI #95

Open
9 tasks
CryptoTotalWar opened this issue Jul 15, 2024 · 8 comments
Open
9 tasks
Labels
documentation Improvements or additions to documentation procedure Action that must be executed

Comments

@CryptoTotalWar
Copy link
Contributor

CryptoTotalWar commented Jul 15, 2024

Description

This ticket is dedicated to updating the Polykey documentation to incorporate the newly integrated Unix-style commands within the pk secrets subsystem. The goal is to ensure that all instructional materials are up-to-date, reflecting the new command functionalities to enhance clarity and usability for end users.

Tasks and Notes

  • Determine Release Strategy:
    • Decide if the CLI updates will be released all at once or in phases.
    • Plan to start detailing and implementing documentation updates 2 weeks prior to the first release.
  • ** Implementation Task Tracking:**:
    • Create and maintain a checklist for updating various sections of the documentation to align with the CLI changes.
  • Set Up Test Environment (Optional): Establish a test environment that mirrors the new CLI version to allow for hands-on interaction and verification of documentation accuracy.

Placeholder for Detailed Documentation Updates

Overview of Documentation Areas Needing Updates:

  • Docs Home Page
  • Getting Started Sections
  • Reference Sections
  • How-To-Guides
  • Blog Posts
@CryptoTotalWar CryptoTotalWar added documentation Improvements or additions to documentation procedure Action that must be executed labels Jul 15, 2024
@CryptoTotalWar CryptoTotalWar self-assigned this Jul 15, 2024
Copy link

linear bot commented Jul 15, 2024

Copy link
Member

What do we do with this issue? It looks underspecced and abandoned.

@tegefaulkes
Copy link
Contributor

Not sure. It still needs to be done to reflect the new unix style commands. But I'm unsure what the priority is for the documentation now.

The spec here will need to be rewritten and the issue added to the unix style commands project.

@aryanjassal
Copy link
Member

The spec here will need to be rewritten and the issue added to the unix style commands project.

This issue is already a part of the unix style commands project. That's how I discovered the existence of this issue in the first place.

This issue probably isn't high up in the priorities, so the documentation update will probably come near the end of the project.

@aryanjassal aryanjassal changed the title Revamp Documentation for Updated Unix Commands in Polykey CLI Revamp documentation for updated Unix commands in Polykey CLI Dec 16, 2024
Copy link
Member

Should I just write up a quick paragraph or two of documentation whenever I add a new command? I tried to get my friend to use polykey, but he was struggling a bit because the documentation was out of date and I was the only one he could ask for documentation.

I might not be able to write up the final documentation, but at least the documentation would be usable for an end-user to try out the product.

@tegefaulkes
Copy link
Contributor

Yeah, it would be great if you could write some updates.

Copy link
Member

#112

@aryanjassal aryanjassal self-assigned this Dec 17, 2024
Copy link
Member

Providing an example of using Polykey in a workflow would be pretty beneficial. We can probably make a separate page for "Using Polykey in your project", which could guide users through a setup similar to what we have with secrets env in nix shells. Later, when we have figured out how to handle this inside the CI, we can add a page for CI too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation procedure Action that must be executed
Development

No branches or pull requests

3 participants