Skip to content
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

Checklist for publishing a post to CCISEL Blog #38

Open
fmcarvalho opened this issue Nov 11, 2020 · 2 comments
Open

Checklist for publishing a post to CCISEL Blog #38

fmcarvalho opened this issue Nov 11, 2020 · 2 comments

Comments

@fmcarvalho
Copy link
Contributor

fmcarvalho commented Nov 11, 2020

This guide assumes that you have an updated local copy of CCISEL https://github.com/CCISEL/ccisel.github.io

  1. Copy paste one of the post files located in ccisel.github.io\_posts

  2. Rename it accordingly and keep the prefix date such as yyyy-mm-dd-your-title.md. Title in lower case, with no spaces and using - instead.

  3. Create an image in the folder ccisel.github.io\assets\blog with the same name of the post filename (excluding the suffix, off course). E.g. yyyy-mm-dd-your-title.png

  4. Review your post file created on step 2 and fill all mappings, including title, image, date, etc

  5. Run Jekyll with Jekyll serve or with docker through the script docker-serve.sh and check it on http://localhost:4000/.

  6. Your post should appear in the carousel of the main page and also in http://localhost:4000/news/

  7. If everything is right then: a) commit it to a new branch e.g. blog-post-title; b) push it to Github; c) create a Pull Request from your branch blog-post-title to ccisel.github.io/tree/master

  8. Wait at least for 1 review before merging your Pull Request.

@pmhsfelix
Copy link
Contributor

LGTM. Perhaps add the requirement for opening a PR and have at least one review before merging into master.

@fmcarvalho
Copy link
Contributor Author

LGTM. Perhaps add the requirement for opening a PR and have at least one review before merging into master.

DONE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants