⚠️ There is now a new publishing flow on Supertype.ai/notes. You should write directly to thessiterepository (markdown, and put them in/content/notes/) and use this repository only for image storage and serving.
This repository provides a publishing gateway to our website
Any articles in Markdown format (.md), in the /articles subdirectory, will be published to the website's Article section.
- Please don't use large images. Keep images to a reasonable size by sizing it down beforehand using Photoshop, GIMP, or any image editor of your choice
- Please keep images in the
_/imagesdirectory, and link accordingly using relative linking (e.g.) in markdown notation - Use *less than 6 images per articles ideally
- Try to include linking to other, revelant articles on Supertype.ai's own website / blogs. This will help readers find related content and promote the work of other authors on the site.
This automation considers the file name as the post slug i.e if the name of the file is data-science-101.md then the post slug is /notes/data-science-101.
You can have more than one category for a post. You should use them correctly. For the most part, this would be at least knowledge and notes. Very rarely would you use internal-guides for internal documentation that are OK for public consumption.
taxonomy:
category:
- knowledge
# - internal-guides
- notes
post_tag:
# Add tags that are relevant to the post
- postgres
- bigquery
- analytics
- database
- dataopsI often get asked how I write my articles. I put my thoughts together on Writing better technical articles