I like the template idea, that could be added to the Solr-site. Maybe in the footer of each case study is a “Got a good story to share, contribute yours” with a link to the template.
This section https://solr.apache.org/community.html#powered-by should be replaced with Case Studies. We could also modify on the main homepage the “Trusted and Proven” section to list out the specific case studies. Let’s use that time together in Glasgow to get a few more written. Eric > On Aug 10, 2026, at 5:03 PM, Lisa Biella <[email protected]> wrote: > > Thanks everyone, I think we are converging on a good approach. > > I agree that we should not create an empty section. I already have a first > case study we can use, thanks to Eric Pugh and Cedric Ulmer, so we have > something to start with [Datafari Case Study > <https://docs.google.com/document/d/1FR3YrKAMaTOyHQENzJnNYQJ7jAtFKduCqzN7BljZ8zs/edit?usp=sharing > > <https://docs.google.com/document/d/1FR3YrKAMaTOyHQENzJnNYQJ7jAtFKduCqzN7BljZ8zs/edit?usp=sharing>> > ]. > > Regarding the format, I agree that case studies could technically be > implemented as a category of posts. We could also create them ourselves > when enough public information about a Solr deployment is available, or > contact companies and projects directly. I have prepared a simple template > that they can fill in, to make contributing as easy as possible [Template > <https://docs.google.com/document/d/1qyTwALbrJwmuJVSAN2XnLDqTXZxdhN3AeLlc7zYbmeI/edit?usp=sharing > > <https://docs.google.com/document/d/1qyTwALbrJwmuJVSAN2XnLDqTXZxdhN3AeLlc7zYbmeI/edit?usp=sharing>>]. > Since > the Solr website is based on Markdown, one option would be to provide an > example .md file where contributors only need to replace the relevant > fields. An even better option could be a simple form that automatically > generates the .md file after submission, ready to be reviewed and added to > the website. > > My only concern with treating case studies mainly as blog content is > visibility. Technical posts will naturally remain the majority of the blog, > while I think case studies serve a different purpose: someone evaluating > Solr is likely to look for real examples of organizations and projects > using it, ideally finding a use case similar to their own. > > So I would make Case Studies a clearly visible section of the website, > potentially powered by posts underneath, but accessible directly from the > main navigation or homepage. > > We are also considering proposing this as a roundtable / Birds of a Feather > topic at Community Over Code. It could be a good opportunity to collect > more real-world Solr stories and then turn them into useful content for the > website. > > > *Lisa Biella*Digital Marketing Manager > e-mail: > *[email protected] <[email protected]>* > > *Sease* - Information Retrieval Applied > Consulting | Training | Open Source > > Website: Sease.io > LinkedIn <https://linkedin.com/company/sease-ltd > <https://linkedin.com/company/sease-ltd>> | Twitter > <https://twitter.com/seaseltd <https://twitter.com/seaseltd>> | Youtube > <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ > <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ>> | Github > <https://github.com/seaseltd <https://github.com/seaseltd>> > > > > On Fri, May 1, 2026 at 11:45 PM Chris Hostetter <[email protected]> > wrote: > > > > > : Would this be really another category of a "post" > > : https://solr.apache.org/posts.html <https://solr.apache.org/posts.html> ? > > I could see doing this and > > : additionally linking to it from elsewhere in the site to make these "case > > : studies" more prominent. > > > > Yeah ... I think this idea (user stories about how people use Solr) was > > one of the main "use cases" that came up when the "official" solr blog was > > first suggested, about why we should make sure it's easy for anyone in the > > community to submit a blog post, thus the blurb... > > > > https://solr.apache.org/blog.html <https://solr.apache.org/blog.html> > > >> Have something to share? We're always looking for new articles! If you > > >> have one you'd like to contribute, or would like to link out to an > > >> external post, create a PR using the instructions here. > > > > > > In general I think that blog posts (with their intrinsic "publish date" > > metadata) are a good way of making sure information like case study write > > ups can be viewed in the appropriate context (ie: "This case study seems > > like a perfect use for feature X, why don't they use it? ... oh, because > > this case study was written 3 years ago.") > > > > > > We might be able to encourage more "case study" type submissions to the > > blog if it had a dedicated "category tab" at the top of the page (like > > "News" and "Security") ... but that brings up the chiecken-vs-egg problem > > of adding the category before anyone has submitted any :) > > > > > > -Hoss > > http://www.lucidworks.com/ <http://www.lucidworks.com> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
