website/archetypes/blog-post.md

2.6 KiB
Raw Permalink Blame History

layout: blog title: "{{ replace .Name "-" " " | title }}" date: {{ .Date }} draft: true slug:

Author: (), <another author's name> ()

Replace this first line of your content with one to three sentences that summarize the blog post.

This is a section heading

To help the reader, organize your content into sections that contain about three to six paragraphs.

If you're documenting commands, separate the commands from the outputs, like this:

  1. Verify that the Secret exists by running the following command:

    kubectl get secrets
    

    The response should be like this:

    NAME                    TYPE                                  DATA   AGE
    mysql-pass-c57bb4t7mf   Opaque                                1      9s
    

You're free to create any sections you like. Below are a few common patterns we see at the end of blog posts.

Whats next?

This optional section describes the future of the thing you've just described in the post.

How can I learn more?

This optional section provides links to more information. Please avoid promoting and over-represent your organization.

How do I get involved?

An optional section that links to resources for readers to get involved, and acknowledgments of individual contributors, such as:

  • The name of a channel on Slack, #a-channel

  • A link to a "contribute" page with more information.

  • Acknowledgements and thanks to the contributors. <person's name> ([](https://github.com/)) who did X, Y, and Z.

  • Those interested in getting involved with the design and development of , join the . Were rapidly growing and always welcome new contributors.