Moving Jenkins is the Way stories and case studies to jenkins.io

I’m starting this thread here to track conversations and progress of moving content from jenkinsistheway.io (currently hosted on godaddy.com) to jenkins.io.

Huge THANK YOU to @halkeye for his work on this.

BR,
alyssa

1 Like

I’m obviously not a lawyer, but is it a good idea to add images referencing intellectual property of one of the most litigious companies in the world to jenkins.io?

Hi @danielbeck - we can certainly leave it out. When we collect the stories we do ask folks whether we can use their logo. If they say ‘no’ we do not use it. Which logo are you referring?

thanks,
alyssa

They are a (the!) Mickey Mouse corporation.

Ha! :grinning_face_with_smiling_eyes:
Noted. Thank you! :blush:

also took me a bit to understand the code here, but assuming I do, its already on Jenkins Artwork and on the front banner on jenkins.io, its not new. Though I agree, a couple of the jenkins logos might be issues with them

Aww man, just when I thought I was doing a decent job at converting posts from freeform to machine parsable.

Jenkins is the way to achieve a fast pace and deliver value through automation – Jenkins has “Team:”

while

Jenkins is the way to do things quickly, simply and in a powerful way – Jenkins has “Team members” with some prefix text

one post has === Submitted by Jenkins User while another has === Submitted By Jenkins User

making progress cleaning up the data though. won’t be 100% but will get us mostly there.

Making this more machine parsable (for applying templates) might not be the best answer, but I think I’m close enough I’m still gonna try

@alyssat can you fix Jenkins is the way to cast magic of continuous delivery – Jenkins

Programming Language: Java, Python, Vue.js Platform : Android, iOS, Linux Version Control System: Gitlab Build Tool: Python

so the headers are different lines?

I think the rest of the inconsistencies I can handle myself.

I’ll get a draft up with all the parsed data soon, then start working on the layout again (would love help with the haml/html if anyone is better at CSS than me)

Rough draft of the data import - Jenkins is the way Import by halkeye · Pull Request #4828 · jenkins-infra/jenkins.io · GitHub

@oleg-nenashev brought up:

So we could keep jenkinsistheway.io and make it a standalone static site as well.

It doesn’t make a lot of difference to me yet, as I still gotta convert and present the data. Presenting in jenkins.io (haml) isn’t that much different than gatsby (react) once everything is in place.

Gotta figure out a way to parse out the quote so I can style it, but looking good so far