gvisor.dev/gvisor@v0.0.0-20240520182842-f9d4d51c7e0f/website/blog/README.md (about)

     1  # gVisor blog
     2  
     3  The gVisor blog is owned and run by the gVisor team.
     4  
     5  ## Contact
     6  
     7  Reach out to us on [gitter](https://gitter.im/gvisor/community) or the
     8  [mailing list](https://groups.google.com/forum/#!forum/gvisor-users) if you
     9  would like to write a blog post.
    10  
    11  ## Submit a Post
    12  
    13  Anyone can write a blog post and submit it for review. Purely commercial content
    14  or vendor pitches are not allowed. Please refer to the
    15  [blog guidelines](#blog-guidelines) for more guidance about content is that
    16  allowed.
    17  
    18  To submit a blog post, follow the steps below.
    19  
    20  1.  [Sign the Contributor License Agreements](https://gvisor.dev/contributing/)
    21      if you have not yet done so.
    22  1.  Familiarize yourself with the Markdown format for the
    23      [existing blog posts](https://github.com/google/gvisor/tree/master/website/blog).
    24  1.  Write your blog post in a text editor of your choice.
    25  1.  (Optional) If you need help with markdown, check out
    26      [StakEdit](https://stackedit.io/app#) or read
    27      [Jekyll's formatting reference](https://jekyllrb.com/docs/posts/#creating-posts)
    28      for more information.
    29  1.  Click **Add file** > **Create new file**.
    30  1.  Paste your content into the editor and save it. Name the file in the
    31      following way: *[BLOG] Your proposed title* , but don’t put the date in the
    32      file name. The blog reviewers will work with you on the final file name, and
    33      the date on which the blog will be published.
    34  1.  When you save the file, GitHub will walk you through the pull request (PR)
    35      process.
    36  1.  Send us a message on [gitter](https://gitter.im/gvisor/community) with a
    37      link to your recently created PR.
    38  1.  A reviewer will be assigned to the pull request. They check your submission,
    39      and work with you on feedback and final details. When the pull request is
    40      approved, the blog will be scheduled for publication.
    41  
    42  ### Blog Guidelines {#blog-guidelines}
    43  
    44  #### Suitable content:
    45  
    46  -   **Original content only**
    47  -   gVisor features or project updates
    48  -   Tutorials and demos
    49  -   Use cases
    50  -   Content that is specific to a vendor or platform about gVisor installation
    51      and use
    52  
    53  #### Unsuitable Content:
    54  
    55  -   Blogs with no content relevant to gVisor
    56  -   Vendor pitches
    57  
    58  ## Review Process
    59  
    60  Each blog post should be approved by at least one person on the team. Once all
    61  of the review comments have been addressed and approved, a member of the team
    62  will schedule publication of the blog post.