Best way to store assets?

[Arne1303]

I got a simple setup using the symlink approach outlined on the website. Now, I do want to add some images, but it seems that this is a lot more tricky than it first seems. Converge kinda expects me to handle the image hosting myself, so I can now either:

1. Upload the assets to a s3 Bucket and get the URL from there, separating the documentation repository and assets.
2. Put the assets into my public directory again, separating them from the documentation repository, as they are then stored in the main directory.
3. Make a custom filesystem location pointing to /docs/assets (as an example) which would be inside the documentation repository, however, I would then also need to create a custom endpoint to get the images which would create a lot of overhead. And I still would prefer if the .png would be in the same or an adjacent directory of the .md where they are used.

Am I missing something, or are all the options a bit complicated? I would expect that I can just, put my assets like .png, .jpg or If I would want even .mp4 (even though I those might be better located on YT or an S3) into the same folder as the .md or into a subfolder within the documentation modules. Converge should then handle them for me. That way, handling assets would be a lot easier and faster.

[CharrafiMed]

Personally, I usually place assets in the public directory or upload them to GitHub (that’s the approach I used in my small package: https://convergephp.com/plugins/gsm/docs/overview).
But I’ve come to realize that keeping assets directly inside the docs repository is much cleaner (from you).
What If we did essentially the same concept: createing a symlink so that laravel-app/public/assets points to docs-repo/assets.

I haven’t tested this approach yet (surely will try and use it), but in principle it’s the same idea as running php artisan storage:link, just exposing docs-repo/assets through a publicly accessible path (so nginx can serve it).