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

Add info about contributing to README #23

Open
bryanwweber opened this issue Jul 4, 2018 · 5 comments
Open

Add info about contributing to README #23

bryanwweber opened this issue Jul 4, 2018 · 5 comments
Labels
documentation-update An update is needed to the documentation

Comments

@bryanwweber
Copy link
Member

Add info about how to add blog posts and new pages to the README, and possibly also a CONTRIBUTING file

@ischoegl
Copy link
Member

ischoegl commented Aug 8, 2019

That addition would be quite helpful. Also, are there portions that are generated by sphinx, doxygen, etc?

@bryanwweber
Copy link
Member Author

Everything in this repository is generated by Nikola. We upload documentation of every build of the master branch of Cantera/cantera into a folder on the website, that documentation is built by Sphinx and managed by the Cantera/cantera Travis builds.

@ischoegl
Copy link
Member

ischoegl commented Aug 8, 2019

Everything in this repository is generated by Nikola.

... except for rst files in pages/science, correct? I.e. those are still edited manually.

@bryanwweber
Copy link
Member Author

Hmm, yes I was not very precise. Technically, Nikola doesn't generate anything that is checked into this repo. Nikola processes all of the reST and Markdown files (which are checked into the repo) into HTML, and uses some custom plugins to process the examples. All of the reST and Markdown files must be edited to change the content.

@ischoegl
Copy link
Member

ischoegl commented Aug 9, 2019

Following up on my comment from the other thread here: assuming that it is possible to pull reST files (specifically science docs) from another repo (e.g. cantera/docs), then you should be able to have two versions as currently being discussed? If it is indeed possible to have Nikola pull that content in from a dedicated reST repo, it would then be possible to replicate the branch structure from the code repo (with branch 2.4 and master for stable cantera and cantera-devel). Hooking the two versions into the website shouldn't be an issue. I hope this cleared up my earlier comment.

From the perspective of documentation, it would be imho much simpler to write something with a single audience, rather than having to always think about who's using what version. From the perspective of readers, it will hopefully also avoid some confusion. I will not comment on the other thread as I need to get out of this conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation-update An update is needed to the documentation
Projects
None yet
Development

No branches or pull requests

2 participants