Hi @pritkc, thank you for creating the Issue and outlining the proposed structure.

I agree, it would be better to move to a different model. I like libCEED's organization.

Just one minor comment. Perhaps I would remove the "manuals" subdirectory, as all those Markdown files there, including guides, will constitute the main User Manual anyways (eventually we won't have the scattered PDF files anymore. Their source will be included in the User Manual content).

Any objections/comments on the proposed structure?

cc: @jbrzensk

I'm a little confused. Outside of the documents folder, isn't the proposed structure the current folder structure?

I like the doc folder suggestions.

I'm a little confused. Outside of the documents folder, isn't the proposed structure the current folder structure?

I like the doc folder suggestions.

Hi @jbrzensk,

You're absolutely right. The main updates are in the documentation, where I've added detailed comments. The bullet points above outline the overall blueprint for the final outcome.

Okay. Sounds good. @pritkc you can proceed with the proposed outlined docs structure (I would just remove manuals).

Please create a PR when ready with the new file organization and, in the PR description, use verbiage that will link/pair it to this Issue, such as

Will close #16

So that GH automatically associates the PR to this Issue. Thanks!

I've posted a branch here: https://github.com/csrc-sdsu/mole/tree/folder-restructure.
I still need to update the affected paths, which I’ll handle in a PR once the proposed structure receives preliminary approval.

Hi @pritkc , thank you for your work.

It looks good for me now. Eventually, as discussed, we will remove the "manuals" subdirectory, as those PDF files will be embedded in the documentation/User Manual source anyways.
You can go ahead. Thank you.