#11 As we migrate quick docs from the draft section, how do we redirect to the production ones
Closed: complete 2 years ago by bcotton. Opened 6 years ago by mattdm.

We need to figure out the architecture here, both for the initial work and for when we move quick docs out of the "beta" area.

I'm assuming that in the end state, we won't publish documents that aren't ready for the public — they'll be done as PRs and built against a non-indexed PR-demo site.

So maybe the thing to do that's least effort is to just hurry up and get the docs we do have out of the beta repo.


I am very +1 to PRs effective post-FAD

We need some way for "pending" content to be visible to potential contributors — the build-on-PR step.

We need some way for "pending" content to be visible to potential contributors — the build-on-PR step.

@bstinson and I discussed this as a potential benefit of CI if we can get a platform and triggers and ...

Metadata Update from @jflory7:
- Issue tagged with: needs info, new change

5 years ago

@mattdm @bex @pbokoc Is this ticket sufficiently handled by the redirect macro that exists on the wiki? Is that macro documented anywhere in Fedora Docs-writing docs?

This might be a duplicate of #69.

Metadata Update from @pbokoc:
- Issue assigned to pbokoc

5 years ago

Hmmm. We don't have a draft section for quick-docs, we just don't publish any unconverted ones, we only keep them in the repo, so redirects aren't necessary.

Redirects for old Wiki pages are a different matter; I'll have to check those, I suspect not all converted wiki pages are redirecting to quick-docs.

Metadata Update from @bcotton:
- Issue close_status updated to: complete
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata