hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-29 09:47:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

getting_started.md: move information about sbt plugin to the bottom and change its type to a tip

Browse Source 
According to the call-outs doc, "tip" should be used for optional information, and "note" for important information that you want to highlight. SBT plugin is not widely used and important.
This commit is contained in:
Karol Lewandowski 2022-08-16 14:40:44 +02:00
parent 60c1e85177
commit 41f113370b
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
topics/basics/getting_started.md
View File

@ -15,10 +15,6 @@ There are three supported workflows available for building plugins.
The recommended workflow for new projects is to [use GitHub Template](#using-github-template) or to [use Gradle](#using-gradle) to create everything from scratch.
The old [Plugin DevKit](#using-devkit) workflow still supports existing projects.
> If a new plugin will be Scala-based, a dedicated [SBT plugin](https://github.com/JetBrains/sbt-idea-plugin) is available.
>
{type="note"}
## Using GitHub Template
* [Developing plugins using GitHub Template](github_template.md)
@ -38,3 +34,7 @@ The old [Plugin DevKit](#using-devkit) workflow still supports existing projects
* [Running and Debugging a Plugin](running_and_debugging_a_plugin.md)
* [Deploying a Plugin](deploying_plugin.md)
* [Publishing a Plugin](publishing_plugin.md)
> A dedicated [SBT plugin](https://github.com/JetBrains/sbt-idea-plugin) is available for plugins implemented in Scala.
>
{type="tip"}