Adding CSS to new domain

[jukent]

Closes #1

[jukent]

Would be useful to add github actions and deployment previews

[jukent]

Adding extensions here, would like to refactor to not have duplicate code across repositories later.

[kmpaul]

I wouldn't use portal for the name of the directory containing the Sphinx site. And should this be a jupyter book, not a raw sphinx site?

[jukent]

I wouldn't use portal for the name of the directory containing the Sphinx site. And should this be a jupyter book, not a raw sphinx site?

Why should this be a Jupyterbook? The only page in this repository is the "index" generated from the cookbook_gallery_generator. I was confused for a while deciding to use the infrastructure from the portal or from the foundations book. The portal seemed like it would play with the gallery generator better (since that is how it worked before).

There were so many moving parts, I wouldn't be surprised if I missed anything.

[kmpaul]

Why is the site/_build directory being committed to this repo? That should be in the gitignore file.

[jukent]

Why is the site/_build directory being committed to this repo? That should be in the gitignore file.

Ahh I thought I missed the "portal" to "cookbooks" to "site" transition somewhere.

[kmpaul]

@jukent: The new Cookbook organization contains a fork of this repository. So, you don't have to move all of your work to that repo. You can just merge this PR into this repo as usual, and then we can merge new changes from this repo into the Cookbooks fork. Once this PR is merged, we can "detach" the Cookbooks fork from this repo and the two will be independent.

[kmpaul]

@jukent: Why did you close this?

[jukent]

@kmpaul Oops @jnmorley and I just started the process already -- and in doing so I deleted this repo and it closed the PR. It will be ready/. The new PR will be opened very soon.

[kmpaul]

We don't want to delete this repo!

[kmpaul]

So, you cannot delete this repo because the ProjectPythiaCookbooks/projectpythiacookbooks.github.io repo is a fork of this repo! Just keep working on your PR here, merge it, and we can pull the changes into the cookbooks repo.

[jukent]

So, you cannot delete this repo because the ProjectPythiaCookbooks/projectpythiacookbooks.github.io repo is a fork of this repo! Just keep working on your PR here, merge it, and we can pull the changes into the cookbooks repo.

I deleted my own fork of it (where the PR is coming from).

I made a new PR here ProjectPythia/cookbook-gallery#3

[kmpaul]

Well, we want a site for the Tutorials org, too. So, keeping this PR, merging it, and then pulling those changes into the Cookbooks repo would have killed 2 birds with 1 stone.

We'll have to merge from the Cookbooks repo back into this repo when ProjectPythia/cookbook-gallery#3 gets merged, then.

[jukent]

Sorry. I got frustrated that GitHub wouldn't let me have a fork of both the tutorials and cookbooks repositories since they are forked from each other. I cannot undo the deletion of my fork by making a new one (since I made one in the cookbooks repo) but we can still merge this PR as is.

[kmpaul]

If you are going to merge ProjectPythia/cookbook-gallery#3 in, then let me know. Once that is merged, I'll merge that into this repo and start working on the tutorials org site myself. You can keep working on the Cookbooks site.

[kmpaul]

That means we'll just have to close this PR.

[jukent]

Okay thanks I'll merge it now

[jukent]

Done!

[jukent]

I figured out the error with the teams -- they need to be added to each repository with write permission, not just created.