Hi,

I'm finished migrating the html to markdown. the current sources for
the site are now markdown files [0].
They generate the html and the site-deploy submits them to [1]. Please
note, that the jackrabbit documentation is (still) in the 'jcr'
subdirectory. I did this to avoid the lengthy checkout that the
scm-publish plugin would do otherwise.

also see the readme at [2]

regards, toby

[0] https://svn.apache.org/repos/asf/jackrabbit/site/trunk/src/site/markdown/
[1] https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr/
[2] https://svn.apache.org/repos/asf/jackrabbit/site/trunk/README.md


On Tue, Apr 7, 2015 at 9:38 AM, Tobias Bocanegra <[email protected]> wrote:
>
>
> On Tue, Apr 7, 2015 at 2:50 AM, Davide Giannella <[email protected]> wrote:
>>
>> On 06/04/2015 07:08, Tobias Bocanegra wrote:
>> > Hi,
>> >
>> > I converted most of the site [0]. I'm not quite finished with the
>> > final structure, but at least it gives a usable result.
>> >
>> > to build:
>> > 1. svn co https://svn.apache.org/repos/asf/jackrabbit/site/trunk
>> > 2. mvn clean site
>> > 3. open target/site/index.html
>> >
>> > if you think this is ok, I'll push it to the live site.
>> >
>> > btw: as you might realize, the "code" now lives in
>> > jackrabbit/site/trunk, rather than jackrabbit/trunk/jackrabbit-site.
>> > should we keep it like this? I think yes, since the overall site does
>> > not really need to be included in the releases. however, the
>> > jackrabbit-1.x specific stuff, like the components description should
>> > go to trunk. and the ocm to ocm.
>> >
>> Thanks Toby.
>>
>> As I just released Oak 1.1.8 I updated both site-live, which seams to be
>> still the live website, and site-trunk for the news part.
>>
>> http://svn.apache.org/viewvc?view=revision&revision=r1671776
>
>
> great.
>>
>>
>>
>> One thing that came in my head. As both Oak and JR will be using the
>> markdown and site-deploy approach, let's make sure that when deploying
>> the JR website it won't wipe out the ./oak part of it. :)
>
>
> yes. there is also other stuff there, like the DTDs and APIs that I don't
> want to re-push every time.
> regards, toby
>
>>
>>
>> Cheers
>> Davide
>>
>>
>

Reply via email to