Re: Sling Site and CMS
Hi Felix, On Tue, May 22, 2012 at 10:59 AM, Felix Meschberger fmesc...@adobe.com wrote: ...I worked a bit more on the conversion and the rendering... Cool, thanks! Are you planning to redirect the old URLs to the new ones? For example http://sling.apache.org/site/getting-started.html would become http://sling.apache.org/documentation/getting-started.html as it's now at http://sling.staging.apache.org/documentation/getting-started.html I think we need that, as we have such URLs scattered around blogs, articles and product documentations. I've gone though the current http://sling.staging.apache.org and noted a few remaining problems, will report in SLING-2002 (but jira seems to be down right now). -Bertrand
Re: Sling Site and CMS
Hi,
Am 24.05.2012 um 10:10 schrieb Bertrand Delacretaz:
Hi Felix,
On Tue, May 22, 2012 at 10:59 AM, Felix Meschberger fmesc...@adobe.com
wrote:
...I worked a bit more on the conversion and the rendering...
Cool, thanks!
Are you planning to redirect the old URLs to the new ones?
Yes, the idea is to have an .htdocs in the old site folder which statically
redirects to the new locations once we are there.
I've gone though the current http://sling.staging.apache.org and noted
a few remaining problems, will report in SLING-2002 (but jira seems to
be down right now).
Ok, thanks.
Right some tables are converted but don't show correctly because apparently the
ASF CMS table support requires table headers and those failing tables don't
have headers.
Then, of course, all {note}, {panel}, etc. macros have not been converted. We
need to come with a solution here.
Regards
Felix
Re: Sling Site and CMS
On Thu, May 24, 2012 at 11:13 AM, Felix Meschberger fmesc...@adobe.com wrote:
...Right some tables are converted but don't show correctly because
apparently the ASF CMS table support requires
table headers and those failing tables don't have headers
I see tables broken in those four pages (but might not have checked
all pages), we can probably fix those by hand:
http://sling.staging.apache.org/documentation/the-sling-engine/authentication/authentication-authenticationhandler.html
http://sling.staging.apache.org/documentation/the-sling-engine/request-parameters.html
http://sling.staging.apache.org/documentation/bundles/content-loading-jcr-contentloader.html
http://sling.staging.apache.org/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html
...
Then, of course, all {note}, {panel}, etc. macros have not been converted. We
need to come with a solution here
Which might also be fix by hand and/or find simpler layouts that work, IMO.
-Bertrand
Re: Sling Site and CMS
Hi,
Right, next steps should be fix by hand, which I already started with some
pages (e.g. duplicate titles) and structuring the files according today's site.
Regards
Felix
Am 24.05.2012 um 11:33 schrieb Bertrand Delacretaz:
On Thu, May 24, 2012 at 11:13 AM, Felix Meschberger fmesc...@adobe.com
wrote:
...Right some tables are converted but don't show correctly because
apparently the ASF CMS table support requires
table headers and those failing tables don't have headers
I see tables broken in those four pages (but might not have checked
all pages), we can probably fix those by hand:
http://sling.staging.apache.org/documentation/the-sling-engine/authentication/authentication-authenticationhandler.html
http://sling.staging.apache.org/documentation/the-sling-engine/request-parameters.html
http://sling.staging.apache.org/documentation/bundles/content-loading-jcr-contentloader.html
http://sling.staging.apache.org/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html
...
Then, of course, all {note}, {panel}, etc. macros have not been converted.
We need to come with a solution here
Which might also be fix by hand and/or find simpler layouts that work, IMO.
-Bertrand
Re: Sling Site and CMS
Great work, Felix - I like the new layout :)
Carsten
2012/5/22 Felix Meschberger fmesc...@adobe.com:
Hi,
Am 22.05.2012 um 10:59 schrieb Felix Meschberger:
Hi
Thanks for the feedback.
I worked a bit more on the conversion and the rendering.
I have described some supported functionality in the site/trunk/readme.txt
file.
Finally, I started fixing conversion leftovers (like removing duplicate
titles or fixing the bullet points on the bundles page).
Have a look at sling.staging.apache.org. IMHO it looks much better now.
Remaining tasks include:
* Fully recreate subfolder structures with real filesystem folders
* Fix-up all tables (ASF CMS markdown seems to not like tables without
headers)
* Fixup remaining missing things like {note} macros and the like.
Plus: The download page. I imagine we create a special download page template
for this where the source is just a list of artifact names and Maven GAV
entries. The template would read the source and prepare the markup for the
actual download page.
Regards
Felix
Am 21.05.2012 um 14:24 schrieb Ruben Reusser:
also, it seems like the tutorials section is not working due to the URL
http://sling.staging.apache.org/tutorials--how-tos.html
This had a special character conversion issue earlier (as had the pages with
parentheses in the name). I modified the page name to URL conversion and
this should now be fixed:
http://sling.staging.apache.org/tutorials-how-tos.html
Regards
Felix
Ruben
On 5/21/2012 5:05 AM, Bertrand Delacretaz wrote:
Hi Felix,
On Sun, May 20, 2012 at 1:09 AM, Felix Meschbergerfmesc...@adobe.com
wrote:
...Granted we have a few open issues like the confluence to markdown
conversion mangling with the {{}} constructs...
...The rest we can fix over time...
There's still a number of pages where tables and lists are broken and
make the content in unusable in large part:
http://sling.staging.apache.org/dispatching-requests.html
http://sling.staging.apache.org/mappings-for-resource-resolution.html
http://sling.staging.apache.org/bundles.html (no links)
http://sling.staging.apache.org/news.html
I think we should fix those before switching...unfortunately I'm
unable to help right now.
-Bertrand
--
Carsten Ziegeler
cziege...@apache.org
Re: Sling Site and CMS
Hi
Thanks for the feedback.
I worked a bit more on the conversion and the rendering.
I have described some supported functionality in the site/trunk/readme.txt file.
Finally, I started fixing conversion leftovers (like removing duplicate titles
or fixing the bullet points on the bundles page).
Have a look at sling.staging.apache.org. IMHO it looks much better now.
Remaining tasks include:
* Fully recreate subfolder structures with real filesystem folders
* Fix-up all tables (ASF CMS markdown seems to not like tables without
headers)
* Fixup remaining missing things like {note} macros and the like.
Am 21.05.2012 um 14:24 schrieb Ruben Reusser:
also, it seems like the tutorials section is not working due to the URL
http://sling.staging.apache.org/tutorials--how-tos.html
This had a special character conversion issue earlier (as had the pages with
parentheses in the name). I modified the page name to URL conversion and this
should now be fixed:
http://sling.staging.apache.org/tutorials-how-tos.html
Regards
Felix
Ruben
On 5/21/2012 5:05 AM, Bertrand Delacretaz wrote:
Hi Felix,
On Sun, May 20, 2012 at 1:09 AM, Felix Meschbergerfmesc...@adobe.com
wrote:
...Granted we have a few open issues like the confluence to markdown
conversion mangling with the {{}} constructs...
...The rest we can fix over time...
There's still a number of pages where tables and lists are broken and
make the content in unusable in large part:
http://sling.staging.apache.org/dispatching-requests.html
http://sling.staging.apache.org/mappings-for-resource-resolution.html
http://sling.staging.apache.org/bundles.html (no links)
http://sling.staging.apache.org/news.html
I think we should fix those before switching...unfortunately I'm
unable to help right now.
-Bertrand
Re: Sling Site and CMS
Hi,
Am 22.05.2012 um 10:59 schrieb Felix Meschberger:
Hi
Thanks for the feedback.
I worked a bit more on the conversion and the rendering.
I have described some supported functionality in the site/trunk/readme.txt
file.
Finally, I started fixing conversion leftovers (like removing duplicate
titles or fixing the bullet points on the bundles page).
Have a look at sling.staging.apache.org. IMHO it looks much better now.
Remaining tasks include:
* Fully recreate subfolder structures with real filesystem folders
* Fix-up all tables (ASF CMS markdown seems to not like tables without
headers)
* Fixup remaining missing things like {note} macros and the like.
Plus: The download page. I imagine we create a special download page template
for this where the source is just a list of artifact names and Maven GAV
entries. The template would read the source and prepare the markup for the
actual download page.
Regards
Felix
Am 21.05.2012 um 14:24 schrieb Ruben Reusser:
also, it seems like the tutorials section is not working due to the URL
http://sling.staging.apache.org/tutorials--how-tos.html
This had a special character conversion issue earlier (as had the pages with
parentheses in the name). I modified the page name to URL conversion and this
should now be fixed:
http://sling.staging.apache.org/tutorials-how-tos.html
Regards
Felix
Ruben
On 5/21/2012 5:05 AM, Bertrand Delacretaz wrote:
Hi Felix,
On Sun, May 20, 2012 at 1:09 AM, Felix Meschbergerfmesc...@adobe.com
wrote:
...Granted we have a few open issues like the confluence to markdown
conversion mangling with the {{}} constructs...
...The rest we can fix over time...
There's still a number of pages where tables and lists are broken and
make the content in unusable in large part:
http://sling.staging.apache.org/dispatching-requests.html
http://sling.staging.apache.org/mappings-for-resource-resolution.html
http://sling.staging.apache.org/bundles.html (no links)
http://sling.staging.apache.org/news.html
I think we should fix those before switching...unfortunately I'm
unable to help right now.
-Bertrand
Re: Sling Site and CMS
Hi Felix,
On Sun, May 20, 2012 at 1:09 AM, Felix Meschberger fmesc...@adobe.com wrote:
...Granted we have a few open issues like the confluence to markdown
conversion mangling with the {{}} constructs...
...The rest we can fix over time...
There's still a number of pages where tables and lists are broken and
make the content in unusable in large part:
http://sling.staging.apache.org/dispatching-requests.html
http://sling.staging.apache.org/mappings-for-resource-resolution.html
http://sling.staging.apache.org/bundles.html (no links)
http://sling.staging.apache.org/news.html
I think we should fix those before switching...unfortunately I'm
unable to help right now.
-Bertrand
Re: Sling Site and CMS
also, it seems like the tutorials section is not working due to the URL
http://sling.staging.apache.org/tutorials--how-tos.html
Ruben
On 5/21/2012 5:05 AM, Bertrand Delacretaz wrote:
Hi Felix,
On Sun, May 20, 2012 at 1:09 AM, Felix Meschbergerfmesc...@adobe.com wrote:
...Granted we have a few open issues like the confluence to markdown conversion
mangling with the {{}} constructs...
...The rest we can fix over time...
There's still a number of pages where tables and lists are broken and
make the content in unusable in large part:
http://sling.staging.apache.org/dispatching-requests.html
http://sling.staging.apache.org/mappings-for-resource-resolution.html
http://sling.staging.apache.org/bundles.html (no links)
http://sling.staging.apache.org/news.html
I think we should fix those before switching...unfortunately I'm
unable to help right now.
-Bertrand
Sling Site and CMS
Hi all,
I have been giving some quality time to the Sling site project [1] (see also
SLING-2002 [2]) again and have started a new page just to get the feel for
Markdown.
Granted we have a few open issues like the confluence to markdown conversion
mangling with the {{}} constructs (creating italic instead of code), I think
overall the experience for me has been very positive and feedback on the site
(well, we just have staging for now) is just great compared to Confluence.
I think the biggest open issue is the download page. I think we can solve this
with a download page template.
The rest we can fix over time.
So, I think it is about time to just switch to ASF CMS.
What needs to be done ?
* Setup the staging to production publishing
* Implement a download page template
* Make SLINGxSITE space on cwiki read-only
* Over time fix the pages
WDYT ?
Regards
Felix
