Skip to content

Conversation

@adityamparikh
Copy link
Contributor

address #11. If merged, can incorporate into https://solr.apache.org/guide/solr/latest/

@epugh
Copy link
Contributor

epugh commented Nov 5, 2025

I think this should actually be part of the Solr mono repo versus here... we should be thinking about Solr 10.1 I suspect. We still need to get release tooling done. One idea... we can publish this tutorial as a blog on Solr site whenever we are ready. So maybe long term it's in the ref guide but short term a copy in the blog?

@epugh
Copy link
Contributor

epugh commented Nov 5, 2025

Also, I discovered LLM good at writing tutorial. I took a bats test and prompted to follow existing tutorials and got out the OpenNLP tutorial!!

Copy link

@janhoy janhoy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree that the tutorial perhaps belongs in ref-guide once we have a stable release here. But for now I think it is ok to have it in this repo.

However, it should not be HTML format, perhaps Markdown or Asciidoc for easy move to ref-guide later? I believe GitHub renders both MD and AsciiDoc well when browsed on the website.

@adityamparikh
Copy link
Contributor Author

adityamparikh commented Nov 17, 2025

Agree that the tutorial perhaps belongs in ref-guide once we have a stable release here. But for now I think it is ok to have it in this repo.

However, it should not be HTML format, perhaps Markdown or Asciidoc for easy move to ref-guide later? I believe GitHub renders both MD and AsciiDoc well when browsed on the website.

@janhoy I made it HTML with the intention of the doc being linked from https://solr.apache.org/guide/solr/latest/. Should I keep this or convert to MD? We have https://github.com/apache/solr-mcp/tree/main/dev-docs here in addition to Readme and Contributing mds

@janhoy
Copy link

janhoy commented Nov 18, 2025

HTML is not friendly for future editing. I'd choose asciidoc as format and let GitHub render it for us for now. Then, moving it into the ref-guide (which is asciidoc) later would be easy.

@epugh
Copy link
Contributor

epugh commented Nov 18, 2025

Agreed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants