You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by Steve Loughran <st...@hortonworks.com> on 2014/05/06 20:04:12 UTC

updated site docs

I've just checked in updated source for the site, including
 -index on the left points to less but more useful items
 -home page better
 -slider specs integrated into site: referenced and cross-referencing other
bits of the app. It's no longer standalone, but copy and paste of things
like the CLI docs wasn't sustainable.

Now, what do I do to publish this?

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: updated site docs

Posted by Billie Rinaldi <bi...@gmail.com>.
On Tue, May 6, 2014 at 12:58 PM, Jon Maron <jm...@hortonworks.com> wrote:

>
> On May 6, 2014, at 2:04 PM, Steve Loughran <st...@hortonworks.com> wrote:
>
> > I've just checked in updated source for the site, including
> > -index on the left points to less but more useful items
> > -home page better
> > -slider specs integrated into site: referenced and cross-referencing
> other
> > bits of the app. It's no longer standalone, but copy and paste of things
> > like the CLI docs wasn't sustainable.
> >
> > Now, what do I do to publish this?
>
> Good question!  I’ve been perusing the docs, and since this is new to me,
> and the docs kind of suck, this is what I’ve gathered:
>
> - Ugly, manual way - if you can have the generated HTML end up in
> http://svn.apache.org/repos/asf/incubator/slider/site/content/ and
> checked in the site would go live.  Of course, that implies a manual
> process of regenerating and checking in modifications
>
> - CMS way - if he markdown files end up in
> http://svn.apache.org/repos/asf/incubator/slider/site/content/ (in a
> markdown subdirectory), if there is a site.xml file in “content”, if there
> is a pom.xml with the site plugin in
> http://svn.apache.org/repos/asf/incubator/slider/site/, if the
> “resources” dir is made a child of the “content” dir, the CMS will
> supposedly take care of regeneration upon an update.  As far as I can make
> out, this requires a JIRA to have the CMS configured to an external build
> mechanism (in this case, maven), but this is where it gets fuzzy for me...
>

I think if we want to go the CMS route, we might have to put in an
additional INFRA ticket.  (Slider doesn't show up on the list at
https://cms.apache.org/ yet.)


>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Re: updated site docs

Posted by Jon Maron <jm...@hortonworks.com>.
On May 6, 2014, at 2:04 PM, Steve Loughran <st...@hortonworks.com> wrote:

> I've just checked in updated source for the site, including
> -index on the left points to less but more useful items
> -home page better
> -slider specs integrated into site: referenced and cross-referencing other
> bits of the app. It's no longer standalone, but copy and paste of things
> like the CLI docs wasn't sustainable.
> 
> Now, what do I do to publish this?

Good question!  I’ve been perusing the docs, and since this is new to me, and the docs kind of suck, this is what I’ve gathered:

- Ugly, manual way - if you can have the generated HTML end up in http://svn.apache.org/repos/asf/incubator/slider/site/content/ and checked in the site would go live.  Of course, that implies a manual process of regenerating and checking in modifications

- CMS way - if he markdown files end up in http://svn.apache.org/repos/asf/incubator/slider/site/content/ (in a markdown subdirectory), if there is a site.xml file in “content”, if there is a pom.xml with the site plugin in http://svn.apache.org/repos/asf/incubator/slider/site/, if the “resources” dir is made a child of the “content” dir, the CMS will supposedly take care of regeneration upon an update.  As far as I can make out, this requires a JIRA to have the CMS configured to an external build mechanism (in this case, maven), but this is where it gets fuzzy for me...

> 
> -- 
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to 
> which it is addressed and may contain information that is confidential, 
> privileged and exempt from disclosure under applicable law. If the reader 
> of this message is not the intended recipient, you are hereby notified that 
> any printing, copying, dissemination, distribution, disclosure or 
> forwarding of this communication is strictly prohibited. If you have 
> received this communication in error, please contact the sender immediately 
> and delete it from your system. Thank You.


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.