https://github.com/zowe/zowe.github.io
Zowe.org website development
https://github.com/zowe/zowe.github.io
Last synced: about 1 year ago
JSON representation
Zowe.org website development
- Host: GitHub
- URL: https://github.com/zowe/zowe.github.io
- Owner: zowe
- License: cc-by-4.0
- Created: 2018-09-22T01:44:52.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2025-05-06T14:49:02.000Z (about 1 year ago)
- Last Synced: 2025-05-06T15:56:08.335Z (about 1 year ago)
- Language: HTML
- Homepage: https://zowe.org
- Size: 29.1 MB
- Stars: 13
- Watchers: 7
- Forks: 35
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Security: security.md
Awesome Lists containing this project
README
[](https://app.netlify.com/sites/condescending-dubinsky-4645a9/deploys)

# Welcome to Zowe website development
This GitHub repo is for management of the Zowe website. It uses [Github Pages](https://pages.github.com/) to automatically publish any commits to the master branch of the repo to https://zowe.org. GitHub Pages uses [Jekyll](https://jekyllrb.com/) to publish this site from the content in your markdown files in this repo. For more details see [GitHub Flavored Markdown](https://guides.github.com/features/mastering-markdown/).It is important to note that the links and content within the .md files require preprocessing and publication on zowe.org before they become fully functional. Attempting to access these links directly from the repository will render them non-operational.
## Site organization
Most site updates can be made without changing the markdown files, but adjusting the [config settings](_config.yml). This includes doing new releases and changing the URLs to other resources.
The primary page content is in [index.md](index.md). The overall layout is in [_layouts/default.html](_layouts/default.html), and css and image files are in [assets](assets).
### Doing a new release
To do a new release, add a new entry at the top of [releases.yml](_data/releases.yml) right under the contents with this structure:
```yaml
- version: 1.4.0 # version number
release_notes: https://zowe.github.io/docs-site/latest/getting-started/summaryofchanges.html#version-1-4-0-august-2019 # link to release notes
release_date: 2019-08-09 # release date in YYYY-MM-DD format
documentation: latest # path to docs ( minus the site url of https://docs.zowe.org )
```
### Add an announcement
To add an announcement, add an entry like below in [announcements.yml](_data/announcements.yml):
```yaml
- announcement: This is my announcement
link: https://linktomyannouncementcalltoaction.org
```
### Add upcoming events
Events are not supposed to be added/modified manually, since they directly get synced with the [OMP events calendar](https://www.openmainframeproject.org/events/category/zowe) and updates only when the response of [ICS feed](https://www.openmainframeproject.org/events/category/zowe?ical=1&tribe_display=photo) changes through a PR by GitHub action.
The events are dynamically fetched from an [ICS feed](https://www.openmainframeproject.org/events/category/zowe?ical=1&tribe_display=photo) and parsed into the [upcoming_events.yml](_data/upcoming_events.yml).
If needed, the [upcoming_events.yml](_data/upcoming_events.yml) can be manually updated by running `cd _data` and `python ics-to-yml.py` locally from the root directory.
## Submitting site updates
Any site updates can be submitted as a pull request. We recommmend you [create a fork](https://help.github.com/en/articles/fork-a-repo) of this repo and make changes there so you can preview them using GitHub Pages on your GitHub account. You can also develop locally with the following steps:
* [Set up Jekyll on your computer](https://jekyllrb.com/docs/installation/)
* Run `bundle install` to install the GitHub Pages gem
* Run `bundle exec jekyll serve` to host the site locally (at `http://localhost:4000`)
This repo aligns with the general [Zowe project role definitions](https://github.com/zowe/zlc/blob/master/process/roles.md) and [License and Copyright guidance](https://github.com/zowe/zlc/blob/master/process/LicenseAndCopyrightGuidance.md)
Note: If your build script, after applying changes & doing a reload, is yielding an incorrect-looking UI, you could automate the closing & restarting of the script. Something like in Bash, `while true; do timeout 25s bundle exec jekyll serve; done`
## Governance
Committers to this repo are defined in the [COMMITTERS.csv](COMMITTERS.csv) file. You can request to the committers to become a committer after having successful commits to this repo. Committers are approved by an affirmative vote of the majority of committers.
# Questions and feedback
You can direct questions about the website to the Zowe ZLC [via email](https://lists.openmainframeproject.org/g/zowe-zlc) or on [Slack](https://slack.openmainframeproject.org).