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

Documentation redundancy: WRENCH 101 / Guide #156

Closed
henricasanova opened this issue Apr 17, 2020 · 9 comments
Closed

Documentation redundancy: WRENCH 101 / Guide #156

henricasanova opened this issue Apr 17, 2020 · 9 comments
Assignees
Labels
Milestone

Comments

@henricasanova
Copy link
Contributor

After adding some words to the WRENCH Guide, there is quite a bit of redundancy between WRENCH 101 and the Guide. For some things one it more specific, for others the other is more specific. I am thinking that we should just put everything under 101....

henricasanova added a commit that referenced this issue Apr 17, 2020
Added words to the Guide about platform descriptions and simulation
output
@rafaelfsilva
Copy link
Member

@henricasanova, I agree with you, since we like making pedagogic modules, maybe we could split it into WRENCH 101, 102, 201, etc. What do you think?

@henricasanova
Copy link
Contributor Author

For now, I am thinking of all in 101 with links to "internal" documents with some of the more detailed "guide" information. In the process of doing that, I may create a 102. . Also, I am thinking of adding a few more examples to the examples directory. I'll take a first stab at all this, and we'll see what we think.

@rafaelfsilva
Copy link
Member

Sounds great to me!

@rafaelfsilva rafaelfsilva added this to the 1.6 milestone Apr 17, 2020
@henricasanova
Copy link
Contributor Author

I am having a small issue, and I am not sure how to resolve it. As Rafael and I discussed yesterday, we're removing the "user/devel/internal" "button" as now the documentation text (i.e., wrench-101, wrench-102) is simply always visible. It was confusing that clicking on the "button" would modify the content.The idea is now just to have a pull-down menu on the API top-level item that allows to select the level of documentation.

The issue I am having is this, taking wrench-102 as an example. In wrench-102.md I have something like wrench::SomeMethod. Conveniently, this generates a link to the API. But this link is based on the directory I am in. So, if I view the user documentation, then this link is not inserted if SomeMethod is not in the User API.

This all makes sense, but I am not sure how to resolve it.... perhaps it's a bit of a showstopper? Regardless, I'll continue writing content for now

@rafaelfsilva
Copy link
Member

You can keep working like that for now, and I can try to find some magic trick to automatically change the paths during compilation or something else :)

henricasanova added a commit that referenced this issue Apr 23, 2020
Pass on wrench-101.md
@henricasanova
Copy link
Contributor Author

I just finished my (super extensive!) pass on the documentation. It's all pushed to master, and ready to somebody to review. I didn't touch much the HTCondor documentation (as I never looked into that), so Rafael if you want to add/modify it, that's great).

@rafaelfsilva
Copy link
Member

I have completed a review on WRENCH 101 and 102 pages.

@henricasanova
Copy link
Contributor Author

ok. so perhaps time to close this issue? Or is there more for us to discuss?

@rafaelfsilva
Copy link
Member

I think it can be closed.

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

2 participants