[incubator-devlake-website] branch kw-devlake-3468-plugin-blueprint updated: docs: remove detailed information for PluginBlueprint interface

[kl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

klesh pushed a commit to branch kw-devlake-3468-plugin-blueprint
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git


The following commit(s) were added to refs/heads/kw-devlake-3468-plugin-blueprint by this push:
     new d011d248a docs: remove detailed information for PluginBlueprint interface
d011d248a is described below

commit d011d248ae6b48b8cc3e87f1f86ec94f604cb1de
Author: Klesh Wong <zh...@merico.dev>
AuthorDate: Mon Nov 7 15:03:56 2022 +0800

    docs: remove detailed information for PluginBlueprint interface
---
 docs/DeveloperManuals/PluginImplementation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/DeveloperManuals/PluginImplementation.md b/docs/DeveloperManuals/PluginImplementation.md
index badee9c31..b77b40eba 100644
--- a/docs/DeveloperManuals/PluginImplementation.md
+++ b/docs/DeveloperManuals/PluginImplementation.md
@@ -37,7 +37,7 @@ A plugin mainly consists of a collection of subtasks that can be executed by Dev
 4. [PluginApi](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_api.go) lets a plugin exposes some self-defined APIs
 5. [Migratable](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_db_migration.go) is where a plugin manages its database migrations 
 6. [PluginModel](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_model.go) allows other plugins to get the model information of all database tables of the current plugin through the GetTablesInfo() method.If you need to access Domain Layer Models,please visit [DomainLayerSchema](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/)
-7. [PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_blueprint.go) is the foundation for Blueprint and Plugin to collaborate to generate a reasonable Pipeline Plan based on User Settings, for example, users may declare that he wanted to collect data from a Github Repo, it implies not only the issues/prs, but also the git-meta-data including commits history, branches, tags, etc, in order to do it and do it fast, leveragin [GitExtractor](../Plugins [...]
+7. [PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_blueprint.go) is the foundation for Blueprint and Plugin to collaborate to generate a reasonable Pipeline Plan based on User Settings, for example, users may declare that he wanted to collect data from a Github Repo, it implies not only the issues/prs, but also the git-meta-data including commits history, branches, tags, etc, in order to do it and do it fast, leveraging [GitExtractor](../Plugin [...]
 
 The diagram below shows the control flow of executing a plugin: