Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update publishing docs: add new images and update starting pattern guide #456

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zihanKuang
Copy link
Contributor

This PR addresses updates to the Publishing and Managing Designs documentation

Changes Introduced

  • Updated Documentation:

    • Enhanced explanation of the publishing workflow.
    • Added details on design state lifecycle and role-based permission controls.
    • Clarified FAQ section regarding modifying published designs, unpublishing, and resubmission of denied designs.
  • Added New Images:

    • Publishing-flow.svg (State lifecycle visualization)
    • approval-queue.png (Approval workflow UI)
    • designs-select-design.png (Design selection UI)
    • designs-select-sidebar.png (Sidebar selection UI)
    • publish-form.png (Publishing form UI)
  • Removed Old Images:

    • 2024-04-14_12-40.png
    • 2024-04-14_12-44.png
      (These two images were removed because their content has been replaced with new, updated images. Other cloned images are still being used in different parts of the documentation, so only these two were deleted.)
  • Code Changes:

    • Modified layouts/_default/content.html to explicitly define dark theme by adding data-bs-theme="dark" to .td-content div.
    • Minor text updates and structural improvements in content/en/kanvas/getting-started/starting-pattern.md.

Notes for Reviewers

  • The documentation now aligns better with the Meshery UI updates.

  • Please review the state transitions and permissions section for accuracy.

  • Ensure the new images are correctly linked and displayed in the rendered documentation.

  • Yes, I signed my commits.

Copy link

netlify bot commented Mar 13, 2025

Deploy Preview for bejewelled-pegasus-b0ce81 ready!

Name Link
🔨 Latest commit 35d2e4a
🔍 Latest deploy log https://app.netlify.com/sites/bejewelled-pegasus-b0ce81/deploys/67d296868de2ec00086d5f17
😎 Deploy Preview https://deploy-preview-456--bejewelled-pegasus-b0ce81.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@zihanKuang zihanKuang requested a review from vishalvivekm March 14, 2025 13:52
@fitzergerald
Copy link

@leecalcote
Copy link
Member

@sangramrath had questions on this topic in the past, like "Can a design be edited after it has been published?"

@leecalcote
Copy link
Member

Modified layouts/_default/content.html to explicitly define dark theme by adding data-bs-theme="dark" to .td-content div.
Good. I wonder what the effect of that is.

Is this where we should expect to see the new Publishing to Catalog doc? https://deploy-preview-454--bejewelled-pegasus-b0ce81.netlify.app/kanvas/tutorials/publishing-to-catalog/

Copy link
Member

@leecalcote leecalcote Mar 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will you consider relocating this page. Publishing of a design that a user has created is not considered a starter task. There is a placeholder under "tutorials" on this topic, but that is not the best location considering the content of this doc.

When we have an outline in a collaborative document, we can refine structure.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good. In the future, let's avoid nondescript examples like "publish test", but instead give the user concrete examples with populate fields, so that the concept is less abstract and more easily digested.


![Publishing Flow](/kanvas/getting-started/images/Publishing-flow.svg)

#### State Transitions Overview
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"State Transition" is good phrasing for contributors, but not so much for users.

"Phases of Publishing Process" or something similar might help user comprehension.

- Withdrawn designs require re-submission as new entries.
- Published designs are immutable.

### 3. Permission Controls
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### 3. Permission Controls
### 3. Publishing Permissions


### 3. Permission Controls

| **Operation** | **Creator** | **Organization Admin** | **Provider Admin** | **Regular User** | **Guest** |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| **Operation** | **Creator** | **Organization Admin** | **Provider Admin** | **Regular User** | **Guest** |
| **Operation** | **Owner** | **Organization Admin** | **Provider Admin** | **Regular User** | **Guest** |

Change the column order to go from least privileged to most privileged. Use only roles that are published in https://docs.layer5.io/cloud/security/roles/. Potentially, include a tip that points to these roles and the default permissions reference - https://docs.layer5.io/cloud/reference/default-permissions/

| **Operation** | **Creator** | **Organization Admin** | **Provider Admin** | **Regular User** | **Guest** |
|---------------------|--------------------|------------------------|--------------------|------------------|-------------------------|
| Edit Pending Design | ✔ | ✔ | ✔ | ✔ | ✔ |
| Unpublish | ✘ | ✔ | ✔ | ✘ | ✘ |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please confirm that each of these operations corresponds to a permission key (sourced from the Meshery Cloud API Endpoints spreadsheet)

|---------------------|--------------------|------------------------|--------------------|------------------|-------------------------|
| Edit Pending Design | ✔ | ✔ | ✔ | ✔ | ✔ |
| Unpublish | ✘ | ✔ | ✔ | ✘ | ✘ |

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we missing "Submit for Review" as an operation?


**Key Notes:**
- Provider Admins have root-level visibility and can see private designs from all organizations.
- Catalog approval queues are org-specific—only members of an organization can see its pending approvals, unless the user is a Provider Admin.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Org Admins are able to review (approve/deny requests) for designs submitted for review within their organization, right? Cloud fully supports Organization-specific catalog publishing queues, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

Copy link
Contributor

@sangramrath sangramrath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fitzergerald @zihanKuang I checked https://deploy-preview-454--bejewelled-pegasus-b0ce81.netlify.app/kanvas/getting-started/starting-pattern/ but I couldn't find the updates images there.

Also are we addressing the following question "Can a design be edited after it has been published" in this article?

@vishalvivekm
Copy link
Contributor

@zihanKuang
Thank you for your contribution!
Let's discuss this during the website call today at 7 AM CT

adding it as an agenda item to the meeting minutes.

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

Successfully merging this pull request may close these issues.

5 participants