Closed pcschreiber1 closed 6 months ago
* To me it still remains open if and how we brand this, so I would stay away from colours and logos now.
Agreed. I think that this goes with the discussion on UX etc. I would personally be hesitant to go beyond the "vanilla" template of mkdocs within the MVP. But obviously this is the opinion of a techy with little taste.
* Stick with a simple homepage for now, since custom homepages of the kind of [mkdocs material](https://squidfunk.github.io/mkdocs-material/) and [up42](https://sdk.up42.com/) would require too much effort & time.
I am honestly not sure what you mean with this question. Is the mkdocs not fulfilling criterion i) and ii) ? You want to drop for mkdocs even for the MVP or in a later iteration ?
* Add link to GitHub repo
Sounds good to me.
* I am honestly not sure what you mean with this question. Is the mkdocs not fulfilling criterion i) and ii) ? You want to drop for mkdocs even for the MVP or in a later iteration ?
No, no - both are examples of what is possible within mkdocs. But it's hard to do, so like you said, I would try to stay within the "Vanilla" mkdocs.
We need to draft a first version of the design website that is i) accessible and ii) attractive enough to be shared with partners and colleagues.
I would suggest that somebody just gives it a shot and we take it from there. @fretchen, I can take this up if you'd prefer not to.
Proposal:
What do you think?