[
https://issues.apache.org/jira/browse/SOLR-14444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364300#comment-17364300
]
Cassandra Targett commented on SOLR-14444:
------------------------------------------
bq. it struck me that the hierarchy such as "Deployment Guide -> Scaling Solr
-> SolrCloud Clusters -> Aliases" is perhaps not consistent.
Regarding this entire point, I'm not really satisfied with the way I've done it
so far so I appreciate the feedback.
The thing I struggled with was the idea that some of this information is only
relevant to certain users, and requires some level of understanding other
concepts. Aliases are only for collections; and collections are SolrCloud
constructs. I had similar challenges with the Collections API - collections are
SolrCloud only, and required to configure SolrCloud. So I was unsure how well
splitting these into different sections would work. Would it be confusing? So I
erred on the side of keeping as much of SolrCloud stuff together, and as I
said, I'm not thrilled with the outcome.
There might also have been a bit of exhaustion - I thought so much and so hard
about what to do with "Scaling" in general that it started to make my brain
hurt. Now with a few weeks away from the topic, I think it's possible a section
for SolrCloud config under "Configuration Guide" might work. I'll give it a try
and see how it works.
> Ref Guide Redesign Phase 2: Page Organization Overhaul
> ------------------------------------------------------
>
> Key: SOLR-14444
> URL: https://issues.apache.org/jira/browse/SOLR-14444
> Project: Solr
> Issue Type: Improvement
> Components: documentation
> Reporter: Cassandra Targett
> Assignee: Cassandra Targett
> Priority: Major
> Fix For: main (9.0)
>
>
> SOLR-14173 changed the look & feel of the Ref Guide, and left one glaring
> problem unresolved: our top-level categories are far too many for that sort
> of design.
> This issue will track a full reconsideration of the Ref Guide organization. I
> have a couple of thoughts and will update this issue with those when I get
> started on it; for now this is a placeholder issue for future work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
