-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blog(Kaoto): Kaoto 2.2 release #1238
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The content LGTM, but the formatting should be changed to favor the markdown over HTML style. I think that the visualization may suffer by adding some fixed format.
<img src="cover.png" alt="Kaoto" height="400"/> | ||
</div> | ||
|
||
<br/><strong> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd avoid to have all that text in strong. Better highlight a few keywords instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the <strong>
tag
|
||
- New look and feel: The flow elements have been redesigned to provide a more modern and clean look. The new design is more intuitive and user-friendly, making it easier to work with your integrations. | ||
|
||
<div style="text-align: center"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd avoid adding too much divs around. I think you can use the format like.
![Canvas](canvas.png)
_Figure 1. Canvas_
I cannot recall if there is the possibility to resize. If not, it would be probably good to publish the image with the required size.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I'll reupload the images
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mmm, the issue with that is the images will lose quality, so they would look fine in the website but if you want to zoom in to see the details, then it will be "un-pretty"
|
||
You can also check out our [examples repository](https://github.com/KaotoIO/kaoto-examples) to see some more advanced use cases which were set up using Kaoto. | ||
|
||
<div style="text-align: center"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this div is useless. Keep it using MD format.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With all due respect, it's not useless, it centers the image in the webpage 😃
Hi @squakez, the This is how it looks like in the website: https://camel.apache.org/blog/2024/07/kaoto-release-2.1.0/ |
47bf3ca
to
b6e8098
Compare
🚀 Preview is available at https://pr-1238--camel.netlify.app |
b6e8098
to
09105ed
Compare
--- | ||
<br/><br/> | ||
<div style="text-align: center"> | ||
We invite you to explore these new features on your summer integrations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
summer integrations? is it a left-over of a copy-paste?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, my bad, I rephrased it
09105ed
to
32a465b
Compare
I'm wondering about the need to center the images, this is something that is already present in the default layout/styling. For example the |
In addition to that, the inline styling is not allowed by the content security policy and will be ignored by the browser. |
+1 to @zregvart comments. IMO we should limit the quantity of html and have a common look and feel and easier maintenance in the future. When we change the layout, the HTML that looks pretty now, may no longer look pretty after. Said that, I have no objection if you want to merge it. |
🚀 Preview is available at https://pr-1238--camel.netlify.app |
2 similar comments
🚀 Preview is available at https://pr-1238--camel.netlify.app |
🚀 Preview is available at https://pr-1238--camel.netlify.app |
for other blogposts, the "related posts" are below the article, there is only this one with them on the side |
e5e7ca7
to
3f62c15
Compare
I don't why would that be, as far as I can see, there's a mistake with the table MD definition, not sure if it relates, I fixed it and pushed it again. |
3f62c15
to
17fba3e
Compare
🚀 Preview is available at https://pr-1238--camel.netlify.app |
@apupier I don't think that's the updated website yet, is still showing bullet points for each feature, let's wait for another update, it seems there's a bit of delay |
17fba3e
to
8e67ce4
Compare
🚀 Preview is available at https://pr-1238--camel.netlify.app |
🚀 Preview is available at https://pr-1238--camel.netlify.app |
No description provided.