search

operate-first / operate-first.github.io-old

GNU General Public License v3.0
18 stars 42 forks source link

Create Operate-First Gatsby Theme #145

Closed anishasthana closed 2 years ago

anishasthana commented 3 years ago

Since we are aiming to have consistent-looking docs across operate-first, internal data hub, and upstream ODH, we should publish a proper theme on gatsby that can be installed for any document sites. This way we'd only have to make changes to the theme in one location and have them trickle down to all the deployments. CC @tumido

tumido commented 3 years ago

Something like https://github.com/jschuler/gatsby-theme-patternfly would do, right? Just updated to Paternfly 4 + our custom components.

anishasthana commented 3 years ago

Yeah I think that'd be perfect.

tumido commented 3 years ago

https://github.com/jschuler/gatsby-theme-patternfly/issues/15

tumido commented 3 years ago

More questions asked https://github.com/patternfly/patternfly-org/issues/2312

anishasthana commented 3 years ago

@oindrillac fyi

durandom commented 3 years ago

@anishasthana do you have a pointer where you're doing your internal deployment? For starters I would work with a fork/rebase relationship of the repos and extract all stuff into configurations

@cfchase should decide if he wants a theme for all his MODH work

anishasthana commented 3 years ago

It's on internal gitlab unfortunately: as of now I had to do a pretty ugly rip and tear. https://gitlab.cee.redhat.com/data-hub/dh-user-docs

tumido commented 3 years ago

So, Patternfly community finally replied. They don't maintain any of it and don't plan to support Gatsby. We would need to update it ourselves and create yet another theme/package if we want to support this. Leaving it up and open - I think this would be a nice Internship project.

/label hacktoberfest

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

schwesig commented 2 years ago

/remove-lifecycle stale /kind website /priority important-longterm

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/operate-first.github.io/issues/145#issuecomment-1085947419): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.