-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation : glitch app link & video ingestion documentation #104
Conversation
lastmod: 2022-05-31 | ||
name: Video Ingestion | ||
title: Video Ingestion | ||
description: Inlive support WebRTC as our video ingestion. We have RTMP in development on progress. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ingrid011 this is will be used as SEO description meta tag, so consider to replace it with a summary about the content.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tyohan Being revised to be : Inlive uses WebRTC which supports video ingestion on all platforms including web, has better latency than RTMP, and can be used to build your own OBS client
.
If counted, it is 157 characters (still reach the SEO description best practice until 160 characters). Kindly advice is it okay mas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ingrid011 I know in my article we don't have the link for some abbreviations like RTMP, WebRTC, and OBS. But will be great to refer them to a link that can explain it.
Deploying with Cloudflare Pages
|
@ingrid011 it seems we have redundant menus for video input or ingestion as shows as in this screenshot Maybe the video ingestion doc needs to change into Choosing RTMP vs WebRTC |
Apologize mas, at first I didn't know the terms are the same. 😅 |
@tyohan @ingrid011 How about we group the video ingestion and video input into one category, for example "Learn" category (similar with the Tutorial). Because I think the content of video ingestion and video input fits with this category which provides an educational content to the user to ensure the user knows what we are offering to them and how our product can benefit to them. |
@faiq-naufal yups mas, I agree with it since it's better in the tutorial one segment and I think it neater if being categorized like that because it's an additional information for developers. I can't think better name though aside from mas advice ('Learn'). Thought of 'Support Articles', but it seems 'Learn' is more compact name. updates @faiq-naufal & @tyohan : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some additional reviews, especially with the weight in front matter. Because the weight is important to describe how the menu and page are ordered and sorted. Do you notice in your screenshot if the next page link in the "Learn" page list is not pointing to the "Choosing RTMP vs WebRTC" page? This is because the weight is not ordered properly. Whenever you add a new page or change the page structure, please make sure the pages are already ordered properly.
https://github.com/asumsi/inlive-website/blob/dev/themes/inlive/archetypes/README.md
Description
We need to include sample code to make it easier for the user to know how to implement the tutorial by the .
Also, we need to add documentation related to video ingestion WebRTC vs RTMP related to the issue #11.
Implementation