As we get closer to site launch and get more open questions closed, we'll need to add how-to guidance for content creators (both core team and external contributors). This issue is a holding place for storing those:
Update top-level README.md with VuePress-specific info deferring into issue https://github.com/ipfs/ipfs-blog/issues/22 for bulk of work, but will trim down readme in the interim to avoid confusion
Make canonical tags list easily accessible: in repo readme and in Forestry edit pages
Remind post authors that header art shouldn't have too many words, to avoid conflicting with card titles
Reword image-crop instructions
As we get closer to site launch and get more open questions closed, we'll need to add how-to guidance for content creators (both core team and external contributors). This issue is a holding place for storing those:
- [x] ~~Update top-level `README.md` with VuePress-specific info~~ deferring into issue https://github.com/ipfs/ipfs-blog/issues/22 for bulk of work, but will trim down readme in the interim to avoid confusion
- [x] Make canonical tags list easily accessible: in repo readme and in Forestry edit pages
- [x] Add explanatory notes in Forestry edit pages wherever appropriate, particularly for image naming guidance (see https://github.com/Ricardo-Silva91/ipfs-blog-vuepress/issues/10#issuecomment-761131072 for context)

- [x] Remind post authors that header art shouldn't have too many words, to avoid conflicting with card titles
- [x] Reword image-crop instructions
<!-- github-sync-id:787140132 -->
@jdiogopeixoto -- For Special Cards templates in Forestry, do we really need both the Name and Title fields? As far as I can see, these will always be the same value. Can we remove one?
@jdiogopeixoto -- For Special Cards templates in Forestry, do we really need both the Name and Title fields? As far as I can see, these will always be the same value. Can we remove one?

<!-- github-comment-id:786849217 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As we get closer to site launch and get more open questions closed, we'll need to add how-to guidance for content creators (both core team and external contributors). This issue is a holding place for storing those:
Update top-leveldeferring into issue https://github.com/ipfs/ipfs-blog/issues/22 for bulk of work, but will trim down readme in the interim to avoid confusionREADME.mdwith VuePress-specific infoMake canonical tags list easily accessible: in repo readme and in Forestry edit pages
Add explanatory notes in Forestry edit pages wherever appropriate, particularly for image naming guidance (see https://github.com/Ricardo-Silva91/ipfs-blog-vuepress/issues/10#issuecomment-761131072 for context)

Remind post authors that header art shouldn't have too many words, to avoid conflicting with card titles
Reword image-crop instructions
@jdiogopeixoto -- For Special Cards templates in Forestry, do we really need both the Name and Title fields? As far as I can see, these will always be the same value. Can we remove one?

Yes, looks like we are not using the
Namefield so we can remove it.