Blog
Mailocity and Zappocity each have a blog: news, how-tos and changes, written in the admin panel. No files or deploys are needed.
- The Mailocity blog is at
/blogon Mailocity's site. - The Zappocity blog is at
/blogon the Zappocity homepage's host, and at/zappocity/blogon any host.
Each has a page of posts (newest first, ten at a time), a page per post, a page per tag (/blog/tag/news) and an Atom feed (/blog/feed.xml) for feed readers.
Writing a post
In the panel, Blog → New post. The Mailocity panel writes the Mailocity blog and the Zappocity panel the Zappocity blog.
- Title, and its address: filled in from the title as you type (
team-templates-are-here), and changeable. Each address is unique in its blog. - Byline: the author's name as shown.
- Summary: one or two sentences for the list and the feed.
- Tags: comma-separated, such as
webmail, teams. - Text in Markdown:
**bold**,*italics*,# headings,- lists,> quotes, andcode;- links (
[text](https://...)): to http(s), mail, this site's own pages (/kb/webmail) and anchors (#how). Anything else, including raw HTML, is shown as text. - Preview shows it as it will look.
- Status:
- Draft is not shown.
- Published shows it at Publish at. Leave the time empty for now, or give a time in the future to schedule the post.
View opens the published post. Delete removes it from the blog and the feed.
Staff need the content permission ("Write the blogs") to write, change and delete posts. Everyone with read can see them in the panel.
Command line and API
corpsuite blog posts site=mailocity
corpsuite blog post add site=mailocity slug=hello title="Hello" body="**Hi** there" status=published authorName=Ann
corpsuite blog post set POST-ID site=mailocity slug=hello title="Hello" status=draft
corpsuite blog post delete POST-ID
corpsuite blog preview body="*hi*"
In the admin API: /v1/blog/posts, /v1/blog/posts/{postId} and /v1/blog/preview. See api/openapi.yaml.