I assume no objections and I can switch the branch.
2014-02-09 22:21 GMT+01:00 Lukasz Lenart :
> Ok, done! All pages migrated, outdated removed, etc.
>
> http://people.apache.org/~lukaszlenart/
>
> To build site locally (install Jekyll first):
> - svn co http://svn.apache.org/repos/asf/struts/site
Ok, done! All pages migrated, outdated removed, etc.
http://people.apache.org/~lukaszlenart/
To build site locally (install Jekyll first):
- svn co http://svn.apache.org/repos/asf/struts/site/branches/jekyll-powered/
struts-site
- cd struts-site
- jekyll serve
- open http://localhost:4000/
If no
First draft :-)
http://people.apache.org/~lukaszlenart/
Jekyll, jQuery 1.11.0, Bootstrap 3.1
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014-02-08 10:35 GMT+01:00 Lukasz Lenart :
> Another thing - I have started site migration to Jekyll on dedicated branch
>
> http://svn.apa
Another thing - I have started site migration to Jekyll on dedicated branch
http://svn.apache.org/repos/asf/struts/site/branches/jekyll-powered/
2014-01-22 11:35 GMT+01:00 Lukasz Lenart :
> I have started updating the site, right now moved the whole /dev to
> Markdown and moved files to root fold
I have started updating the site, right now moved the whole /dev to
Markdown and moved files to root folder. Please check if everything is
ok - WIP!
http://struts.staging.apache.org/
2014/1/21 Lukasz Lenart :
> I don't see objections so I think we can start with that :-)
>
> 2014/1/9 Lukasz Lenar
I don't see objections so I think we can start with that :-)
2014/1/9 Lukasz Lenart :
> Infra doesn't have time to answer my questions [1] and it's a bit
> annoying to wait with everything for them. So to not be dependent on
> Infra I think we should move / create a user guide under website and
>
Infra doesn't have time to answer my questions [1] and it's a bit
annoying to wait with everything for them. So to not be dependent on
Infra I think we should move / create a user guide under website and
left Confluence / Wiki as a reference with more detailed informations.
Then the release process
Years in the making. WOW! The Wiki documentation finally looks readable!
On Mon, Dec 16, 2013 at 3:33 PM, Lukasz Lenart wrote:
> I have removed custom css, the space looks better now :-)
>
> https://cwiki.apache.org/confluence/display/WW/Home
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http:/
I have removed custom css, the space looks better now :-)
https://cwiki.apache.org/confluence/display/WW/Home
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/12/16 Lukasz Lenart :
> FYI
>
> Confluence was upgraded to version 5 and there are some problems with
> editing pages.
FYI
Confluence was upgraded to version 5 and there are some problems with
editing pages.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/12/11 Lukasz Lenart :
> One more thing: everything editable will be moved to struts-site (i.e.
> the new plugin.md) to don't mess with thin
One more thing: everything editable will be moved to struts-site (i.e.
the new plugin.md) to don't mess with things generated by Maven
So the project source code will contain only source code and JavaDocs,
the rest will be outside it.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Sounds good to me. The easier the better.
On Wed, Dec 11, 2013 at 2:06 AM, Lukasz Lenart wrote:
> Still thinking how to organise everything, maybe instead common
> /release/2.3.x and so on it'd be better to have something like that:
>
> /docs/latest -> latest development version
> /docs/2.3.x
>
Still thinking how to organise everything, maybe instead common
/release/2.3.x and so on it'd be better to have something like that:
/docs/latest -> latest development version
/docs/2.3.x
/docs/2.2.x
...
and
/apidocs/latest -> the same as above
/apidocs/2.3.x
/apidocs/2.2.x
...
there be no more
Starting work on that - it must be resolved before next release comes out.
My plan is to have two tasks:
1. it will export pages from Confluence and will put them under /docs
2. used after release to update JavaDocs (regenerate from tag) and
Docs (copy from /docs to /release/2.3.x/docs)
WDYT?
ht
2013/11/5 Paul Benedict :
> I usually find it a life-saver to see the docs of previous versions. Not
> everyone upgrades and it's impossible to compare latest syntax and features
> to what was before. I think we definitely need to keep the docs of the
> previously published versions around.
But yo
rt.org.pl/
> >
> > 2013/9/10 :
> >> +1 for that
> >> It will reduce a lot of confusion
> >> --Original Message--
> >> From: Lukasz Lenart
> >> To: Struts Developers List
> >> ReplyTo: Struts Developers List
> >> Subject: Re-
:\
> >
> > ech... bit messy solution, but I don't see other option.
> >
> >
> > Regards
> > --
> > Łukasz
> > + 48 606 323 122 http://www.lenart.org.pl/
> >
> > 2013/9/10 :
> >> +1 for that
> >> It will reduce a lot of confusio
confusion
>> --Original Message--
>> From: Lukasz Lenart
>> To: Struts Developers List
>> ReplyTo: Struts Developers List
>> Subject: Re-organise docs
>> Sent: Sep 10, 2013 12:18 PM
>>
>> Hi,
>>
>> I thought a bit about our docs - fo
lyTo: Struts Developers List
> Subject: Re-organise docs
> Sent: Sep 10, 2013 12:18 PM
>
> Hi,
>
> I thought a bit about our docs - for each main branch we provide docs,
> i.e. /release/2.3.x/, /release/2.2.x/ etc. We also expose draft docs
> as /development/2.x - all thus lead
+1 for that
It will reduce a lot of confusion
--Original Message--
From: Lukasz Lenart
To: Struts Developers List
ReplyTo: Struts Developers List
Subject: Re-organise docs
Sent: Sep 10, 2013 12:18 PM
Hi,
I thought a bit about our docs - for each main branch we provide docs,
i.e
Hi,
I thought a bit about our docs - for each main branch we provide docs,
i.e. /release/2.3.x/, /release/2.2.x/ etc. We also expose draft docs
as /development/2.x - all thus leads to mess when we must update
something or so.
So maybe just instead of many places with docs we should expose the
lat
21 matches
Mail list logo
