Provide firebase accounts for subproject docs about k8s.io HOT 9 CLOSED

See this thread for some more details until we get it written up properly: https://kubernetes.slack.com/archives/C1J0BPD2M/p1550730421025400

I've been working to solve subproject docs, we have a netlify experiment here: https://kind.sigs.k8s.io/

I think we can do this repeatably at scale and at no additional cost to the main website, which already uses it.

In particular nearly all details of netlify can be managed via a config file in the repo, and the cost for paid netlify as we use it is just based on the number of team-members.

For DNS verification reasons these have to be the same team anyhow (unless every site also gets a domain), so we can have an overall Netlify team (which I'm volunteering to help with) do initial setup for each site and then do ongoing site configuration via the netlify.toml in each repo.

Doing this means each site doesn't cost additional $, and we're unlikely to move the main https://kubernetes.io site off of it anytime soon.

Aligning with SIG Docs on the stack (netlify + hugo) is additionally helpful for shared expertise, though any static site generator can be used.

I am syncing back with @zacharysarah about this next week when they're back from vacation.

from k8s.io.

thanks for logging this @justinsb !

from k8s.io.

/cc

from k8s.io.

Justin and @dims discussed this on the #k8s-wg-infra call toady.
@idvoretskyi recommended the request come from you or @spiffxp

from k8s.io.

Before submitting, can someone please update this issue with more details on the purpose of using Firebase?

Specifically, in Firebase vs Netlify comparison.

from k8s.io.

thanks @idvoretskyi
^ @davidewatson could you please comment.

from k8s.io.

@davidewatson please write up what we need and why, and ping me back?

from k8s.io.

After talking to @BenTheElder I learned that kind and kubebuilder recently switched to using netlify so I don't think there is any reason for us to use firebase anymore. Thanks for everyone's help on this.

/close

from k8s.io.

@davidewatson: Closing this issue.

from k8s.io.