Hi Ron, What about storing them in the docs repo directly? The site's branch is this one https://github.com/apache/lucenenet-site/tree/asf-site but what if we created a branch called "images" or something like that? and then you can references them using the raw.githubusercontent.com domain, for example this is an image in the "master" branch as a raw image that can be referenced in html/markdown: https://raw.githubusercontent.com/apache/lucenenet-site/master/logo/lucene-net-color.png
Alternatively, another repo could work too What do you think? Shannon On Tue, May 18, 2021 at 3:37 PM Ron Clabo - Git <[email protected]> wrote: > Hey Shannon (Shazwazza) and anyone else with a good idea for solving this, > > > > I could use some advice. NightOwl888 and I just revisited the process of > how to setup a dev box for running Eclipse in a VM on windows with the > ability to debug Java Lucene 4.8. He supplied the knowhow, and I got it > going on my machine and document the process, taking lots of screenshots > along the way. > > > > So now I have this word doc with notes and 83 screenshots. Yah, I know, > kinda long. There are more than a few steps J > > > > Shad wants me to turn it all into a markdown doc for the website's > contributors sections. Seems easy enough. The challenge is the images. > We > don't really want them in the main repo since it increases the size of the > repo and time it takes to clone. > > > > So do you have a good suggestion of where I could put them? > > > > One thought was to create a sister repo for such artifacts and have the > markdown doc in the main repo reference the images in the sister repo. Such > a repo could be LuceneNetArtifacts for example. We could also use it for > other large items related to Lucene (e.g. test text) that isn't code. > > > > But I wanted to reach out to you and the Lucene Dev community at large in > case you or someone else has a better idea? > > > > Thoughts? > > > > Thanks, > > > > -Ron > > rclabo > >
