|
| 1 | +# osusec.github.io |
| 2 | + |
| 3 | +The source code for [www.osusec.org](https://www.osusec.org)! |
| 4 | + |
| 5 | +We recently migrated from Wordpress to the static Hugo site you see now; if you see a bug, please let us know in Issues! |
| 6 | + |
| 7 | +## Adding a blogpost |
| 8 | + |
| 9 | +Blogposts and any other content to the website is written in Markdown. Here is [a Markdown Cheatsheet](https://www.markdownguide.org/cheat-sheet/) if you need it! |
| 10 | + |
| 11 | +### Clone the repo and create a branch |
| 12 | + |
| 13 | +```sh |
| 14 | +git clone [email protected]:cacama-valvata/osusec-hugo.git |
| 15 | +git checkout -b BRANCH_NAME |
| 16 | +git push --set-upstream origin BRANCH_NAME |
| 17 | +``` |
| 18 | + |
| 19 | +### Have Hugo installed |
| 20 | + |
| 21 | +Hugo is available in many [package repositories](https://gohugo.io/installation/linux/#repository-packages), as a [Docker](https://gohugo.io/installation/linux/#repository-packages), or as [prebuilt binaries](https://gohugo.io/installation/linux/#prebuilt-binaries). Choose one and open a terminal! |
| 22 | + |
| 23 | +### Create new .md file |
| 24 | + |
| 25 | +From the project's root directory, run |
| 26 | + |
| 27 | +```sh |
| 28 | +hugo new content/blog/BLOGPOST_NAME_HERE.md |
| 29 | +``` |
| 30 | + |
| 31 | +Hugo will prevent you from creating a blogpost with a title that already exists for a previous blogpost. Make sure that the title you're choosing is descriptive! The title should also be in all lowercase, with spaces replaced with hyphens. See other files in the `content/blog/` folder for examples. |
| 32 | + |
| 33 | +This will create the new blogpost file with certain 'default' information already written. To start writing: |
| 34 | + |
| 35 | +1. Hugo will intuit your title from the URL you provide it. Edit this if need be to fix capitalization and include special characters. |
| 36 | +2. Add your name to the `author` field. |
| 37 | +3. Add a category (or more!) to the `categories` array. This will be array of strings like `['Club News', 'Meeting News']`. See below for a full list of available categories. |
| 38 | +4. Add tags if appropriate (many other posts on the same topic, etc). Feel free to be creative. |
| 39 | +5. If including a picture, provide a caption for the picture. |
| 40 | +6. Write all content below the final `---` that denotes the file's metadata. |
| 41 | +7. When ready, set the `draft` field to `false`. |
| 42 | + |
| 43 | +### Commit it, push it, and open a PR! |
| 44 | + |
| 45 | +Once finished with the blogpost, commit it: |
| 46 | + |
| 47 | +```sh |
| 48 | +git add content/ static/ |
| 49 | +git commit -m "added blogpost BLOGPOST_NAME" |
| 50 | +git push |
| 51 | +``` |
| 52 | + |
| 53 | +Navigate to your branch in Github, and create a Pull Request by clicking `Contribute` > `Open pull request`. Verify that it is merging into `base: master` and hit `Create pull request.` Finally, let other officers know in Discord that you have an open PR to be reviewed and published. |
| 54 | + |
| 55 | +#### Blogpost Categories |
| 56 | + |
| 57 | +| Category Name | Purpose | |
| 58 | +|---------------|--------------------------------------------------------------------------------------------------------| |
| 59 | +| Meeting Notes | Summaries of weekly general meetings. Include links to slides and announcements for next week. | |
| 60 | +| Club News | Announcements of recent accomplishments, summaries of non-meeting activities, or other special events. | |
| 61 | +| Writeups | Writeups by club members of recent CTF Challenges they completed, explaining how they solved them. | |
| 62 | +| Uncategorized | Posts that don't fall into any of the other categories, such as a post used as material for a CTF. | |
| 63 | + |
| 64 | +#### Including photos |
| 65 | + |
| 66 | +For "featured photos" that show as the title's background of the post itself, the website will look for JPG files that share the same URL as the post itself. For example, for the post `/blog/nsa-visit/`, the website will be looking for `/blog/nsa-visit.jpg`. The caption for this image will be set in the `caption` field in the `.md` file's metadata. |
| 67 | + |
| 68 | +For non-featured photos, the URL can be anything you want, as you will specify it yourself in the markdown. For cleanliness, keep the image names as "extensions" of the original blog URL. For example, for `/blog/nsa-visit/`, use the URL/name of `/blog/nsa-visit-extra-image.png`. Include a caption with the image for accessibility. |
0 commit comments