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

Reorganize documentation #156

Open
cbolisetti opened this issue Aug 22, 2018 · 6 comments
Open

Reorganize documentation #156

cbolisetti opened this issue Aug 22, 2018 · 6 comments
Assignees

Comments

@cbolisetti
Copy link
Contributor

Currently, when we create a new material (with multiple classes, usually kernel, material classes and an action) we have the documentation for this material spread out in the documentation for all of these classes. We need a better organization.

My idea is as follows. For each new material (or other entity which involves creating multiple classes), we will create two new documentation files apart from the individual documentation for the classes. These two files are for theory (background and the math of the material/other entity) and user (how to use model this material, i.e., what classes to use or what actions to use.) We can then index all the theory doc files and the user doc files into the main theory and user manuals. This way, the theory and user manuals will be updated automatically every time we create a new material.

@cbolisetti cbolisetti self-assigned this Aug 22, 2018
@aeslaughter
Copy link
Contributor

Looking at the current doc structure, I would move the "user" and "theory" folders to the top-level of doc/content. Also, "interfaces" should be moved to the "source" directory. Just my two cents.

May I suggest adding instructions for writing documentation in MASTODON, where this wording is explained and linked against some examples.

@cbolisetti
Copy link
Contributor Author

@aeslaughter, yes both sound good. I will do that.

@sveerara @hoffwm @colejust If you have any suggestions about how the documentation can be improved, please let me know.

@sveerara
Copy link
Contributor

@cbolisetti, i like both your suggestions and Andrew's suggestions on editing the documentation.

Should a test be added to check whether the theory and user documentation file exists for each .C file?

@cbolisetti
Copy link
Contributor Author

@sveerara, yes, I think a test like that would be very helpful. And perhaps generate user and theory stub files with a template too? @aeslaughter how difficult would it be to do this?

@cbolisetti
Copy link
Contributor Author

@sveerara, actually I don't think that would work since we need theory and user manual files for each material or BC, etc., and not each class. Should we check for it manually, if there's no other way?

@sveerara
Copy link
Contributor

Oh, I din't think about that. Yes, I guess we can just check manually.

cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 5, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 5, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 5, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 5, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 5, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 10, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 10, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 10, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Sep 10, 2018
cbolisetti added a commit to cbolisetti/mastodon that referenced this issue Aug 8, 2019
crswong888 pushed a commit to crswong888/mastodon that referenced this issue Aug 20, 2019
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Mar 11, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Mar 12, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Mar 12, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Mar 12, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Mar 12, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Mar 12, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Apr 8, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Apr 8, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Apr 8, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue May 11, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue May 11, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Oct 22, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Oct 22, 2020
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Oct 31, 2020
This is no longer needed because of changes to MOOSE

(refs idaholab#156)
aeslaughter added a commit to aeslaughter/mastodon that referenced this issue Dec 24, 2020
aeslaughter added a commit that referenced this issue Oct 6, 2021
cticenhour added a commit that referenced this issue Jan 12, 2023
cticenhour pushed a commit to cticenhour/mastodon that referenced this issue Jan 18, 2023
cticenhour added a commit to cticenhour/mastodon that referenced this issue Jan 18, 2023
cticenhour added a commit that referenced this issue Jan 18, 2023
This was referenced Jul 30, 2024
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