confluentinc / kafka-tutorials Goto Github PK

We should remove the top text and keep the bottom one, and also add some color to the CTA.

People might enjoy getting updates when we add new content. Let's put a mailing list form on the main page.

Safari 12.1.1

chrome

"Mark Teehan [5:20 PM]
A prospect needs a replace() UDF to replace special characters in kSQL. I'm not a java coder. They cannot do this in an SMT so kSQL is the next best option. Ideally a UDF that accepts an ASCII code (these are unprintable), and one that can be nested. Does anyone know of a suitable UDF chunk of code that I can use as a starting point?"

Java 8 is EOL
CP officially support Java 11.
We should too

Inspired by https://twitter.com/monitoring_king/status/1148133135374327808?s=21

Not sure if possible with KSQL yet

In order to effectively focus on the writing of recipe instructions, provide infrastructure to support markup language (Asciidoc/asciidoctor preferable, markdown is ok).
Authoring the recipe instruction with HTML is counterproductive and error-prone.
Not only it makes writing difficult (you probably need HTML editor to highlight breakage of open/close tags, support semantical tags) but it also makes review process difficult.

Docs team uses rst (though I think it's a terrible choice for markup, it's still better than HTML)
PS, Integration architects and training team use asciidoc for customer reports, white papers and training curriculums respectively.

The tabs for the separate platforms (kafka, kstreams, and ksql) are super handy. What would we think of extending the tabbing system to the three...let's call them "modalities," so we can sound extra annoying (try/test/deploy)? It might make each recipe page a bit less daunting and require less scrolling.

Started running through a recipe just to get the hang of things. I picked "Transform a stream of events". Two notes:

1. Gradle is referred to as gradlew in the examples. Typo or deliberate to make people type things? gradlew build in step 3 and gradlew shadowJar in step 5.

2. I got confused between step 2 and 3. Step 2 says to create a config directory with a dev.properties file. Step 3 says mkdir -p src/main/avro. But I did a cd to the config directory to create the file, which meant I had configuration/src/main/avro after step 3.

I know it's my fault but it seems like since recipes are new we should have some conventions. Maybe a convention should be to make paths absolute to a recipe basedir at all times?

Not sure this is currently possible with KSQL.

The code of a recipe today is written in «wild-wild-west» style- different people use whatever style they have configured in their IDEs.

Confluent uses Google style guide for java https://google.github.io/styleguide/javaguide.html
All Confluent projects have the checkstyle plugin enabled to enforce checks.

https://confluentinc.atlassian.net/wiki/spaces/Engineering/pages/5505079/New+Hire+Onboard#NewHireOnboard-CodingStyle

CD recipes should adopt is as well.