burning-duck discussion

[pbit]

Remove all modules we dont need

• Tours
• Destinations
• Demo content

[pbit]

Do we need a custom bundle for this?

[janroesler]

I think we should use the empty-webapp + CE bundle you made the last day..
We also can clean up the light-module to get one main page and one content page.
No more is needed at this time.

[janroesler]

Ok we need a clean .war file.
@pbit where is the link for tomcat bundle :)

[pbit]

Workin on it, push it to GH once its working.

[janroesler]

Ok, i have test yesterday the author and public configuration for the magnolia basic cms. Have move the war on the burning-duck server. But don't get it running :(

[janroesler]

Or lets say, Magnolia is running but don't load the right configuration 🗡
I have something wrong in the web.xml , i think.

[pbit]

Yeah we only had this config in local development.

But there is an entry in web.xml which should work (tm):

So it should be work if the context parameter is set:

In context.xml?

<Context>
  ...
  <Parameter name="magnoliaMode" value="public"
         override="false"/>
  ...
</Context>

[pbit]

Currently wrestling with maven...

• BAM breaks nearly everything -> remove it
• Magnolia enforces Magnolia license in all source files -> remove it

so there is not much left we can use ;)

[janroesler]

I have add the component for the page teaser.
Now it works like expected.
Need some improvements like:

• add field for substring length (?substring (0, ${content.val})
• add field for poste date
• add field or select for author

I think it would be nice when we have the component #4 for the version badge.
We can include the dialog field and the template in the teaser component 👍

And i add a card layout, but i don't know, don't feel right. We need a MEG 😄

[janroesler]

So add issues #9 and #10 for refactoring.

[janroesler]

We need the md component :D
If we have the component, is the "text and image" component still needed? @pbit

[pbit]

Yeah, CMS bundle is on the way hust cleaning up a few things.
@janroesler I would keep the text and image, may be easier to add small content everywhere.

[janroesler]

Ok, we have the bundle with markdownfn. The refactoring of this light module is almost done.
Is in the bundle a ready to use component for markdownfn? @pbit
Or should we create a new light module for this component?

[janroesler]

Have create the project https://github.com/orgs/burning-duck/projects/1 to add ideas for anything.
So we have nodes for any idea and don't lost something.

[janroesler]

Ok i have add a md component, but i don't get it running.
That is your part @pbit 📄

[pbit]

@janroesler but it worked on my machine ...

Basic syntax in freemarker:

[#if content.md?has_content]
${markdownfn.renderToHtml(content, "md")}
[/#if]

If the markdown comes from a JCR-Node or ContentMap we are not able to render the returned value.
There is some HtmlEscaping involved which breaks the renderer.
For more info see Javadocs in https://github.com/burning-duck/burning-duck-cms-bundle/blob/master/src/main/java/com/github/burningduck/cms/markdown/MarkdownTemplatingFunctions.java

In theory this opens a door which was closed by HtmlEscaping, as the original Node is unwraped, but if you know what youre doing there should be no problems.

The installer should register the functions:

The highlighting is not done on the server, I just dropped in http://prismjs.com/ ....