Handbook: DevRel Addition #4070
Conversation
Added guidelines for content production phases including pre-production, production, and post-production.
Updated the structure and content of the marketing videos section to focus on Developer Relations content, including audience targeting and production phases.
src/handbook/marketing/videos.md
Outdated
| ### Distribution Channels | ||
| ### Content Production |
There was a problem hiding this comment.
3 # means h3 in HTML. Subitems should be a fourth level of headings, h4. So 4 times a #.
src/handbook/marketing/videos.md
Outdated
| - DaVinci Resolve with exports to convertible formats for Premiere Pro and After Effects. | ||
| - Music, SFX, and Foley from [Epidemic Sound](https://www.epidemicsound.com/). | ||
| - Blackmagic Design DaVinci Resolve Speed Editor for rapid editing. | ||
| ### Distribution Channels |
There was a problem hiding this comment.
@KristopherLeads is this WIP? I recommend linking to the social media section, where all social channels are listed.
|
@KristopherLeads if you clone the website and work on branches instead of forking it, we’ll be able to see the preview 🙂 Also, I think it might be helpful to include a link to a shared Drive directory where all open files, scripts, and exports are stored. That way, everyone has access to the same materials. As for editing tools, it could be good to align on a common platform (or at least standardise exports to Premiere or After Effects). It doesn’t have to be decided right now; it could just be something to revisit later on. |
Expanded the Developer Relations content section to include tools and processes for content generation, production phases, and uploading guidelines. Detailed the equipment and software used by Kristopher Sandoval for filming and editing.
| * Audio should be filtered and cleaned up. In editors like Davinci, you may have an AI isolation option - please use these techniques to reduce room noise, but balance it with natural sound and EQ to make sure that the audio is not overly compressed or otherwise fatigueing for the listener. | ||
| * Solutions like Adobe podcast can be used to clean up audio from noisy sources - but as with AI isolation, make sure you use it sparingly to not overwhelm the listener with artifacting or over-compression. | ||
| * Video edits should be professional and focused on the content at hand. Jump cuts are fine, but should be used only to emphasise a point or to cleanly transition between video - it should not be frentic or distracting. | ||
| * Video effects can be applied, but again, sparingly. Try not to be too visually loud or over-stimulating - Developer Relations content is somewhere between educational and entertainment, but we're not trying to go for frentic YouTube here. |
There was a problem hiding this comment.
@KristopherLeads could you add a link to a Drive folder where all the assets, scripts, and exports are hosted?
|
|
||
| ##### Thumbnail | ||
|
|
||
| Provide a thumbnail for the video. Try to keep the title and any featured content simple, relatively high-contrast, and minimal. The idea here is to give an immediate preview of what is going to be talked about - not to engage in "clickbait" or catch someone's eye with extremely large or garish text. |
There was a problem hiding this comment.
@KristopherLeads a link to open files and exports in our Drive for thumbnails would be useful too, like we have for blog posts.
4 participants
Description
This is the first iteration of documentation around DevRel content at FlowFuse. This will be expanded soon - I just wanted to get the base version live before iterating.
Related Issue(s)
n/a
Checklist