Update from Forestry.io

Harsh Shandilya created content/posts/why-should-you-be-using-kotlin-s-explicit-api-mode-for-your-library-projects.md

.forestry/front_matter/templates/blog-post.yml

@@ -44,3 +44,4 @@ pages:
 - content/posts/teachingkotlin-part-1-classes-and-objects-and-everything-in-between.md
 - content/posts/teachingkotlin-part-2-variables.md
 - content/posts/why-i-went-back-to-the-gradle-groovy-dsl.md
+- content/posts/why-should-you-be-using-kotlin-s-explicit-api-mode-for-your-library-projects.md

content/posts/why-should-you-be-using-kotlin-s-explicit-api-mode-for-your-library-projects.md

@@ -0,0 +1,11 @@
++++
+categories = ["android", "kotlin"]
+date = 2020-11-03T07:30:00Z
+description = "Building libraries is hard, and keeping track of your public API surface harder. Kotlin 1.4's explicit API mode tries to make the latter not be difficult anymore."
+draft = true
+slug = "kotlin-explicit-api-mode"
+social_image = "/uploads/kotlin_800x320.png"
+tags = []
+title = "Why should you be using Kotlin's explicit API mode for your library projects"
+
++++