@dhblum this addresses your first point in https://github.com/ibpsa/project1-boptest/pull/606#pullrequestreview-1846125296. For the new section in the design guide, I'm doubting whether to implement it in this pull request or in the main one. If I implement it in this one then the main will have to pull the changes later on from the gh-pages-custom branch. This stems from having part of the documentation in main (only docs-design) and the rest in both main and gh-pages-custom, which I find a bit confusing right now. I suggest to unify both branches since it's not needed to keep a separate branch for gh-pages. We can always edit the web through regular pull requests to master. What do you think?
@dhblum this addresses your first point in https://github.com/ibpsa/project1-boptest/pull/606#pullrequestreview-1846125296. For the new section in the design guide, I'm doubting whether to implement it in this pull request or in the main one. If I implement it in this one then the main will have to pull the changes later on from the
gh-pages-custombranch. This stems from having part of the documentation inmain(onlydocs-design) and the rest in bothmainandgh-pages-custom, which I find a bit confusing right now. I suggest to unify both branches since it's not needed to keep a separate branch for gh-pages. We can always edit the web through regular pull requests tomaster. What do you think?