#55 How to publish your content using GitHub and Jekyll
Closed: scheduled 2 years ago by rlengland. Opened 2 years ago by theevilskeleton.


Comments moved from Taiga #397:

TheEvilSkeleton22 Nov 2021 04:13
*serveshad thanks! And no worries, take your time.

Servesha Dudhgaonkar22 Nov 2021 03:24
*rlengland Hi, I am working on the article and it will be ready-to-review soon. I will let this task update as such when it's ready. Thanks!
Apologies for the late reply I was on vacation.

Servesha Dudhgaonkar22 Nov 2021 03:23
*theevilskeleton hi, sorry I couldn't respond, I was on vacation. I am still working on the article. It will be ready-to-review soon. Thanks

TheEvilSkeleton18 Nov 2021 08:14
*serveshad hey, we just wanted to ask if you're still up for writing this article?

Richard England04 Nov 2021 10:01
Hi *serveshad I'm checking to see if you have made any progress on your article. When you have it to the point where you would like the editors to review it, please leave a link to the preview in the Taiga card and change the status of the card to ‘review’ using the dropdown menu in the upper right-hand corner.

Thank you

TheEvilSkeleton07 Oct 2021 14:18
I'm familiar with Jekyll. I had a lot of trouble using Jekyll on Fedora because setting up Ruby and Jekyll is a PITA and half, but I think I have enough knowledge to edit and design a cover image.

Metadata Update from @rlengland:
- Custom field preview-link adjusted to https://fedoramagazine.org/?p=35518&preview=true

2 years ago

Metadata Update from @rlengland:
- Custom field editor adjusted to theevilskeleton

2 years ago

Metadata Update from @rlengland:
- Custom field editor adjusted to @theevilskeleton (was: theevilskeleton)

2 years ago

Hello, @rlengland I have logged in to this issue and have access to it. Thanks!

Metadata Update from @rlengland:
- Assignee reset

2 years ago

Metadata Update from @rlengland:
- Issue assigned to serveshad

2 years ago

@serveshad I've assigned this article to you. Thank you for letting me know.

@serveshad It looks like you have been making progress on your article. I just noticed that you have not signed the FPCA ( Fedora Project Contributor Agreement). This is required for your article to be published in the Fedora Magazine.

When you are ready for the editors to review your work, please make sure you have signed and then leave a comment here so we know it is ready.

To Sign the FPCA:

Thanks for contributing!

2 years ago

The article is sent for the review

@theevilskeleton: I see that you've put yourself down as the editor for this one. How soon do you think you can get this done? We are in need of something to publish for Wednesday. If you can get this one done by then, that would be great. If not, I'll need to get something else ready.

Thanks.

Oops, sorry about that. I have free time right now. I'll take a look.

Ech... Fedora Magazine really needs some work in CSS. Where can I find the source code of Fedora Magazine?

Editing the CSS isn't the easiest thing to do. For now, it is probably best to stick with preformatted blocks.

Thanks.

Editing the CSS isn't the easiest thing to do. For now, it is probably best to stick with preformatted blocks.

Thanks.

I'm okay with torturing myself a bit just to learn how all of this works. Fedora Magazine is great and I believe making it better for readers is a step in the right direction.

If you want to give it a try, the documentation is under Technical Notes and Processes → Maintaining the Magazine Theme on the Fedora Magazine documentation site. Please submit patches in very small pieces though. I don't want to drastically overhaul the site in one big change at this time. Also, if we find a problem with some change such as that it doesn't render properly on mobile devices, it is better if we can revert just the small commit/change that is causing the problem than that we should have to revert the entire theme to an older version.

Thanks.

Wait... I just realized. This is the issue tracker for GitLab and not GitHub!

Edit: Renamed the title.

Alright, I made the thumbnail. What do you guys think?

It looks good to me. Thanks.

Feature image looks good to me. @theevilskeleton
Are the two logos Creative Commons or stated as available for use with out © copyright issues?

Can you check it for me? I got both logos from Wikipedia. The GitHub logo is under MIT and the Jekyll logo under CC BY SA I think.

I think these are OK. They are under the "Good Licenses" section here.

@theevilskeleton is this ready to go? If so, please go ahead and schedule it in WordPress to go out tomorrow. Don't forget to also move this card to the top of the scheduled column.

Thanks!

Metadata Update from @glb:
- Custom field publish adjusted to 2021-12-24

2 years ago

Metadata Update from @theevilskeleton:
- Custom field image-editor adjusted to @theevilskeleton
- Issue untagged with: needs-image

2 years ago

@theevilskeleton is this ready to go? If so, please go ahead and schedule it in WordPress to go out tomorrow. Don't forget to also move this card to the top of the scheduled column.

Thanks!

Done! Can you double check please?

@theevilskeleton Schedule looks good for 24 Dec 08:00 UTC.
Next step is to drag this card to the Scheduled column on the Kanban

Metadata Update from @theevilskeleton:
- Issue close_status updated to: scheduled
- Issue status updated to: Closed (was: Open)

2 years ago

Issue status updated to: Open (was: Closed)

2 years ago

@glb can you move the card? I'm using my phone right now and Pagure is really touch unfriendly.

Issue status updated to: Closed (was: Open)
Issue close_status updated to: scheduled

2 years ago

Login to comment on this ticket.

Metadata