A Proof of Concept (PoC) plan for new content proposal

I’m just pondering my work plan for the upcoming week and wondering, how to proceed exactly with the content work here.

I can clone the Installation Guide repo, but I can’t work in the stg branch because it would change the current stg pages, what we don’t want. I could create another branch, but I wouldn’t be able to preview anywhere but locally. And in the long run it would be a mislabeled repo because it would no longer be an installation guide, but an Anaconda Reference Manual.

And unlike yesterday, I now think we should make the proposed changes in stg as soon as possible. Only in this way we will get a realistic preview. And the changes are not so big that everything would be turned upside down. We make changes of this kind practically on a regular basis.

And especially with regard to Outreachy applicants: they need as realistic a picture as possible of what we want in the future.

Where can we discuss the course of action further?