ccapture.js VS docsify

I also tried to find a better recording method. Since I’m now using canvas, there are some solutions to recording that seemed quite elegant. For example, paper.js uses requestAnimationFrame to achieve its smooth animation. There are libraries like ccapture.js that hooks into the various methods like requestAnimationFrame and setInterval, allowing it to render each frame separately.

I actually spent a fair bit of time on this and eventually got something to work. Someone named "spite" made a great library called CCapture for doing this, but it needs to be updated and repackaged for ES6. Right now it is painful to integrate into your project, but it could be super-easy. You can help to encourage someone to fix the issues here.

Check out CCapture.

The image capture step uses ccapture to ensure that the playback frame is converted to an image. All frame images to webm video.

ccapture.js basically let's you write out frames from a threejs camera, which you then stitch together with ffmpeg.

I use ccapture, using the png option, which will spit out a tar with a png of each frame, and then I stitch them with ffmpeg.

This video is 1800 frames (30 FPS * 60s)... a browser trying to save 1800 individual frames would lock up and die. Ccapture.js hooks into the browser's rendering code and captures the frames as a 'blob' - a binary object that is often used for streaming video - and then wraps them up into one single download.

p5.js runs the sketch, ccapture.js captures all of the frames (1800 in this video), and ffmpeg combines the frames into an MP4.

I use ccapture.js, which captures the frames as a blob in real-time then exports it as a .tar file full of jpgs when the sketch is finished (with 'finished' defined as reaching 1800 frames, in this case). This is a lot better than having the browser try to save 1800 jpgs the usual way.

Docsify is frequently updated; the latest release was on June 24, 2023, and the most recent update was on December 17, 2023. It is MIT-licensed and has an active Discord community.

okay new plan, does anyone know how to do this docsify on github? i obviously am a noob on github and recently on reddit. I'd like to help where i can but my knowlegde seems to be my handycap. i could provide you a trash-mail, if you need one, but i need a PO (product owner) to manage the git... i have no clue about this yet (pages and functions and stuff)

The tools to author it aren't that important, frankly. Ask your audience what they're most comfortable using and try to meet them there.

If the stakeholders are technical, you have more options. If they aren't, I hope you like Google Docs or Word, because if you give them anything other than that or a PDF, they'll probably complain. At worst, yeah, write it in a long Markdown text file and use tools like pandoc to transform that into other formats as needed.

If you do need a website and you're not generating enterprise-scale amounts of content (and it sounds like you're not) try things that let you avoid needing build steps and infrastructure if at all possible, so you can iterate and deploy changes with as little friction as you can.

Tools like Docsify[1] can take a pile of Markdown files and serve a site out of them, client- or server-side, without a static build step. Depending on the org, you can get away with GitHub's default rendering of Markdown in a repo. Most static site builds for stuff your scale are overengineered instances of premature optimization.

Past those initial hurdles, the format and tools challenges are all in maintenance. How can you:

- most easily keep the content up to date

- delegate updates as the staff grows or changes

- proactively distribute updates ASAP to the people who'd most benefit from receiving them

That's going to depend a lot more on who'll contribute updates, what their technical proficiency's like, and how they prefer to communicate. It might be a shared git repo and RSS or Slack notifications if they're comfortable with those things, and it might be a Google Doc and email if they're like most non-technical stakeholders.

1: https://docsify.js.org

Big fan of https://docsify.js.org since theres no need to compile your static site. A small amount of js just renders markdown.

If you are searching for examples of an arbitrary Jellyfin support site, visit https://travisflix.com/help/#/support (or help.travisflix.com which redirects to the /help/ URI of the TLD) to take a look at what I have done with docsify on Github Pages.

*Leantime - Competitor to OP? Updated recently, uses Docsify, no demo :(

There are a lot of open-source projects that can help businesses to save time and money. For example, we created a Free Admin panel a few months ago https://github.com/altence/lightence-admin That's an example of free documentation generator https://github.com/docsifyjs/docsify There are a lot more examples. And I want to find an idea of some similar generic solutions that can help various types of businesses