Skip to content

Port Website to Docsy Go module #5496

Open

Description

@asmacdo

Operator Framework sites are built with Hugo and the Docsy theme, which was previously versioned as a git submodule. We had to go pretty far outside of the accepted best practices to get our custom theme, and it has prevented us from migrating to newer versions of docsy.

Docsy is now available as a go module plugin to hugo instead, which should be significantly easier to upgrade.

Original discussion: docsy/docsy#535

Porting to module docs:

We will likely run into some trouble here, since we did so much beyond-best-practice stuff to override our custom theme. If we do, the best place ask questions here https://github.com/google/docsy/discussions/

Activity

  1. asmacdo commented on Jan 13, 2022

    @asmacdo
    MemberAuthor

    The part of this to watch for is whether we can cleanly override the docsy theme. If that part does not go smoothly, this could be a significant amount of front-end work.

  2. deining commented on Jan 18, 2022

    @deining

    The author that ported docsy theme to a module here 😄.
    I might be able to help you out in the transition of your documenation to dosy hugo module.
    Having a look at your website folder, I realized, that it's content is not self-contained yet. I have no idea what revision/commit of the docsy theme you are using. Are you able to add the docsy theme as a submodule, at the revision that your production site uses right now? Once I'm able to clone your site and run it locally, I will try to add the option to convert/use it as module. Your site can still use submodules, I should be able to bring it into a state where you can switch back and forth between module and submodule quite easily.
    I was curious and had a first quick glance and I immediately realized that your site/repo has to be reworked on several places to make it compatible with modules. So don't be deceived: while hugo modules are great, they are by no means a magic wand that will upgrade your site to the latest version without manual rework.

  3. added this to the Backlog milestone on Jan 24, 2022
  4. openshift-bot commented on Apr 25, 2022

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

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

    /lifecycle stale

  5. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 25, 2022
  6. asmacdo commented on Apr 26, 2022

    @asmacdo
    MemberAuthor

    /lifecycle frozen

  7. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2022
  8. added
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on May 18, 2022
  9. removed
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    on Jun 8, 2022
  10. added
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    on Jun 29, 2022
  11. openshift-bot commented on Sep 28, 2022

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

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

    /lifecycle stale

  12. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 28, 2022
  13. jberkhahn commented on Oct 12, 2022

    @jberkhahn
    Contributor

    /lifecycle-frozen

  14. removed
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    on Oct 12, 2022
  15. jberkhahn commented on Oct 12, 2022

    @jberkhahn
    Contributor

    /lifecycle frozen

  16. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.needs discussionpriority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions