You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Aristedes Maniatis <am...@apache.org> on 2012/10/17 06:51:06 UTC

Website CMS

Dima

I think you were the last person working on the Apache CMS migration (no docbook, but the main site migration). Can you give us a summary of where you got up to? What is left to be done?

Cheers
Ari



-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 17, 2012, at 11:22 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> 2. Figure how to implement blog-posts (news)

I wouldn't mind if we post those via the new CMS (or even externally), and manually create summaries on the home page.

Andrus

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Thanks! we did it!

It feels good to be in control again :)

On Nov 8, 2012, at 12:33 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> On 8/11/12 8:26pm, Aristedes Maniatis wrote:
>> On 8/11/12 7:28pm, Andrus Adamchik wrote:
>>> BTW the site seems to be in process of publishing now:http://cayenne.apache.org/  hopefully will be up shortly.
>> 
>> Daniel from infra is trying to solve this now.
> 
> And now fixed. The site is publishing as we speak.
> 
> 
> Ari
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 8/11/12 8:26pm, Aristedes Maniatis wrote:
> On 8/11/12 7:28pm, Andrus Adamchik wrote:
>> BTW the site seems to be in process of publishing now:http://cayenne.apache.org/  hopefully will be up shortly.
>
> Daniel from infra is trying to solve this now.

And now fixed. The site is publishing as we speak.


Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 8/11/12 7:28pm, Andrus Adamchik wrote:
> BTW the site seems to be in process of publishing now:http://cayenne.apache.org/  hopefully will be up shortly.

Daniel from infra is trying to solve this now.

Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Looks like we still need one more redirect though. 3.0 docs were served as /doc till now, so this has to go to /doc30… Hmm… I might change the new /doc/ to /docs/ then to avoid redirect confusion.

BTW the site seems to be in process of publishing now: http://cayenne.apache.org/ hopefully will be up shortly.

Andrus


On Nov 8, 2012, at 10:56 AM, Andrus Adamchik <an...@objectstyle.org> wrote:

> On Nov 8, 2012, at 3:14 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>> Today loaded 3.1 javadocs and docbook HTML to the cms site. We have a total of 4 independent books in 3.1 (will probably refactor the whole docbook structure soon to make them easier to manipulate). Manually copying the folders wasn't too bad. The worst part was "git svn dcommit" after a Javadocs dump. But never the less it worked.
>>> 
>>> Notice the new docs structure. I wanted the subfolders to logically follow dropdown menus, so instead of calling it /doc31/, I went with /doc/3_1/ :
>>> 
>>> http://cayenne.staging.apache.org/doc/3_1/index.html
>> 
>> Not sure how changing the path syntax helps. If you really want to do that we'll need redirects from all the old simpler URLs to the new structure.
>> Remember that people will end up in doc pages from a google search and may just change the URL to go to a different version.
> 
> I didn't touch 1.2, 2.0, 3.0 layout. So no need for redirects. I strongly support the notion that we shouldn't be changing the existing well-publicized URLs without a cause. And if we do, always provide a 301 redirect (see "content/.htaccess"). But this is not the case here. 
> 
> The new scheme starts with 3.1 release. Among other things the new CMS freed us from the directory and file naming imposed by Confluence Autoexport, so I figured the URLs might follow the menu hierarchy for the docs. Also "unflattening" the top directory structure seems like a good thing for our own sanity.
> 
>> I also suggest a redirect
>> 
>> /doc/latest/  -->  /doc/3.1/
>> 
>> That makes it easier to refer people to the docs and for the links in mailing list archives to remain pointing to the current docs.
> 
> I've been thinking about this for some time. A "latest" symlink is both good and bad. The positive is that it creates a perception of a single set of docs. The negative is that we do have multiple versions of the docs after all and it is not always clear what "latest" means on any given day and associating "latest" with this moving target is not always such a clear cut. As Cayenne accumulates more major releases, I feel like using explicit versioning everywhere will save us and users from more trouble.
> 
> Taking your example, links in mailing list archives would actually work better with no "latest" symlink. Consider that some docs go away occasionally (e.g. dataviews are no longer in Cayenne, jpa, etc.). So this example seems to validate the version-aware URL approach.
> 
>>> Ari, any word on publishing our staging to the live site?
>> 
>> Yes, spoke to infra and created a ticket a few days ago. It is on their list.
> 
> Awesome.
> 
> Andrus
> 


Re: Website doc path renaming

Posted by Andrus Adamchik <an...@objectstyle.org>.
Sure. I'll rename 3_1 to 3.1. Makes sense.

Regarding older docs… Let me play with .htaccess. I think we can move those too. 

Again, now that we have possibilities not available when we used Confluence, organizing everything the way it "should" be is certainly a good idea.

Andrus


On Nov 8, 2012, at 12:37 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> On 8/11/12 6:56pm, Andrus Adamchik wrote:
>> I didn't touch 1.2, 2.0, 3.0 layout. So no need for redirects. I strongly support the notion that we shouldn't be changing the existing well-publicized URLs without a cause. And if we do, always provide a 301 redirect (see "content/.htaccess"). But this is not the case here.
>> 
>> The new scheme starts with 3.1 release. Among other things the new CMS freed us from the directory and file naming imposed by Confluence Autoexport, so I figured the URLs might follow the menu hierarchy for the docs. Also "unflattening" the top directory structure seems like a good thing for our own sanity.
> 
> Personally I don't know it is more sane (although I hate underscores). But I think we *want* consistency. That is, if I'm looking at
> 
>   http://cayenne.apache.org/doc/3.0/something
> 
> I'd like to be able to change the url to
> 
>  http://cayenne.apache.org/doc/2.0/something
> 
> and have it work.
> 
> 
> 
> Ari
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Website doc path renaming

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 8/11/12 6:56pm, Andrus Adamchik wrote:
> I didn't touch 1.2, 2.0, 3.0 layout. So no need for redirects. I strongly support the notion that we shouldn't be changing the existing well-publicized URLs without a cause. And if we do, always provide a 301 redirect (see "content/.htaccess"). But this is not the case here.
>
> The new scheme starts with 3.1 release. Among other things the new CMS freed us from the directory and file naming imposed by Confluence Autoexport, so I figured the URLs might follow the menu hierarchy for the docs. Also "unflattening" the top directory structure seems like a good thing for our own sanity.

Personally I don't know it is more sane (although I hate underscores). But I think we *want* consistency. That is, if I'm looking at

    http://cayenne.apache.org/doc/3.0/something

I'd like to be able to change the url to

   http://cayenne.apache.org/doc/2.0/something

and have it work.



Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Nov 8, 2012, at 3:14 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>> Today loaded 3.1 javadocs and docbook HTML to the cms site. We have a total of 4 independent books in 3.1 (will probably refactor the whole docbook structure soon to make them easier to manipulate). Manually copying the folders wasn't too bad. The worst part was "git svn dcommit" after a Javadocs dump. But never the less it worked.
>> 
>> Notice the new docs structure. I wanted the subfolders to logically follow dropdown menus, so instead of calling it /doc31/, I went with /doc/3_1/ :
>> 
>> http://cayenne.staging.apache.org/doc/3_1/index.html
> 
> Not sure how changing the path syntax helps. If you really want to do that we'll need redirects from all the old simpler URLs to the new structure.
> Remember that people will end up in doc pages from a google search and may just change the URL to go to a different version.

I didn't touch 1.2, 2.0, 3.0 layout. So no need for redirects. I strongly support the notion that we shouldn't be changing the existing well-publicized URLs without a cause. And if we do, always provide a 301 redirect (see "content/.htaccess"). But this is not the case here. 

The new scheme starts with 3.1 release. Among other things the new CMS freed us from the directory and file naming imposed by Confluence Autoexport, so I figured the URLs might follow the menu hierarchy for the docs. Also "unflattening" the top directory structure seems like a good thing for our own sanity.

> I also suggest a redirect
> 
> /doc/latest/  -->  /doc/3.1/
> 
> That makes it easier to refer people to the docs and for the links in mailing list archives to remain pointing to the current docs.

I've been thinking about this for some time. A "latest" symlink is both good and bad. The positive is that it creates a perception of a single set of docs. The negative is that we do have multiple versions of the docs after all and it is not always clear what "latest" means on any given day and associating "latest" with this moving target is not always such a clear cut. As Cayenne accumulates more major releases, I feel like using explicit versioning everywhere will save us and users from more trouble.

Taking your example, links in mailing list archives would actually work better with no "latest" symlink. Consider that some docs go away occasionally (e.g. dataviews are no longer in Cayenne, jpa, etc.). So this example seems to validate the version-aware URL approach.

>> Ari, any word on publishing our staging to the live site?
> 
> Yes, spoke to infra and created a ticket a few days ago. It is on their list.

Awesome.

Andrus

Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 8/11/12 6:33am, Andrus Adamchik wrote:
> Today loaded 3.1 javadocs and docbook HTML to the cms site. We have a total of 4 independent books in 3.1 (will probably refactor the whole docbook structure soon to make them easier to manipulate). Manually copying the folders wasn't too bad. The worst part was "git svn dcommit" after a Javadocs dump. But never the less it worked.
>
> Notice the new docs structure. I wanted the subfolders to logically follow dropdown menus, so instead of calling it /doc31/, I went with /doc/3_1/ :
>
> http://cayenne.staging.apache.org/doc/3_1/index.html

Not sure how changing the path syntax helps. If you really want to do that we'll need redirects from all the old simpler URLs to the new structure. Remember that people will end up in doc pages from a google search and may just change the URL to go to a different version.

I also suggest a redirect

/doc/latest/  -->  /doc/3.1/

That makes it easier to refer people to the docs and for the links in mailing list archives to remain pointing to the current docs.


> Kept the older folders unchanged though. Next I will go back to docbook HTML template work (and maybe the refactoring above).
>
> Ari, any word on publishing our staging to the live site?


Yes, spoke to infra and created a ticket a few days ago. It is on their list.


Ari



> Cheers,
> Andrus
>
>
> On Nov 5, 2012, at 11:44 AM, Andrus Adamchik <an...@objectstyle.org> wrote:
>> On Nov 5, 2012, at 11:25 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>
>>> 1. Hosting from the ci server isn't a good idea in the long term
>>> 2. The API and docbook are pointing to trunk and this is now for 3.1
>>>
>>> However, I don't think that the differences between trunk and 3.1 are important yet and certainly we are a long way before we need to branch docbook.
>>
>> Cool. I think we need to start publishing javadoc artifacts to Maven central with releases (which is prolly a good idea regardless, as it would improve IDE integration). Then Javadocs publish procedure will be like
>>
>> * get cayenne-server-XX-javadoc.jar from Maven
>> * unpack it into site/
>> * commit
>>
>> I may do that manually for the relevant releases.
>>
>>> I'm discussing some ideas with infra about how we might be publishing trunk realtime docbook builds. As you point out, we may never need nightly javadoc published on the website.
>>>
>>>
>>> I'll ask infra now to put our site live, unless anyone has any final words.
>>
>> Let's do it!
>>
>>> I've now disabled all my scripts which previously published javadocs and confluence. I have also now disabled public read access, and committer read-write access to the CAYSITE confluence space. It appears that the CAYDOC, CAYDOC12, CAYDOC20, etc space are already all gone.
>>
>> Also we need infra help to delete CAY/, CAYDOC/, CAYDOC12/, CAYDOC20/, CAYDOC30/, CAYDV/, CAYJPA/ CAYSITE/ folders from https://cwiki.apache.org/
>>
>> Or do they autoexport everything, regardless of the space purpose? In this case we still need their help to delete autoexports of the previously deleted spaces: CAYDOC/, CAYDOC12/, CAYDOC20/, CAYDOC30/ (and CAYSITE/ once we delete that one as well).
>>
>> Andrus
>>
>>
>

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Today loaded 3.1 javadocs and docbook HTML to the cms site. We have a total of 4 independent books in 3.1 (will probably refactor the whole docbook structure soon to make them easier to manipulate). Manually copying the folders wasn't too bad. The worst part was "git svn dcommit" after a Javadocs dump. But never the less it worked. 

Notice the new docs structure. I wanted the subfolders to logically follow dropdown menus, so instead of calling it /doc31/, I went with /doc/3_1/ :

http://cayenne.staging.apache.org/doc/3_1/index.html

Kept the older folders unchanged though. Next I will go back to docbook HTML template work (and maybe the refactoring above). 

Ari, any word on publishing our staging to the live site?

Cheers,
Andrus


On Nov 5, 2012, at 11:44 AM, Andrus Adamchik <an...@objectstyle.org> wrote:
> On Nov 5, 2012, at 11:25 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> 
>> 1. Hosting from the ci server isn't a good idea in the long term
>> 2. The API and docbook are pointing to trunk and this is now for 3.1
>> 
>> However, I don't think that the differences between trunk and 3.1 are important yet and certainly we are a long way before we need to branch docbook.
> 
> Cool. I think we need to start publishing javadoc artifacts to Maven central with releases (which is prolly a good idea regardless, as it would improve IDE integration). Then Javadocs publish procedure will be like 
> 
> * get cayenne-server-XX-javadoc.jar from Maven 
> * unpack it into site/ 
> * commit
> 
> I may do that manually for the relevant releases.
> 
>> I'm discussing some ideas with infra about how we might be publishing trunk realtime docbook builds. As you point out, we may never need nightly javadoc published on the website.
>> 
>> 
>> I'll ask infra now to put our site live, unless anyone has any final words.
> 
> Let's do it!
> 
>> I've now disabled all my scripts which previously published javadocs and confluence. I have also now disabled public read access, and committer read-write access to the CAYSITE confluence space. It appears that the CAYDOC, CAYDOC12, CAYDOC20, etc space are already all gone.
> 
> Also we need infra help to delete CAY/, CAYDOC/, CAYDOC12/, CAYDOC20/, CAYDOC30/, CAYDV/, CAYJPA/ CAYSITE/ folders from https://cwiki.apache.org/ 
> 
> Or do they autoexport everything, regardless of the space purpose? In this case we still need their help to delete autoexports of the previously deleted spaces: CAYDOC/, CAYDOC12/, CAYDOC20/, CAYDOC30/ (and CAYSITE/ once we delete that one as well).
> 
> Andrus
> 
> 


Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Nov 5, 2012, at 11:25 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> 1. Hosting from the ci server isn't a good idea in the long term
> 2. The API and docbook are pointing to trunk and this is now for 3.1
> 
> However, I don't think that the differences between trunk and 3.1 are important yet and certainly we are a long way before we need to branch docbook.

Cool. I think we need to start publishing javadoc artifacts to Maven central with releases (which is prolly a good idea regardless, as it would improve IDE integration). Then Javadocs publish procedure will be like 

* get cayenne-server-XX-javadoc.jar from Maven 
* unpack it into site/ 
* commit

I may do that manually for the relevant releases.

> I'm discussing some ideas with infra about how we might be publishing trunk realtime docbook builds. As you point out, we may never need nightly javadoc published on the website.
> 
> 
> I'll ask infra now to put our site live, unless anyone has any final words.

Let's do it!

> I've now disabled all my scripts which previously published javadocs and confluence. I have also now disabled public read access, and committer read-write access to the CAYSITE confluence space. It appears that the CAYDOC, CAYDOC12, CAYDOC20, etc space are already all gone.

Also we need infra help to delete CAY/, CAYDOC/, CAYDOC12/, CAYDOC20/, CAYDOC30/, CAYDV/, CAYJPA/ CAYSITE/ folders from https://cwiki.apache.org/ 

Or do they autoexport everything, regardless of the space purpose? In this case we still need their help to delete autoexports of the previously deleted spaces: CAYDOC/, CAYDOC12/, CAYDOC20/, CAYDOC30/ (and CAYSITE/ once we delete that one as well).

Andrus


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 5/11/12 5:09pm, Andrus Adamchik wrote:
> At the same time I think it is in a shape good enough to be published as "master" 3.1 (and 3.2) documentation set on the site, while I am slowly rewriting the remaining chapters. It should be much more useful to 3.1 users then just cloning the old 3.0 wiki docs (which is what we essentially have on the current site). And publishing would require HTML (and PDF) templates cleanup.

OK, then I've just added more links on the left to the docbook and java api. This is temporary since:

1. Hosting from the ci server isn't a good idea in the long term
2. The API and docbook are pointing to trunk and this is now for 3.1

However, I don't think that the differences between trunk and 3.1 are important yet and certainly we are a long way before we need to branch docbook.

I'm discussing some ideas with infra about how we might be publishing trunk realtime docbook builds. As you point out, we may never need nightly javadoc published on the website.


I'll ask infra now to put our site live, unless anyone has any final words. I've now disabled all my scripts which previously published javadocs and confluence. I have also now disabled public read access, and committer read-write access to the CAYSITE confluence space. It appears that the CAYDOC, CAYDOC12, CAYDOC20, etc space are already all gone.



Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Nov 5, 2012, at 2:14 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

>> I also have a post launch cleanup list that will require their involvement:
>> 
>> * stop cwiki.a.o rsync (you control this one IIRC?)
>> * delete all autoexported files on cwiki.a.o (infra)
>> * track down unlinked files in docroot, delete them, creating 301 redirects where applicable. (me or any other Cayenne committer)
> 
> Actually I suspect I can just ask Infra to discard our entire website folder and replace it with the Apache CMS folder. So we should look for 'unlinked' pages now. Personally I can't think of any, and we could review Google webmaster tools after the change to see what pages people link to that are gone. I'll set that up now…

That'll work.


>>> I think the next focus needs to be on getting docbook finished so we can add 3.1 to the left menu. I'm happy to help copy in existing documentation, but Andrus, you said that you wanted to restructure the docs for this project. Perhaps you want to work on it, or outline what you had in mind?
>> 
>> Yep. I can create a more site-centric HTML template for docbook and do a manual initial docs dump from the main SVN tree into the "site" and adding needed menus. Once that's live, we can work on improving CSS, etc.
> 
> Are we talking about the same thing? I'm not talking about the html template so much as the content of the docbook itself. It is currently missing lots of content from Confluence and in the past you said that you did not want to just copy it over but to rearrange it into more helpful structures. Moving stuff into docbook takes a bit of effort, so any structure changes should be done first.

Yes, the new docbook stuff is about rearranging and a substantial rewrite of the wiki docs. It is still unfinished, and I'd rather we do not just move the old wikidocs to it. That would defeat the purpose of the "modernizing" effort done so far.

At the same time I think it is in a shape good enough to be published as "master" 3.1 (and 3.2) documentation set on the site, while I am slowly rewriting the remaining chapters. It should be much more useful to 3.1 users then just cloning the old 3.0 wiki docs (which is what we essentially have on the current site). And publishing would require HTML (and PDF) templates cleanup. 

Andrus

Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 4/11/12 11:08pm, Andrus Adamchik wrote:
>
> On Nov 4, 2012, at 2:58 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
>> Nicely done polishing off those last remaining tasks... My look around the site reveals nothing that needs to be fixed before launch, so let's do it. I think infra will need to be involved to switch the website over from the current synchronisation feed to Apache CMS.
>
> Cool. You are in touch with the infra guys. Could you Jira it for them (or ask on irc)?

Sure.


> I also have a post launch cleanup list that will require their involvement:
>
> * stop cwiki.a.o rsync (you control this one IIRC?)
> * delete all autoexported files on cwiki.a.o (infra)
> * track down unlinked files in docroot, delete them, creating 301 redirects where applicable. (me or any other Cayenne committer)

Actually I suspect I can just ask Infra to discard our entire website folder and replace it with the Apache CMS folder. So we should look for 'unlinked' pages now. Personally I can't think of any, and we could review Google webmaster tools after the change to see what pages people link to that are gone. I'll set that up now...

  
>> I think the next focus needs to be on getting docbook finished so we can add 3.1 to the left menu. I'm happy to help copy in existing documentation, but Andrus, you said that you wanted to restructure the docs for this project. Perhaps you want to work on it, or outline what you had in mind?
>
> Yep. I can create a more site-centric HTML template for docbook and do a manual initial docs dump from the main SVN tree into the "site" and adding needed menus. Once that's live, we can work on improving CSS, etc.

Are we talking about the same thing? I'm not talking about the html template so much as the content of the docbook itself. It is currently missing lots of content from Confluence and in the past you said that you did not want to just copy it over but to rearrange it into more helpful structures. Moving stuff into docbook takes a bit of effort, so any structure changes should be done first.


Ari




-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Nov 4, 2012, at 2:58 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> Nicely done polishing off those last remaining tasks... My look around the site reveals nothing that needs to be fixed before launch, so let's do it. I think infra will need to be involved to switch the website over from the current synchronisation feed to Apache CMS.

Cool. You are in touch with the infra guys. Could you Jira it for them (or ask on irc)? 

I also have a post launch cleanup list that will require their involvement:

* stop cwiki.a.o rsync (you control this one IIRC?)
* delete all autoexported files on cwiki.a.o (infra)
* track down unlinked files in docroot, delete them, creating 301 redirects where applicable. (me or any other Cayenne committer)

> I think the next focus needs to be on getting docbook finished so we can add 3.1 to the left menu. I'm happy to help copy in existing documentation, but Andrus, you said that you wanted to restructure the docs for this project. Perhaps you want to work on it, or outline what you had in mind?

Yep. I can create a more site-centric HTML template for docbook and do a manual initial docs dump from the main SVN tree into the "site" and adding needed menus. Once that's live, we can work on improving CSS, etc.

Andrus

Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
Nicely done polishing off those last remaining tasks... My look around the site reveals nothing that needs to be fixed before launch, so let's do it. I think infra will need to be involved to switch the website over from the current synchronisation feed to Apache CMS.

I think the next focus needs to be on getting docbook finished so we can add 3.1 to the left menu. I'm happy to help copy in existing documentation, but Andrus, you said that you wanted to restructure the docs for this project. Perhaps you want to work on it, or outline what you had in mind?


Ari


On 4/11/12 1:59am, Andrus Adamchik wrote:
> Ok. I think I am done and we are ready to replace the site.
>
> Last night I played with fancy way to include live feeds (ASF::Value::Blogs, ASF::Value::Twitter, etc.) Unfortunately this didn't work for me. I narrowed it down to third-party XML::Atom::Feed not returning any entries and left it at that for now.
>
> This morning I ported 2 years worth of blog posts to markdown (and even preserved the article URLs!), and simply linked to them from the home page. The whole process was very simple, and for our low rate of news, I don't mind keeping it as is.
>
> We may play with some RSS scanners in parallel without delaying the launch. For instance I would love to get a Twitter panel showing latest stuff from https://twitter.com/ApacheCayenne (a resource that is updated periodically), a commit feed, etc.
>
> Feel free to review and tweak the site at http://cayenne.staging.apache.org/ At some point next week I'd like to flip the switch on the old site and publish the new one.
>
> BTW, beside following this http://www.apache.org/dev/cmsref.html#publishing do we need any infra help to activate publishing?
>
> Andrus
>
>
> On Oct 31, 2012, at 11:50 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>
>> Tonight I fixed legacy docs wrappers and created small per-version menus for each piece of the docs. Also checked in a bunch of smaller things, like the Twitter button, doc titles with version in them, etc.
>>
>> News seems to be the only thing remaining before we can go live.
>>
>> Andrus
>>
>> On Oct 31, 2012, at 10:31 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>
>>> On 31/10/12 5:20pm, Andrus Adamchik wrote:
>>>> I'll take a look at porting the news. Don't think we need to port many past news.
>>>
>>> Some would be nice to give the project history.
>>>
>>>>> Why can't the third template extend skeleton?
>>>>
>>>> My thinking was that we don't need left hand menu for the docs. For instance looking at Docbook produced HTML I like how clean and distraction free it is. Wanted to keep that across the board for docs. I would imagine we'll just need a Cayenne header with a backlink to the main site, and a copyright/privacy policy footer. Anyways, I'll refactor the templates to maybe have a single skeleton and optional menu include. Will need to play with it a bit.
>>>
>>> Sure, that makes sense. Let me know when you are done and I'll play with the css a bit. It is a bit ugly right now.
>>>
>>>
>>> Ari
>>>
>>>
>>>
>>>> Andrus
>>>>
>>>>
>>>> On Oct 31, 2012, at 1:27 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>>>> On 31/10/12 7:24am, Andrus Adamchik wrote:
>>>>>
>>>>>> Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:
>>>>>>
>>>>>> http://cayenne.staging.apache.org/download.html
>>>>>> http://cayenne.staging.apache.org/doc30/api/index.html
>>>>>> http://cayenne.staging.apache.org/doc30/overview.html
>>>>>
>>>>> Why can't the third template extend skeleton? I tried to strip out the bits of the html from the Confluence export which were incompatible, leaving only (hopefully) compatible bits. Perhaps we can put back skeleton and tweak the css a little to cope?
>>>>>
>>>>> I think the next steps are just news and tying in the automated docbook/javadoc builds for trunk documentation.
>>>>>
>>>>> If we go down the Apache Blog approach for news, this is what we do:
>>>>>
>>>>> {% for e in blog.list %}
>>>>>      <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
>>>>>      <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
>>>>>      <hr>
>>>>>    {% endfor %}
>>>>>
>>>>> in our path.pm file:
>>>>>
>>>>> [ qr!^/index\.mdtext$!, news_page => {
>>>>>         blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
>>>>> } ],
>>>>>
>>>>>
>>>>> Pluses:
>>>>>
>>>>> * people can add comments to the posts
>>>>> * we get broader publicity on the main apache site as well with no extra effort
>>>>> * there is probably an rss feed
>>>>>
>>>>> Minuses:
>>>>>
>>>>> * I don't know if we can carry forward historical news, so we'd need to handle that separately
>>>>>
>>>>>
>>>>> Andrus, would you like to give this a try since you now have a local environment? I can then style up the news items. Later on if we get really clever it seems we might be able to have a feed on the side of recent Jira comments and svn commits. That would be nice to show the activity that happens behind the scenes.
>>>>>
>>>>>
>>>>> Ari
>>>>>
>>>>>
>>>>> --
>>>>> -------------------------->
>>>>> Aristedes Maniatis
>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>>>
>>>>
>>>
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>
>>
>>
>

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Ok. I think I am done and we are ready to replace the site.

Last night I played with fancy way to include live feeds (ASF::Value::Blogs, ASF::Value::Twitter, etc.) Unfortunately this didn't work for me. I narrowed it down to third-party XML::Atom::Feed not returning any entries and left it at that for now.

This morning I ported 2 years worth of blog posts to markdown (and even preserved the article URLs!), and simply linked to them from the home page. The whole process was very simple, and for our low rate of news, I don't mind keeping it as is.

We may play with some RSS scanners in parallel without delaying the launch. For instance I would love to get a Twitter panel showing latest stuff from https://twitter.com/ApacheCayenne (a resource that is updated periodically), a commit feed, etc.

Feel free to review and tweak the site at http://cayenne.staging.apache.org/ At some point next week I'd like to flip the switch on the old site and publish the new one. 

BTW, beside following this http://www.apache.org/dev/cmsref.html#publishing do we need any infra help to activate publishing?

Andrus


On Oct 31, 2012, at 11:50 PM, Andrus Adamchik <an...@objectstyle.org> wrote:

> Tonight I fixed legacy docs wrappers and created small per-version menus for each piece of the docs. Also checked in a bunch of smaller things, like the Twitter button, doc titles with version in them, etc.
> 
> News seems to be the only thing remaining before we can go live.
> 
> Andrus
> 
> On Oct 31, 2012, at 10:31 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> 
>> On 31/10/12 5:20pm, Andrus Adamchik wrote:
>>> I'll take a look at porting the news. Don't think we need to port many past news.
>> 
>> Some would be nice to give the project history.
>> 
>>>> Why can't the third template extend skeleton?
>>> 
>>> My thinking was that we don't need left hand menu for the docs. For instance looking at Docbook produced HTML I like how clean and distraction free it is. Wanted to keep that across the board for docs. I would imagine we'll just need a Cayenne header with a backlink to the main site, and a copyright/privacy policy footer. Anyways, I'll refactor the templates to maybe have a single skeleton and optional menu include. Will need to play with it a bit.
>> 
>> Sure, that makes sense. Let me know when you are done and I'll play with the css a bit. It is a bit ugly right now.
>> 
>> 
>> Ari
>> 
>> 
>> 
>>> Andrus
>>> 
>>> 
>>> On Oct 31, 2012, at 1:27 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>>> On 31/10/12 7:24am, Andrus Adamchik wrote:
>>>> 
>>>>> Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:
>>>>> 
>>>>> http://cayenne.staging.apache.org/download.html
>>>>> http://cayenne.staging.apache.org/doc30/api/index.html
>>>>> http://cayenne.staging.apache.org/doc30/overview.html
>>>> 
>>>> Why can't the third template extend skeleton? I tried to strip out the bits of the html from the Confluence export which were incompatible, leaving only (hopefully) compatible bits. Perhaps we can put back skeleton and tweak the css a little to cope?
>>>> 
>>>> I think the next steps are just news and tying in the automated docbook/javadoc builds for trunk documentation.
>>>> 
>>>> If we go down the Apache Blog approach for news, this is what we do:
>>>> 
>>>> {% for e in blog.list %}
>>>>     <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
>>>>     <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
>>>>     <hr>
>>>>   {% endfor %}
>>>> 
>>>> in our path.pm file:
>>>> 
>>>> [ qr!^/index\.mdtext$!, news_page => {
>>>>        blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
>>>> } ],
>>>> 
>>>> 
>>>> Pluses:
>>>> 
>>>> * people can add comments to the posts
>>>> * we get broader publicity on the main apache site as well with no extra effort
>>>> * there is probably an rss feed
>>>> 
>>>> Minuses:
>>>> 
>>>> * I don't know if we can carry forward historical news, so we'd need to handle that separately
>>>> 
>>>> 
>>>> Andrus, would you like to give this a try since you now have a local environment? I can then style up the news items. Later on if we get really clever it seems we might be able to have a feed on the side of recent Jira comments and svn commits. That would be nice to show the activity that happens behind the scenes.
>>>> 
>>>> 
>>>> Ari
>>>> 
>>>> 
>>>> --
>>>> -------------------------->
>>>> Aristedes Maniatis
>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>> 
>>> 
>> 
>> -- 
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>> 
> 
> 


Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Tonight I fixed legacy docs wrappers and created small per-version menus for each piece of the docs. Also checked in a bunch of smaller things, like the Twitter button, doc titles with version in them, etc.

News seems to be the only thing remaining before we can go live.

Andrus

On Oct 31, 2012, at 10:31 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> On 31/10/12 5:20pm, Andrus Adamchik wrote:
>> I'll take a look at porting the news. Don't think we need to port many past news.
> 
> Some would be nice to give the project history.
> 
>>> Why can't the third template extend skeleton?
>> 
>> My thinking was that we don't need left hand menu for the docs. For instance looking at Docbook produced HTML I like how clean and distraction free it is. Wanted to keep that across the board for docs. I would imagine we'll just need a Cayenne header with a backlink to the main site, and a copyright/privacy policy footer. Anyways, I'll refactor the templates to maybe have a single skeleton and optional menu include. Will need to play with it a bit.
> 
> Sure, that makes sense. Let me know when you are done and I'll play with the css a bit. It is a bit ugly right now.
> 
> 
> Ari
> 
> 
> 
>> Andrus
>> 
>> 
>> On Oct 31, 2012, at 1:27 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>> On 31/10/12 7:24am, Andrus Adamchik wrote:
>>> 
>>>> Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:
>>>> 
>>>> http://cayenne.staging.apache.org/download.html
>>>> http://cayenne.staging.apache.org/doc30/api/index.html
>>>> http://cayenne.staging.apache.org/doc30/overview.html
>>> 
>>> Why can't the third template extend skeleton? I tried to strip out the bits of the html from the Confluence export which were incompatible, leaving only (hopefully) compatible bits. Perhaps we can put back skeleton and tweak the css a little to cope?
>>> 
>>> I think the next steps are just news and tying in the automated docbook/javadoc builds for trunk documentation.
>>> 
>>> If we go down the Apache Blog approach for news, this is what we do:
>>> 
>>> {% for e in blog.list %}
>>>      <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
>>>      <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
>>>      <hr>
>>>    {% endfor %}
>>> 
>>> in our path.pm file:
>>> 
>>> [ qr!^/index\.mdtext$!, news_page => {
>>>         blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
>>> } ],
>>> 
>>> 
>>> Pluses:
>>> 
>>> * people can add comments to the posts
>>> * we get broader publicity on the main apache site as well with no extra effort
>>> * there is probably an rss feed
>>> 
>>> Minuses:
>>> 
>>> * I don't know if we can carry forward historical news, so we'd need to handle that separately
>>> 
>>> 
>>> Andrus, would you like to give this a try since you now have a local environment? I can then style up the news items. Later on if we get really clever it seems we might be able to have a feed on the side of recent Jira comments and svn commits. That would be nice to show the activity that happens behind the scenes.
>>> 
>>> 
>>> Ari
>>> 
>>> 
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>> 
>> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 31/10/12 5:20pm, Andrus Adamchik wrote:
> I'll take a look at porting the news. Don't think we need to port many past news.

Some would be nice to give the project history.

>> Why can't the third template extend skeleton?
>
> My thinking was that we don't need left hand menu for the docs. For instance looking at Docbook produced HTML I like how clean and distraction free it is. Wanted to keep that across the board for docs. I would imagine we'll just need a Cayenne header with a backlink to the main site, and a copyright/privacy policy footer. Anyways, I'll refactor the templates to maybe have a single skeleton and optional menu include. Will need to play with it a bit.

Sure, that makes sense. Let me know when you are done and I'll play with the css a bit. It is a bit ugly right now.


Ari



> Andrus
>
>
> On Oct 31, 2012, at 1:27 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>> On 31/10/12 7:24am, Andrus Adamchik wrote:
>>
>>> Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:
>>>
>>> http://cayenne.staging.apache.org/download.html
>>> http://cayenne.staging.apache.org/doc30/api/index.html
>>> http://cayenne.staging.apache.org/doc30/overview.html
>>
>> Why can't the third template extend skeleton? I tried to strip out the bits of the html from the Confluence export which were incompatible, leaving only (hopefully) compatible bits. Perhaps we can put back skeleton and tweak the css a little to cope?
>>
>> I think the next steps are just news and tying in the automated docbook/javadoc builds for trunk documentation.
>>
>> If we go down the Apache Blog approach for news, this is what we do:
>>
>> {% for e in blog.list %}
>>       <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
>>       <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
>>       <hr>
>>     {% endfor %}
>>
>> in our path.pm file:
>>
>> [ qr!^/index\.mdtext$!, news_page => {
>>          blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
>> } ],
>>
>>
>> Pluses:
>>
>> * people can add comments to the posts
>> * we get broader publicity on the main apache site as well with no extra effort
>> * there is probably an rss feed
>>
>> Minuses:
>>
>> * I don't know if we can carry forward historical news, so we'd need to handle that separately
>>
>>
>> Andrus, would you like to give this a try since you now have a local environment? I can then style up the news items. Later on if we get really clever it seems we might be able to have a feed on the side of recent Jira comments and svn commits. That would be nice to show the activity that happens behind the scenes.
>>
>>
>> Ari
>>
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>
>

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
I'll take a look at porting the news. Don't think we need to port many past news. 

> Why can't the third template extend skeleton? 

My thinking was that we don't need left hand menu for the docs. For instance looking at Docbook produced HTML I like how clean and distraction free it is. Wanted to keep that across the board for docs. I would imagine we'll just need a Cayenne header with a backlink to the main site, and a copyright/privacy policy footer. Anyways, I'll refactor the templates to maybe have a single skeleton and optional menu include. Will need to play with it a bit.

Andrus


On Oct 31, 2012, at 1:27 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> On 31/10/12 7:24am, Andrus Adamchik wrote:
> 
>> Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:
>> 
>> http://cayenne.staging.apache.org/download.html
>> http://cayenne.staging.apache.org/doc30/api/index.html
>> http://cayenne.staging.apache.org/doc30/overview.html
> 
> Why can't the third template extend skeleton? I tried to strip out the bits of the html from the Confluence export which were incompatible, leaving only (hopefully) compatible bits. Perhaps we can put back skeleton and tweak the css a little to cope?
> 
> I think the next steps are just news and tying in the automated docbook/javadoc builds for trunk documentation.
> 
> If we go down the Apache Blog approach for news, this is what we do:
> 
> {% for e in blog.list %}
>      <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
>      <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
>      <hr>
>    {% endfor %}
> 
> in our path.pm file:
> 
> [ qr!^/index\.mdtext$!, news_page => {
>         blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
> } ],
> 
> 
> Pluses:
> 
> * people can add comments to the posts
> * we get broader publicity on the main apache site as well with no extra effort
> * there is probably an rss feed
> 
> Minuses:
> 
> * I don't know if we can carry forward historical news, so we'd need to handle that separately
> 
> 
> Andrus, would you like to give this a try since you now have a local environment? I can then style up the news items. Later on if we get really clever it seems we might be able to have a feed on the side of recent Jira comments and svn commits. That would be nice to show the activity that happens behind the scenes.
> 
> 
> Ari
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 31/10/12 7:24am, Andrus Adamchik wrote:

> Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:
>
> http://cayenne.staging.apache.org/download.html
> http://cayenne.staging.apache.org/doc30/api/index.html
> http://cayenne.staging.apache.org/doc30/overview.html

Why can't the third template extend skeleton? I tried to strip out the bits of the html from the Confluence export which were incompatible, leaving only (hopefully) compatible bits. Perhaps we can put back skeleton and tweak the css a little to cope?

I think the next steps are just news and tying in the automated docbook/javadoc builds for trunk documentation.

If we go down the Apache Blog approach for news, this is what we do:

{% for e in blog.list %}
       <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
       <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
       <hr>
     {% endfor %}

in our path.pm file:

[ qr!^/index\.mdtext$!, news_page => {
          blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
} ],


Pluses:

* people can add comments to the posts
* we get broader publicity on the main apache site as well with no extra effort
* there is probably an rss feed

Minuses:

* I don't know if we can carry forward historical news, so we'd need to handle that separately


Andrus, would you like to give this a try since you now have a local environment? I can then style up the news items. Later on if we get really clever it seems we might be able to have a feed on the side of recent Jira comments and svn commits. That would be nice to show the activity that happens behind the scenes.


Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Finally I am getting hands on with the site build. After messing up and consequently restoring my OSX Perl installation, I could run "perl build_site.pl" for the first time… 

So.. I decided to classify our docroot as "markdown", "apidocs" and "legacy_confluence", giving each its own template:

our @patterns = (
  [qr!\.mdtext$!, single_narrative => { template => "markdown.html" }],
  [qr!^/doc[0-9]{0,2}/api/.*\.html$!, single_narrative => { template => "apidocs.html" }],
  [qr!^/doc[0-9]{0,2}/(?\!api/).*\.html$!, single_narrative => { template => "legacy_confluence.html" }],
) ;

Note that second and third templates do not extend skeleton template, as they are essentially incompatible. I just committed the changes, and here are the rendered examples:

http://cayenne.staging.apache.org/download.html
http://cayenne.staging.apache.org/doc30/api/index.html
http://cayenne.staging.apache.org/doc30/overview.html

Sure enough we need to tweak #3, and can do many other improvements. But I think we are very close to having a working site!  

I am impressed with how fast the publishing is, be it locally or on the server. Beats anything we've used to date. Anyways, I think I am done for today. We can address the remaining things tomorrow.

Andrus




On Oct 30, 2012, at 12:58 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> On 30/10/12 7:48pm, Andrus Adamchik wrote:
> 
>> I will try to find time to check the Perl stuff…
> 
> My last commit as an experiment seemed to break the Perl stuff. I'll try and muddle my way through unless you can see why it is broken.
> 
> Ari
> 
> 
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 30/10/12 7:48pm, Andrus Adamchik wrote:

> I will try to find time to check the Perl stuff…

My last commit as an experiment seemed to break the Perl stuff. I'll try and muddle my way through unless you can see why it is broken.

Ari




-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 30, 2012, at 11:39 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> On 29/10/12 7:48pm, Andrus Adamchik wrote:
> 
>> Yes, but is this even an issue? Most docs should not be published on each code commit, and should be deferred till we make an official release. Our releases are fairly formalized events with a documented scenario that a release manager follows. One of the steps in this scenario can be doc publishing.
> 
> Personally I rather see the documents as living things where fixes and improvements are continuously rolled out. Waiting 18 months to release doc fixes or improvements doesn't seem helpful.

We are talking about 2 complimentary scenarios here:

1. the docs (including Javadocs) that describe the code that is yet unreleased. 
2. the docs that describe things already released and available. 

I'd say we should wait 18 months (or whatever it takes to release the underlying code) with #1. And you are absolutely right about #2. So I guess we need publishing scenarios for both cases and then see how that maps to CI. 

I will try to find time to check the Perl stuff…

Andrus


On Oct 30, 2012, at 11:39 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> On 29/10/12 7:48pm, Andrus Adamchik wrote:
> 
>> Yes, but is this even an issue? Most docs should not be published on each code commit, and should be deferred till we make an official release. Our releases are fairly formalized events with a documented scenario that a release manager follows. One of the steps in this scenario can be doc publishing.
> 
> Personally I rather see the documents as living things where fixes and improvements are continuously rolled out. Waiting 18 months to release doc fixes or improvements doesn't seem helpful.
> 
> 
> I've now imported doc12/doc20/doc30 into our new CMS, ripped out the headers and footers in each file, and converted the Title into the same format as the other pages. I left out /doc for now until we understand whether we'll be able to get our docbook up to speed for 3.1.
> 
>   http://cayenne.staging.apache.org/doc30/overview.html
> 
> 
> The problem here is some Perl you might be able to help with. Look at path.pm, we probably need to add a line like:
> 
> 	[qr!\.html$!, single_narrative => { template => "single_narrative.html" }],
> 
> and then edit view.pm where you see
> 
>        sub single_narrative {
> 
> Ideally we'd disable Django processing ( http://search.cpan.org/~maluku/Dotiac-0.8/lib/Dotiac/DTL.pm ) but we still want it to parse the "Title" tag in the top of the page. I can't find which bit of code does that.
> 
> 
> 
> Next, for the docs inside the /api/ folder, we want to stop it adding any templating at all. I guess that's another path.pm entry.
> 
> 
> Some of this will be trial and error I think....
> 
> 
> I'm chatting to a Lucene guy about how they did their news on their home page. http://lucenenet.apache.org/ Seems simple enough but it means we'd move to the Apache Blog tool for all our news entries. It is pretty ugly:
> 
>   https://blogs.apache.org/lucenenet/entry/lucene_net_3_0_3
> 
> But it does allow comments which is nice.
> 
> 
> Ari
> 
> 
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 29/10/12 7:48pm, Andrus Adamchik wrote:

> Yes, but is this even an issue? Most docs should not be published on each code commit, and should be deferred till we make an official release. Our releases are fairly formalized events with a documented scenario that a release manager follows. One of the steps in this scenario can be doc publishing.

Personally I rather see the documents as living things where fixes and improvements are continuously rolled out. Waiting 18 months to release doc fixes or improvements doesn't seem helpful.


I've now imported doc12/doc20/doc30 into our new CMS, ripped out the headers and footers in each file, and converted the Title into the same format as the other pages. I left out /doc for now until we understand whether we'll be able to get our docbook up to speed for 3.1.

    http://cayenne.staging.apache.org/doc30/overview.html


The problem here is some Perl you might be able to help with. Look at path.pm, we probably need to add a line like:

	[qr!\.html$!, single_narrative => { template => "single_narrative.html" }],

and then edit view.pm where you see

         sub single_narrative {

Ideally we'd disable Django processing ( http://search.cpan.org/~maluku/Dotiac-0.8/lib/Dotiac/DTL.pm ) but we still want it to parse the "Title" tag in the top of the page. I can't find which bit of code does that.



Next, for the docs inside the /api/ folder, we want to stop it adding any templating at all. I guess that's another path.pm entry.


Some of this will be trial and error I think....


I'm chatting to a Lucene guy about how they did their news on their home page. http://lucenenet.apache.org/ Seems simple enough but it means we'd move to the Apache Blog tool for all our news entries. It is pretty ugly:

    https://blogs.apache.org/lucenenet/entry/lucene_net_3_0_3

But it does allow comments which is nice.


Ari




-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 29, 2012, at 11:02 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> OK, then we just have to get it finished before we release 3.1. Until then it can serve as partial documentation with an early focus on the new features. Sounds fair?

Yes. The plan is to finish it for 3.1-final [*], but include partial docs with betas and RCs as we go. I am actually hoping we are on the verge of RC1 now.


>> Another issue with doc publishing - should we be tying doc publishing to CI? All doc changes can be roughly split into two categories - those catching up with an existing release and those corresponding to the yet unreleased code. Especially the Javadocs will mostly fall in the second category… So maybe we do docbook+javadoc publishing manually by checking in the built files to the site SVN folder? This way we can do both - fix doc bugs between releases and time publishing with a given release.
> 
> 
> I think that tying it into CI is much simpler. Otherwise it relies on people remembering to commit and publish.

Yes, but is this even an issue? Most docs should not be published on each code commit, and should be deferred till we make an official release. Our releases are fairly formalized events with a documented scenario that a release manager follows. One of the steps in this scenario can be doc publishing.

Andrus

[*] The old docs were skipping a variety of topics related to the Modeler and ROP. I am afraid if we want to ever release 3.1-final, we'll have to compromise on those too.

Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 29/10/12 5:54pm, Andrus Adamchik wrote:
> Awesome!
>
>> 1c Fix or remove news: I asked oninfra and was pointed to some similar solutions
>
> Unless we have a plan for this, I suggest moving the most recent blog entry announcements to Apache CMS pages, and manually filling the summary section on the home page. We'll revisit it later.




>> 1d Breadcrumb doesn't work:we have code for this, but do we even need it?
>
> Yeah, it was useful, but not that useful to delay migration.

I just removed it.


>
>> I don't know where we are with 2a. Is this mostly done? Somewhat done?
>
> The new docs are for 3.1 and 3.2 only. (Older releases will keep using SVN-checked wikidocs of course)
>
> The docs are not finished (we have 100% of tutorials, ~60-70% of Cayenne Guide, 1% of Modeler Guide). But I still suggest publishing what we have in docbook and do not preserve wikidocs for 3.1 (and 3.2). The docbook project is a complete rewrite, rather then porting of the old docs. So it doesn't have any legacy assumptions and attempts to present a consistent picture of the framework the way I see it now (as opposed to the way I saw it ca 2004). Conversely wikidocs doesn't have anything on 3.1 DI, and will confuse anybody trying to get started with Cayenne 3.1

OK, then we just have to get it finished before we release 3.1. Until then it can serve as partial documentation with an early focus on the new features. Sounds fair?

Actually I found our docbook output:

http://ci.apache.org/projects/cayenne/docbook/

  
> Another issue with doc publishing - should we be tying doc publishing to CI? All doc changes can be roughly split into two categories - those catching up with an existing release and those corresponding to the yet unreleased code. Especially the Javadocs will mostly fall in the second category… So maybe we do docbook+javadoc publishing manually by checking in the built files to the site SVN folder? This way we can do both - fix doc bugs between releases and time publishing with a given release.


I think that tying it into CI is much simpler. Otherwise it relies on people remembering to commit and publish. And the buildbot documentation build doesn't fail in odd ways like the big Jenkins run against different databases.

But I agree that we need a way to easily branch the docs and publish them in a sane way. Let me get some more answers from infra about the staging/publishing process when we want to bypass svn committing for the output.

In theory, docbook is just an alternative to textile or markdown. But I don't think that would be easy to tie into Perl somehow...

  
> Thoughts?
>
>> I've never written Perl, so much of the scripting is a bit foreign to me.
>
> I have some Perl skills (I can *write* in Perl, but often can't read other's code :) Perl is "write-only" after all :)). Let me know if you need help with Perl scripting.

Great. To me Perl looks like one multiline regular expression.


Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Awesome!

> 1c Fix or remove news: I asked oninfra and was pointed to some similar solutions

Unless we have a plan for this, I suggest moving the most recent blog entry announcements to Apache CMS pages, and manually filling the summary section on the home page. We'll revisit it later.

> 1d Breadcrumb doesn't work:we have code for this, but do we even need it?

Yeah, it was useful, but not that useful to delay migration.

> I don't know where we are with 2a. Is this mostly done? Somewhat done?

The new docs are for 3.1 and 3.2 only. (Older releases will keep using SVN-checked wikidocs of course)

The docs are not finished (we have 100% of tutorials, ~60-70% of Cayenne Guide, 1% of Modeler Guide). But I still suggest publishing what we have in docbook and do not preserve wikidocs for 3.1 (and 3.2). The docbook project is a complete rewrite, rather then porting of the old docs. So it doesn't have any legacy assumptions and attempts to present a consistent picture of the framework the way I see it now (as opposed to the way I saw it ca 2004). Conversely wikidocs doesn't have anything on 3.1 DI, and will confuse anybody trying to get started with Cayenne 3.1

Another issue with doc publishing - should we be tying doc publishing to CI? All doc changes can be roughly split into two categories - those catching up with an existing release and those corresponding to the yet unreleased code. Especially the Javadocs will mostly fall in the second category… So maybe we do docbook+javadoc publishing manually by checking in the built files to the site SVN folder? This way we can do both - fix doc bugs between releases and time publishing with a given release.

Thoughts?

> I've never written Perl, so much of the scripting is a bit foreign to me.

I have some Perl skills (I can *write* in Perl, but often can't read other's code :) Perl is "write-only" after all :)). Let me know if you need help with Perl scripting.

On Oct 29, 2012, at 4:25 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> OK, let's see what needs to be done.
> 
> Phase 1:
> Apache CMS to replace Confluence CAY main site
> 
> 1a Broken links: I think I've got most of them
> 1b Broken images in a few places: I've fixed some of those now
> 1c Fix or remove news: I asked oninfra and was pointed to some similar solutions
> 1d Breadcrumb doesn't work:we have code for this, but do we even need it?
> 1e Review how we can keep both the Apache CMS deployment and mix into that the CAYDOC pages: advice from infra was to just commit the old docs into svn. Easily enough done. I'd just need to strip off the page template from the files. I'll do that...
> 
> 
> Phase 2:
> Replace CAYDOC with docbook generated documentation
> 
> 2a Finish migration of all pages into docbook
> 2b Speak to infra about how the build and deployment system for docbook will work
> 
> 
> I don't know where we are with 2a. Is this mostly done? Somewhat done? Most of phase 1 is easy other than coming up with a good solution for 1c and implementing that. I've never written Perl, so much of the scripting is a bit foreign to me.
> 
> Ari
> 
> 
> 
> 
> 
> On 28/10/12 1:55am, Andrus Adamchik wrote:
>> Hi Ari,
>> 
>> So do you think we can launch the site, and deal with remaining issues later?
>> 
>> Our menus are outdated and we can't publish the new docs for 3.1/3.2. We are really stuck now. And I'd rather we sacrifice some current functionality, but make it live ASAP.
>> 
>> Thanks,
>> Andrus
>> 
>> 
>> On Oct 19, 2012, at 3:15 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>> On 18/10/12 5:51pm, Andrus Adamchik wrote:
>>>> 
>>>> On Oct 18, 2012, at 4:17 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>>> 
>>>>> I think that problem of truncated text is solvable in nice ways. But I am unclear from the reading of the code as to how the content is included. Doesn't the Apache CMS only get triggered on svn commit? How does it update content automatically in response to external data from an svn feed, Jira list or RSS feed? Those things would be really nice to show the world that stuff is happening. How nice would it be to show users the list of recent thread subjects from the mailing list…
>>>> 
>>>> The dynamic part can be done with JavaScript. The only limitation is accessing data from external domains. We can work around it in a few ways.
>>>> 
>>>> 1. Including externally hosted JS. E.g. Tapestry home page includes an external twitter widget.
>>>> 
>>>> 2. We can also periodically save a given external RSS feeds to a file on our server with a cron'd curl command, and then read it with JS hosted on our site.
>>> 
>>> If we save a file in that way, we may not need to merge the content client-side. I see that Apache CMS has a cgi-bin folder. Maybe we can use that to merge the content.
>>> 
>>> 
>>> Ari
>>> 
>>> 
>>> 
>>> 
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>> 
>> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
OK, let's see what needs to be done.

Phase 1:
Apache CMS to replace Confluence CAY main site

1a Broken links: I think I've got most of them
1b Broken images in a few places: I've fixed some of those now
1c Fix or remove news: I asked oninfra and was pointed to some similar solutions
1d Breadcrumb doesn't work:we have code for this, but do we even need it?
1e Review how we can keep both the Apache CMS deployment and mix into that the CAYDOC pages: advice from infra was to just commit the old docs into svn. Easily enough done. I'd just need to strip off the page template from the files. I'll do that...


Phase 2:
Replace CAYDOC with docbook generated documentation

2a Finish migration of all pages into docbook
2b Speak to infra about how the build and deployment system for docbook will work


I don't know where we are with 2a. Is this mostly done? Somewhat done? Most of phase 1 is easy other than coming up with a good solution for 1c and implementing that. I've never written Perl, so much of the scripting is a bit foreign to me.

Ari





On 28/10/12 1:55am, Andrus Adamchik wrote:
> Hi Ari,
>
> So do you think we can launch the site, and deal with remaining issues later?
>
> Our menus are outdated and we can't publish the new docs for 3.1/3.2. We are really stuck now. And I'd rather we sacrifice some current functionality, but make it live ASAP.
>
> Thanks,
> Andrus
>
>
> On Oct 19, 2012, at 3:15 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>> On 18/10/12 5:51pm, Andrus Adamchik wrote:
>>>
>>> On Oct 18, 2012, at 4:17 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>>
>>>> I think that problem of truncated text is solvable in nice ways. But I am unclear from the reading of the code as to how the content is included. Doesn't the Apache CMS only get triggered on svn commit? How does it update content automatically in response to external data from an svn feed, Jira list or RSS feed? Those things would be really nice to show the world that stuff is happening. How nice would it be to show users the list of recent thread subjects from the mailing list…
>>>
>>> The dynamic part can be done with JavaScript. The only limitation is accessing data from external domains. We can work around it in a few ways.
>>>
>>> 1. Including externally hosted JS. E.g. Tapestry home page includes an external twitter widget.
>>>
>>> 2. We can also periodically save a given external RSS feeds to a file on our server with a cron'd curl command, and then read it with JS hosted on our site.
>>
>> If we save a file in that way, we may not need to merge the content client-side. I see that Apache CMS has a cgi-bin folder. Maybe we can use that to merge the content.
>>
>>
>> Ari
>>
>>
>>
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>
>

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
Hi Ari,

So do you think we can launch the site, and deal with remaining issues later?

Our menus are outdated and we can't publish the new docs for 3.1/3.2. We are really stuck now. And I'd rather we sacrifice some current functionality, but make it live ASAP.

Thanks,
Andrus


On Oct 19, 2012, at 3:15 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> On 18/10/12 5:51pm, Andrus Adamchik wrote:
>> 
>> On Oct 18, 2012, at 4:17 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>> 
>>> I think that problem of truncated text is solvable in nice ways. But I am unclear from the reading of the code as to how the content is included. Doesn't the Apache CMS only get triggered on svn commit? How does it update content automatically in response to external data from an svn feed, Jira list or RSS feed? Those things would be really nice to show the world that stuff is happening. How nice would it be to show users the list of recent thread subjects from the mailing list…
>> 
>> The dynamic part can be done with JavaScript. The only limitation is accessing data from external domains. We can work around it in a few ways.
>> 
>> 1. Including externally hosted JS. E.g. Tapestry home page includes an external twitter widget.
>> 
>> 2. We can also periodically save a given external RSS feeds to a file on our server with a cron'd curl command, and then read it with JS hosted on our site.
> 
> If we save a file in that way, we may not need to merge the content client-side. I see that Apache CMS has a cgi-bin folder. Maybe we can use that to merge the content.
> 
> 
> Ari
> 
> 
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 18/10/12 5:51pm, Andrus Adamchik wrote:
>
> On Oct 18, 2012, at 4:17 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
>> I think that problem of truncated text is solvable in nice ways. But I am unclear from the reading of the code as to how the content is included. Doesn't the Apache CMS only get triggered on svn commit? How does it update content automatically in response to external data from an svn feed, Jira list or RSS feed? Those things would be really nice to show the world that stuff is happening. How nice would it be to show users the list of recent thread subjects from the mailing list…
>
> The dynamic part can be done with JavaScript. The only limitation is accessing data from external domains. We can work around it in a few ways.
>
> 1. Including externally hosted JS. E.g. Tapestry home page includes an external twitter widget.
>
> 2. We can also periodically save a given external RSS feeds to a file on our server with a cron'd curl command, and then read it with JS hosted on our site.

If we save a file in that way, we may not need to merge the content client-side. I see that Apache CMS has a cgi-bin folder. Maybe we can use that to merge the content.


Ari




-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 18, 2012, at 4:17 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> I think that problem of truncated text is solvable in nice ways. But I am unclear from the reading of the code as to how the content is included. Doesn't the Apache CMS only get triggered on svn commit? How does it update content automatically in response to external data from an svn feed, Jira list or RSS feed? Those things would be really nice to show the world that stuff is happening. How nice would it be to show users the list of recent thread subjects from the mailing list…

The dynamic part can be done with JavaScript. The only limitation is accessing data from external domains. We can work around it in a few ways. 

1. Including externally hosted JS. E.g. Tapestry home page includes an external twitter widget. 

2. We can also periodically save a given external RSS feeds to a file on our server with a cron'd curl command, and then read it with JS hosted on our site.

Andrus

Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 18/10/12 1:04am, Andrus Adamchik wrote:
>
> On Oct 17, 2012, at 4:46 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
>>> 2. Figure how to implement blog-posts (news)
>>
>> I tried to analyse the root apache site but I was unable to figure what drove the content in the neat little svn, jira and apache blog dynamic content you can see here:
>>
>>    http://svn.apache.org/repos/asf/infrastructure/site/trunk/content/index.html
>>
>> It would be nice to do something similar.
>
> We have 2 issues here - where the actual blog engine should reside, and how to maintain. a list of recent posts on the home pages.
>
> I'd say we can start using CMS for both of these things. For the blog engine in parallel we can experiment with some free blogging platform outside Apache. As for the summaries, manual handling of those will allow us to better tweak the summary text, the order of entries, their expiration, etc. In the past automatically grabbing a summary from Confluence often resulted in truncated or otherwise unreadable text.


I think that problem of truncated text is solvable in nice ways. But I am unclear from the reading of the code as to how the content is included. Doesn't the Apache CMS only get triggered on svn commit? How does it update content automatically in response to external data from an svn feed, Jira list or RSS feed? Those things would be really nice to show the world that stuff is happening. How nice would it be to show users the list of recent thread subjects from the mailing list...


>> 4. Replace the confluence wiki with something. It hasn't been successful at all as a community wiki, so it will not be greatly missed.
>
> I don't think we are under any pressure to do that. IIRC infra only wanted to get rid of Confluence autoexport. Using Confluence as a wiki is still supported. The good thing about it is that we can create any unorganized content that does not belong anywhere (such as design blueprints, board reports, etc.)
>
> What I think we should do though is link the menu to the dynamic URL of wiki, and delete the autoexported part. And then kill stale and unsupported sections like FAQ. This should indeed be all superseded by Docbook, user list, stackoverflow, etc.

Perhaps, but the real issue with the wiki is that it isn't. A wiki that is. Too hard for users to create an account and edit or add information. I want something with anonymous (or simple sign up) editing. Often I find the most usable solutions are things like manuals with user comments at the bottom. The PHP manual has been like that for 10 years. Also the mysql manual and more recently the Apache httpd manual.


>>   But it would be nice to replace it with something. Stackoverflow or getsatisfaction, for knowledgebase perhaps.
>
> I am following 'apache-cayenne' tag on stackoverflow at http://stackoverflow.com/questions/tagged/apache-cayenne and trying to help people there… So the knowledge base sort of grows there organically (in addition to cayenne-user).


Good. But we should drive people toward that if it is to become our defacto knowledgebase. That might be just a link (easy) or a feed of recent topics (again, don't understand how this technology is supposed to work in the Apache CMS).


Ari




-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 17, 2012, at 4:46 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:

>> 2. Figure how to implement blog-posts (news)
> 
> I tried to analyse the root apache site but I was unable to figure what drove the content in the neat little svn, jira and apache blog dynamic content you can see here:
> 
>   http://svn.apache.org/repos/asf/infrastructure/site/trunk/content/index.html
> 
> It would be nice to do something similar.

We have 2 issues here - where the actual blog engine should reside, and how to maintain. a list of recent posts on the home pages. 

I'd say we can start using CMS for both of these things. For the blog engine in parallel we can experiment with some free blogging platform outside Apache. As for the summaries, manual handling of those will allow us to better tweak the summary text, the order of entries, their expiration, etc. In the past automatically grabbing a summary from Confluence often resulted in truncated or otherwise unreadable text.

> 4. Replace the confluence wiki with something. It hasn't been successful at all as a community wiki, so it will not be greatly missed.

I don't think we are under any pressure to do that. IIRC infra only wanted to get rid of Confluence autoexport. Using Confluence as a wiki is still supported. The good thing about it is that we can create any unorganized content that does not belong anywhere (such as design blueprints, board reports, etc.) 

What I think we should do though is link the menu to the dynamic URL of wiki, and delete the autoexported part. And then kill stale and unsupported sections like FAQ. This should indeed be all superseded by Docbook, user list, stackoverflow, etc.

>  But it would be nice to replace it with something. Stackoverflow or getsatisfaction, for knowledgebase perhaps.

I am following 'apache-cayenne' tag on stackoverflow at http://stackoverflow.com/questions/tagged/apache-cayenne and trying to help people there… So the knowledge base sort of grows there organically (in addition to cayenne-user). 

Andrus


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 17/10/12 7:22pm, Aristedes Maniatis wrote:
> Nice. So it seems like the plan needs to be:
>
> 1. Make all the links relative so it is easy to navigate around the staging site

Done. Looks like Dima already made most of the pages and I just need to tweak the template, css, js a little and it is all good.

> 2. Figure how to implement blog-posts (news)

I tried to analyse the root apache site but I was unable to figure what drove the content in the neat little svn, jira and apache blog dynamic content you can see here:

    http://svn.apache.org/repos/asf/infrastructure/site/trunk/content/index.html

It would be nice to do something similar.


> 3. Finish pulling over all the content (there isn't actually that much left).

Actually, other than news and some missing images I think it is almost done.


Oh, and there is another item:

4. Replace the confluence wiki with something. It hasn't been successful at all as a community wiki, so it will not be greatly missed. But it would be nice to replace it with something. Stackoverflow or getsatisfaction, for knowledgebase perhaps.


Ari



>
> Dima, do you remember where in svn the templates live?
>
>
> Ari
>
>
>
> On 17/10/12 7:10pm, Dzmitry Kazimirchyk wrote:
>> Apache CMS staging site is up and running at http://cayenne.staging.apache.org/. Skeleton html is still containing hard links to cayenne's main site, etc. So some work needs to be done on this.
>>
>> In overall a number of pages have already been converted to new format. You can view, edit, add new ones by following the next url and logging in with your apache credentials:
>>
>> https://cms.apache.org/redirect?uri=http://cayenne.apache.org/
>>
>>
>> Dima
>>
>>
>> On 10/17/2012 09:32 AM, Andrus Adamchik wrote:
>>>  From what I can gather, this is the last mention of the status and it is likely that nobody touched it since then:
>>>
>>> http://markmail.org/message/afmvwmbigijbwlvl
>>>
>>> also per https://issues.apache.org/jira/browse/INFRA-4053 the staging area should be available.
>>>
>>> Andrus
>>>
>>>
>>> On Oct 17, 2012, at 7:51 AM, Aristedes Maniatis <am...@apache.org> wrote:
>>>> Dima
>>>>
>>>> I think you were the last person working on the Apache CMS migration (no docbook, but the main site migration). Can you give us a summary of where you got up to? What is left to be done?
>>>>
>>>> Cheers
>>>> Ari
>>>>
>>>>
>>>>
>>>> --
>>>> -------------------------->
>>>> Aristedes Maniatis
>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>>
>>
>>
>

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Michael Gentry <mg...@masslight.net>.
Interesting.  I hadn't actually looked into this yet, but it looks
like the main content is in Markdown.  Where is the CSS?  I couldn't
locate it.

Thanks,

mrg

PS. I've been using Jekyll (https://github.com/mojombo/jekyll) lately
which isn't too bad of a static content site generator and blogging
system.  It also uses Markdown.  It really helps (at least me) to use
a Markdown editor.  I've been using Mou (http://mouapp.com/) on OS X
so far, but there are many others available.  I put together a list of
Markdown editors I found for OS X if anyone would like to look at the
different offerings.


On Wed, Oct 17, 2012 at 4:30 AM, Dzmitry Kazimirchyk
<dk...@gmail.com> wrote:
>> Dima, do you remember where in svn the templates live?
>
>
> Sure.
>
> https://svn.apache.org/repos/asf/cayenne/site/cms/trunk/templates/.
>
>
> Dima
>
>
> On 10/17/2012 11:22 AM, Aristedes Maniatis wrote:
>>
>> Nice. So it seems like the plan needs to be:
>>
>> 1. Make all the links relative so it is easy to navigate around the
>> staging site
>> 2. Figure how to implement blog-posts (news)
>> 3. Finish pulling over all the content (there isn't actually that much
>> left).
>>
>> Dima, do you remember where in svn the templates live?
>>
>>
>> Ari
>>
>>
>>
>> On 17/10/12 7:10pm, Dzmitry Kazimirchyk wrote:
>>>
>>> Apache CMS staging site is up and running at
>>> http://cayenne.staging.apache.org/. Skeleton html is still containing hard
>>> links to cayenne's main site, etc. So some work needs to be done on this.
>>>
>>> In overall a number of pages have already been converted to new format.
>>> You can view, edit, add new ones by following the next url and logging in
>>> with your apache credentials:
>>>
>>> https://cms.apache.org/redirect?uri=http://cayenne.apache.org/
>>>
>>>
>>> Dima
>>>
>>>
>>> On 10/17/2012 09:32 AM, Andrus Adamchik wrote:
>>>>
>>>>  From what I can gather, this is the last mention of the status and it
>>>> is likely that nobody touched it since then:
>>>>
>>>> http://markmail.org/message/afmvwmbigijbwlvl
>>>>
>>>> also per https://issues.apache.org/jira/browse/INFRA-4053 the staging
>>>> area should be available.
>>>>
>>>> Andrus
>>>>
>>>>
>>>> On Oct 17, 2012, at 7:51 AM, Aristedes Maniatis <am...@apache.org>
>>>> wrote:
>>>>>
>>>>> Dima
>>>>>
>>>>> I think you were the last person working on the Apache CMS migration
>>>>> (no docbook, but the main site migration). Can you give us a summary of
>>>>> where you got up to? What is left to be done?
>>>>>
>>>>> Cheers
>>>>> Ari
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -------------------------->
>>>>> Aristedes Maniatis
>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>>>
>>>
>>>
>>
>

Re: Website CMS

Posted by Dzmitry Kazimirchyk <dk...@gmail.com>.
> Dima, do you remember where in svn the templates live? 

Sure.

https://svn.apache.org/repos/asf/cayenne/site/cms/trunk/templates/.


Dima

On 10/17/2012 11:22 AM, Aristedes Maniatis wrote:
> Nice. So it seems like the plan needs to be:
>
> 1. Make all the links relative so it is easy to navigate around the 
> staging site
> 2. Figure how to implement blog-posts (news)
> 3. Finish pulling over all the content (there isn't actually that much 
> left).
>
> Dima, do you remember where in svn the templates live?
>
>
> Ari
>
>
>
> On 17/10/12 7:10pm, Dzmitry Kazimirchyk wrote:
>> Apache CMS staging site is up and running at 
>> http://cayenne.staging.apache.org/. Skeleton html is still containing 
>> hard links to cayenne's main site, etc. So some work needs to be done 
>> on this.
>>
>> In overall a number of pages have already been converted to new 
>> format. You can view, edit, add new ones by following the next url 
>> and logging in with your apache credentials:
>>
>> https://cms.apache.org/redirect?uri=http://cayenne.apache.org/
>>
>>
>> Dima
>>
>>
>> On 10/17/2012 09:32 AM, Andrus Adamchik wrote:
>>>  From what I can gather, this is the last mention of the status and 
>>> it is likely that nobody touched it since then:
>>>
>>> http://markmail.org/message/afmvwmbigijbwlvl
>>>
>>> also per https://issues.apache.org/jira/browse/INFRA-4053 the 
>>> staging area should be available.
>>>
>>> Andrus
>>>
>>>
>>> On Oct 17, 2012, at 7:51 AM, Aristedes Maniatis 
>>> <am...@apache.org> wrote:
>>>> Dima
>>>>
>>>> I think you were the last person working on the Apache CMS 
>>>> migration (no docbook, but the main site migration). Can you give 
>>>> us a summary of where you got up to? What is left to be done?
>>>>
>>>> Cheers
>>>> Ari
>>>>
>>>>
>>>>
>>>> -- 
>>>> -------------------------->
>>>> Aristedes Maniatis
>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>>
>>
>>
>


Re: Website CMS

Posted by Aristedes Maniatis <ar...@maniatis.org>.
Nice. So it seems like the plan needs to be:

1. Make all the links relative so it is easy to navigate around the staging site
2. Figure how to implement blog-posts (news)
3. Finish pulling over all the content (there isn't actually that much left).

Dima, do you remember where in svn the templates live?


Ari



On 17/10/12 7:10pm, Dzmitry Kazimirchyk wrote:
> Apache CMS staging site is up and running at http://cayenne.staging.apache.org/. Skeleton html is still containing hard links to cayenne's main site, etc. So some work needs to be done on this.
>
> In overall a number of pages have already been converted to new format. You can view, edit, add new ones by following the next url and logging in with your apache credentials:
>
> https://cms.apache.org/redirect?uri=http://cayenne.apache.org/
>
>
> Dima
>
>
> On 10/17/2012 09:32 AM, Andrus Adamchik wrote:
>>  From what I can gather, this is the last mention of the status and it is likely that nobody touched it since then:
>>
>> http://markmail.org/message/afmvwmbigijbwlvl
>>
>> also per https://issues.apache.org/jira/browse/INFRA-4053 the staging area should be available.
>>
>> Andrus
>>
>>
>> On Oct 17, 2012, at 7:51 AM, Aristedes Maniatis <am...@apache.org> wrote:
>>> Dima
>>>
>>> I think you were the last person working on the Apache CMS migration (no docbook, but the main site migration). Can you give us a summary of where you got up to? What is left to be done?
>>>
>>> Cheers
>>> Ari
>>>
>>>
>>>
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>
>
>

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Website CMS

Posted by Dzmitry Kazimirchyk <dk...@gmail.com>.
Apache CMS staging site is up and running at 
http://cayenne.staging.apache.org/. Skeleton html is still containing 
hard links to cayenne's main site, etc. So some work needs to be done on 
this.

In overall a number of pages have already been converted to new format. 
You can view, edit, add new ones by following the next url and logging 
in with your apache credentials:

https://cms.apache.org/redirect?uri=http://cayenne.apache.org/


Dima


On 10/17/2012 09:32 AM, Andrus Adamchik wrote:
>  From what I can gather, this is the last mention of the status and it is likely that nobody touched it since then:
>
> http://markmail.org/message/afmvwmbigijbwlvl
>
> also per https://issues.apache.org/jira/browse/INFRA-4053 the staging area should be available.
>
> Andrus
>
>
> On Oct 17, 2012, at 7:51 AM, Aristedes Maniatis <am...@apache.org> wrote:
>> Dima
>>
>> I think you were the last person working on the Apache CMS migration (no docbook, but the main site migration). Can you give us a summary of where you got up to? What is left to be done?
>>
>> Cheers
>> Ari
>>
>>
>>
>> -- 
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>


Re: Website CMS

Posted by Andrus Adamchik <an...@objectstyle.org>.
From what I can gather, this is the last mention of the status and it is likely that nobody touched it since then:

http://markmail.org/message/afmvwmbigijbwlvl

also per https://issues.apache.org/jira/browse/INFRA-4053 the staging area should be available.

Andrus


On Oct 17, 2012, at 7:51 AM, Aristedes Maniatis <am...@apache.org> wrote:
> Dima
> 
> I think you were the last person working on the Apache CMS migration (no docbook, but the main site migration). Can you give us a summary of where you got up to? What is left to be done?
> 
> Cheers
> Ari
> 
> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>