updating plugin introduction

[mhmohona]

Explanation

Updated plugin PR adding more info about

• What is a WasmEdge plugin?
• How can WasmEdge plugins be used?
• Benefits of using WasmEdge Plug-in System

Related issue -

#85

Reopening PR #84 for passing DOC test

What type of PR is this

/kind documentation

Proposed Changes

[alabulei1]

Hello, I am a code review bot on flows.network. Here are my reviews of code commits in this PR.

---

Overall Summary:

In this pull request, there are multiple patches that update the introduction to the WasmEdge Plug-in System and provide more details about its architecture, usages, and benefits. These changes enhance understanding and provide valuable additional information about WasmEdge plugins. The patches seem to be mostly additions of new content, but it may be important to verify if any important information has been omitted or if there are inconsistencies with the existing content. Additionally, there is a patch that adds various new packages and another patch that removes the mermaid dependency. The removal of the mermaid dependency should be confirmed for its intention and if all necessary changes have been made to handle its absence.

Details

Commit 1552fd4f7fa9696f4cfd32fc18276d5aa9d20433

Key Changes:

• The patch updates the introduction to the WasmEdge Plug-in System.
• It adds more details about the plug-in architecture and how it can extend the functionality of the WasmEdge runtime.
• It introduces a diagram that explains the interaction between the host application, plugin shared library, and the WasmEdge runtime.
• It adds a section about the usages and benefits of using WasmEdge plugins.

Potential Problems:

• The patch does not mention any specific problems or issues.

Overall, the changes in this patch enhance the understanding of the WasmEdge Plug-in System and provide more details about its usages and benefits.

Commit 01233502b7677b111571ca4fbe86ca164504ff11

Key changes:

• The introduction to WasmEdge plugins has been expanded to provide more information on their usages and benefits.
• The specific use cases and scenarios where WasmEdge plugins can be applied have been described in detail.

Potential problems:

• The changes made in this patch seem to be mostly additions of new content. However, without a context on what was there before, it is difficult to determine if any important information has been omitted or if there are inconsistencies with the existing content.

Overall, the changes seem to be providing valuable additional information about WasmEdge plugins and their applications.

Commit fc3af9faa65ec1a5b21fa2c91948e9687dc096c0

Key changes:

• Added "mermaid" package to the package.json file.
• Added a new entry for "mermaid" in the package-lock.json file.
• Added various new packages such as "@braintree/sanitize-url", "cose-base", "cytoscape", "cytoscape-cose-bilkent", "cytoscape-fcose", "layout-base", and "d3" to the package-lock.json file.

Potential problems:

• There are no potential problems with the changes.

Commit cc0d6cc51ec62321eb33a92e30742ed9eb98c6df

Key Changes:

• Added support for mermaid diagrams in the Docusaurus config file.
• Added the "@docusaurus/theme-mermaid" package as a dependency.
• Updated the package-lock.json file with the new "@docusaurus/theme-mermaid" package and its dependencies.
• Added the "@docusaurus/theme-mermaid" package as a dependency in the package.json file.

Potential Problems:

• There are no potential problems identified in this pull request. The changes appear to be straightforward and related to adding support for mermaid diagrams in the Docusaurus project.

Commit db6ed5194267d481a147ab73967fc4c746de635d

Key changes:

• The patch removes the mermaid dependency from both the package-lock.json and package.json files.
• The package-lock.json file has 93 lines deleted.

Potential problems:

• The removal of the mermaid dependency might cause issues if any part of the code relies on mermaid functionality. It's important to verify if the removal is intentional and if all the necessary changes are made to the code to handle the absence of mermaid.

Overall, the patch seems to be a straightforward removal of the mermaid dependency. It would be good to communicate with the contributor to confirm the reasons for removing the dependency and to ensure that all necessary changes and tests have been carried out.

[adithyaakrishna]

@alabulei1 CI Workflows need your approval to run. Its a default feature of GH Actions. More Info: https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks

[alabulei1]

Hi @mhmohona Sorry for my delay. Could you please fix the conflicts?

[adithyaakrishna]

@mhmohona Could you please address the above comment?