Re: buildout.coredev - docs

I think there are some SEO advantages to placing stuff under one domain.
plone.org/documentation might be better as the canonical version.

Anthony


On 3 March 2014 13:40, sven <[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 03/03/2014 01:20 PM, Alex Clark wrote:
> > On 3/3/14, 3:15 AM, sven wrote:
> >> Hi,
> >>
> >> as some of you may already know, the docs team is busy with rearranging
> >> and bundling the documentation, during this process we would also like
> >> to move the docs of buildout.coredev away from RTD, include them into
> >> the new docs buildout and place them under the upcoming docs.plone.org.
> >>
> >> Would this be ok with everyone ?
> >
> >
> > +0, although at some point we may want to clean up all our offerings, we
> > currently have:
> >
> > - developer.plone.org
> > - dev.plone.org
> > - plone.org/documentation
> >
>
> We started already cleaning up and preparing at the last docs sprint and
> will continue on the upcoming sprint in Munich. All of these above will
> be go away, we only keep docs.plone.org and plone.org/documentation
> which will be one entry to all our docs.
> You will also be able to search in docs.plone.org via plone.org.
>
> > And if you add to that:
> >
> > - docs.plone.org
> >
> > Then we have 4 places where documentation happens (granted dev.plone.org
> > docs are minimal, and possibly outdated).
> >
> > Wherever you put them, we should link to them from here:
> > http://developer.plone.org/#manuals.
>
> > In an ideal world we'd have one place for documentation and a section
> > with coredev docs in it. developer.plone.org is the closest we currently
> > have to that.
>
> To explain it a bit, the idea is not to move it now, but start
> preparing, meaning when we decide to go official online with our new
> style/setup of documentation [release of plone5] you will find
> buildout.coredev docs under the umbrella of docs.plone.org
>
> Cheers,
>
> Sven
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTFIZBAAoJEMipVdWfKjFj5+0H/0yrADIANaVJD1BHUDz5rdVl
> vegxwT6DHdmxAWjETpZ068FGLQgD9SEbKZwRfrQZeoTL17zn+1Gh/NUkSNGAiaMZ
> zbFSg3Z7qxEMPbwoju/Q4zsLVA04t6rc9S5uGHbQ6H4DVzHVQJLe/EIVU8gb2udr
> lBBDTXW7g5DYNJ+Q3zcnt7NiqY5kY+tJ6k+EYNXF59KDy8WNPlNzGw/An6RyIJcB
> cBlAqL1l5BK0mCYRsGsGKCihTbtskJQ8c2asSdHHKjcn6Cx6x67QcudE584h1wpq
> B76+uimve4wLGgMv4O3fG6XWV76fAn97ikaoMvcyVJWuyYjUGxgHoalF7PkFE5s=
> =tIBN
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers