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

Start populating the github wiki #32

Closed
mateor opened this issue Jan 5, 2017 · 1 comment
Closed

Start populating the github wiki #32

mateor opened this issue Jan 5, 2017 · 1 comment
Labels

Comments

@mateor
Copy link
Contributor

mateor commented Jan 5, 2017

We have some internal documentation that I can migrate to the wiki - and we have had multiple consumers write up their experiences consuming plugins.

I think my favorite answer is to just add .md files in the source. I know it is a little non-standard but the contributor list is so small that I don't have much faith in being able to keep a separate wiki from drifting.

The short term answer is to take the text of issues #27,#28, #29, #30 and somehow surfacing them on the Fsq.io wiki tab.

@mateor mateor added the wontfix label Feb 21, 2017
@mateor
Copy link
Contributor Author

mateor commented Feb 21, 2017

The new model is to add .md pages at target level. We accept pull requests for documentation, with the preference being to place the docs as close to the code as possible.

So that means that we are not planning on integrating the Github wiki, at least not as a separate entity.

@mateor mateor closed this as completed Feb 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant