-
Notifications
You must be signed in to change notification settings - Fork 200
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
Documentation #148
Comments
With codeplex shutting down soon, should someone take a snapshot of the original documentation? |
@mhov Thanks for information! Yes, me should. I try to contact with team members. But seems that all members are inactive for a long time. Is it possible to download documentation if you are not a team member? |
Good news from CodePlex team:
|
Hi, am new in open source and was trying to get some projects on hand, was wondering if i could render any assistance in it? |
Hi, Also you can improve generated documentation (http://yaccconstructor.github.io/QuickGraph/reference/index.html). You can add some valuable comments in code for class and methods (especially if comments is empty now). |
I have a copy of the CodePlex wiki converted to Github flavored markdown if you want it. |
@briangabriel Could you share that somehow? I cannot seem to find the original documentation anywhere... |
I've migrated the wiki content from the archived CodePlex project. There's no way to send a PR against the wiki repo, so either you'll have to make me a contributor to this repo, or you'll have to manually pull in the commits from my custom "fork" of the wiki repo, here: https://github.com/eloekset/QuickGraph-Wiki/tree/feature/148-MigrateCodePlexWiki Since I'm not able to see my own changes hosted as GitHub Wiki, I've obviously not tested how the content works. Basically I've just renamed the files that contained spaces to use dashes instead, to make links work. At least that seems to be needed when previewing files in VSCode. |
@eloekset Thank you very much! |
For all. What do you think about "synchronization" with autogenerated documentation? For example, description of AdjacencyGraph from wiki can be moved to autogenerated page It may done documentation more unified. Also, I think that other pats can be moved to github.io page |
It may be useful to move (and create new) examples too (#177). |
I’ve updated all markdown files to use GitHub pages syntax for code blocks now. Still there are some things left to clean up after the port from CodePlex:
Since I’m not on a PC at the moment, I’ve got limited editing capabilities ref this tweet 😋 |
Hello colleagues, i've updated some parts of the wiki here, https://github.com/eosfor/Quickgraph.Wiki. Just did some cleanup, fixed markup and pics. |
@eosfor Thank you! Merged. |
We need a good documentation.
We have own site.
There is an original documentation.
What we should do.
The text was updated successfully, but these errors were encountered: