Skip to content

Migrate content from v5 "Queries, Search And Indexing" #1730

Open

Activity

  1. moved this from New to Todo in Plone Documentationon Oct 2, 2024
  2. added this to the Plone 6.1 milestone on Nov 24, 2024
  3. Manas-Kenge commented on Mar 1, 2025

    @Manas-Kenge
    Contributor

    Do the Plone 5 docs just need to be copied into the Plone 6 docs, or do they need updates for the new version?

  4. stevepiercy commented on Mar 1, 2025

    @stevepiercy
    MemberAuthor

    They need a content expert to review their accuracy for Plone 6. That could mean overhauling, updating, or copying them. That's the situation for all the Plone 5 docs that have not yet been migrated to Plone 6.

  5. boss6825 commented on Jan 28, 2026

    @boss6825
    Member

    @stevepiercy Can I do this by first reviewing and validating the existing Plone 5 docs, and then creating updated versions for Plone 6 based on them...
    also, is there a central place where I can check the major changes from Plone 5 to 6 (for example, release notes or migration guides)?

  6. stevepiercy commented on Jan 29, 2026

    @stevepiercy
    MemberAuthor

    @boss6825 in addition to the resources in the issue's description, you can mine https://6.docs.plone.org/backend/upgrading/ for relevant changes.

    I'd suggest working on only a section of a page at a time, especially if it's long and complicated. That will help it get reviewed faster, too. I'd be happy with small incremental baby steps, as that would be better than the current situation. Thank you!

  7. boss6825 commented on Jan 29, 2026

    @boss6825
    Member

    yeah its quite long as it involves indexing , catalogs , Querystring, security and Language, and much more.
    I think i should split it into 2-3 PRs as it is getting quite long....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions