Open Stack

On Sat, 2020-03-14 at 09:36 -0400, Donny Davis wrote:
> On Fri, Mar 13, 2020 at 5:53 PM Jimmy McArthur <jimmy at openstack.org> wrote:
> 
> > 
> > Jeremy Stanley <fungi at yuggoth.org>
> > March 13, 2020 at 4:33 PM
> > On 2020-03-13 20:59:30 +0000 (+0000), Sean Mooney wrote:
> > [...]
> > 
> > Yep, this trips me up fairly often as well. The pattern of serving
> > multiple versions of documentation is a fairly widespread one, far
> > beyond just OpenStack circles, so maybe we should look at some other
> > examples and see if we can reverse engineer how they manage to
> > direct search results to their latest versions. For example, why do
> > searches for Python module names return results under
> > https://docs.python.org/3/ before they return results for
> > https://docs.python.org/3.5/ ? I briefly skimmed the page sources
> > for some examples but nothing jumped out at me, nor did the site's
> > robots.txt provide any insight. Perhaps SEO specialists know what
> > trick is at play there?
> > 
> > I will add it to my list of questions.  Normally you'd do it with
> > redirects to the latest, but that doesn't help if you're trying to keep
> > archived documentation.
> > 
> > Sean Mooney <smooney at redhat.com>
> > March 13, 2020 at 3:59 PM
> > 
> > On Fri, 2020-03-13 at 15:46 -0500, Jimmy McArthur wrote:
> > 
> > Sorry - I accidentally left Zuul keywords and examples in there. Fixed
> > below:
> > 
> > 
> > Jimmy McArthur <mailto:jimmy at openstack.org> <jimmy at openstack.org>
> > March 13, 2020 at 3:27 PM
> > Hi all -
> > 
> > We've contracted a professional SEO firm to help improve search
> > placement for all OSF projects.  I'd like to crowd source this on each
> > of the project mailing lists, so the community is able to be
> > involved.  Could you all help out in providing the below:
> > 
> > “Wish List” of keywords: 8-12 big terms you think fit your domain (if
> > you only have 4-5 to share, fewer is okay)
> > - open infrastructure
> > - ?
> > 
> > At least 3 competitors
> > - AWS
> > - ?
> > 
> > Any other input on positioning, offerings, etc. that you think will
> > help best filter for relevance
> > - ?
> > 
> > honestly the only think i would like to see is fixing the search result so that the 'latest' version of all our doc
> > are at the top of the list instead of pike.
> > the docs for our older release always come up first and its hard fo fine the direct link to the 'latest' version
> > which
> > tracks master.
> > 
> > granted i have it save in my broswer history but when users are looking for docs on things it would be nice if they
> > got
> > the more recent docs.
> > 
> > Cheers,
> > Jimmy
> > 
> > 
> > Jimmy McArthur <jimmy at openstack.org>
> > March 13, 2020 at 3:46 PM
> > Sorry - I accidentally left Zuul keywords and examples in there. Fixed
> > below:
> > 
> > 
> > Jimmy McArthur <jimmy at openstack.org>
> > March 13, 2020 at 3:27 PM
> > Hi all -
> > 
> > We've contracted a professional SEO firm to help improve search placement
> > for all OSF projects.  I'd like to crowd source this on each of the project
> > mailing lists, so the community is able to be involved.  Could you all help
> > out in providing the below:
> > 
> > “Wish List” of keywords: 8-12 big terms you think fit your domain (if you
> > only have 4-5 to share, fewer is okay)
> > - open source ci
> > - ?
> > 
> > At least 3 competitors
> > - Jenkins
> > - ?
> > 
> > Any other input on positioning, offerings, etc. that you think will help
> > best filter for relevance
> > - ?
> > 
> > Cheers,
> > Jimmy
> > 
> > 
> > 
> 
> It would be really great if when you click the current release is X button
> at the top of the page it would reload the same doc and just replace the
> release instead of directing you back to the home page of the doc release.
yes althought that is not a SEO thing i think we need to change how that baner is create but
i basically always ignore it because it does not do what i want so removing it entirly or more
helpflly making it link to the latest verion of the current doc would both be greate improvemnts.
> [image: image.png]