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

Readme creation / cleanup update #165

Open
PrzemyslawKlys opened this issue Nov 26, 2023 · 2 comments
Open

Readme creation / cleanup update #165

PrzemyslawKlys opened this issue Nov 26, 2023 · 2 comments

Comments

@PrzemyslawKlys
Copy link

Is there a way to create README.MD like PlatyPS does?

image

I tried using Wiki, but I don't see any results. Also is it possible to clear any deleted commands from doc?

@StartAutomating
Copy link
Owner

@PrzemyslawKlys

For creating the README:

I normally do this by hand / with PipeScript's help (see almost any repo's README.ps.md). This allows me to hand-craft most of the content I want and templatize stuff like command tables and examples.

I haven't found a "perfect" default for this yet. I'm open to suggestions on a "good enough" default.

For deleting the help content that's no longer "correct"

This one is a trickier problem. The long story made short is that it's easy to clear a directory, and that would prevent manually editing docs (which would be bad). It's very hard to figure out that a file has become an orphan.

I'm open to suggestions here. Changes would have to be tracked in an additional file in order for us to know that "the file was generated by the last build, but not this build".

Hope this helps / Lemme know what you think

@SamErde
Copy link

SamErde commented Nov 7, 2024

@PrzemyslawKlys, I'm curious if this is relevant to your question. In my PSPrworkout module, I have a GitHub action that publishes MkDocs. I wanted to combine the PlatyPS-generated readme with my own content, so this action has a PowerShell scriptblock that combines two files to create a new readme.
https://github.com/SamErde/PSPreworkout/blob/cf68aa76afe1f2474295ac0e0cc93ecb6c354a1e/.github/workflows/Deploy%20MkDocs.yml#L36

It basically lets me use separate files for the header, content, and footer of the repository's readme. It's a bit hacky right now but could probably be polished into a proper script or action. What do you think?

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

No branches or pull requests

3 participants