|
1 | | -# project-ocre.github.io |
| 1 | +# Ocre Documentation |
2 | 2 |
|
3 | | -Will update soon |
| 3 | + |
| 4 | +## Overview |
| 5 | +This repository contains the documentation for [Ocre](https://lfedge.org/projects/ocre/). This repo hosts the code for the Ocre docs site, which is separate from the main Ocre project repository. |
| 6 | + |
| 7 | +The live version of the documentation can be viewed at [https://example.com](https://example.com). |
| 8 | + |
| 9 | +## Project Structure and Contribution Guidelines |
| 10 | +This documentation site was built using [Jekyll](https://jekyllrb.com/) and the [Just the Docs theme](https://just-the-docs.com/). |
| 11 | + |
| 12 | +### Project File Structure |
| 13 | +``` |
| 14 | +. |
| 15 | +├── _docs/ # Documentation files (Markdown format) - main focus for contributors |
| 16 | +├── assets/ # Contains images, scripts, and other static assets |
| 17 | +├── _config.yml # Site configuration file |
| 18 | +├── Gemfile # Ruby dependencies for Jekyll |
| 19 | +├── Gemfile.lock # Version lockfile for dependencies |
| 20 | +├── README.md # The file you are reading right now |
| 21 | +└── _site/ # Auto-generated, do not edit directly (site build output) |
| 22 | +``` |
| 23 | + |
| 24 | +### Key Guidelines for Contributors |
| 25 | +* **Documentation Location:** All content related to Ocre’s documentation lives in the `_docs` folder. If you're contributing, focus your efforts here. |
| 26 | +* **Editing Scope:** Contributors (who are not maintainers) should avoid editing files outside the `_docs` folder. The rest of the structure is primarily for configuration and assets that support the documentation. |
| 27 | +* **Assets:** Any images, scripts, or styles related to the documentation should be placed in the assets folder. When adding images, make sure to reference them correctly in your Markdown files. |
| 28 | + |
| 29 | +This structure and these guidelines help ensure the integrity and maintainability of the Ocre documentation site while allowing contributions to focus on content updates. |
| 30 | + |
| 31 | +## Getting Started |
| 32 | + |
| 33 | +### Prerequisites |
| 34 | + |
| 35 | +Ensure you have the following installed on your system: |
| 36 | + |
| 37 | +| Software | Version | |
| 38 | +|----------|---------| |
| 39 | +| Ruby | ≥ 3.3.2 | |
| 40 | +| Bundler | ≥ 2.5.4 | |
| 41 | +| Jekyll | ≥ 4.3.0 | |
| 42 | + |
| 43 | +### Setup and Local Development |
| 44 | + |
| 45 | +We encourage contributions to improve the documentation! If you’re looking to update or add content, follow these steps: |
| 46 | + |
| 47 | +1. Fork the repository on GitHub. |
| 48 | +2. Clone your forked repo |
| 49 | + ```bash |
| 50 | + git clone https://github.com/your-username/project-ocre.github.io.git |
| 51 | + cd project-ocre.github.io |
| 52 | + ``` |
| 53 | +3. Install dependencies. |
| 54 | + ``` |
| 55 | + bundle install |
| 56 | + ``` |
| 57 | +4. Create a new branch for your changes. |
| 58 | + ```bash |
| 59 | + git checkout -b feature/your-feature |
| 60 | + ``` |
| 61 | +5. Make your changes. Rembmer to focus on the `_docs` folder for content updates. |
| 62 | +6. Preview your changes locally by running: |
| 63 | + ```bash |
| 64 | + bundle exec jekyll serve |
| 65 | + ``` |
| 66 | +7. Open your browser and visit http://localhost:4000 to see your changes. |
| 67 | + |
| 68 | +8. Once satisfied with your changes, commit them: |
| 69 | + ``` |
| 70 | + git add . |
| 71 | + git commit -m "Brief description of your changes" |
| 72 | + ``` |
| 73 | + |
| 74 | +9. Push your changes to your fork: |
| 75 | + ``` |
| 76 | + git push origin feature/your-feature-name |
| 77 | + ``` |
| 78 | + |
| 79 | +10. Go to the main [Ocre docs repository](https://github.com/project-ocre/project-ocre.github.io) and submit a pull request with a clear description of your changes. |
| 80 | + |
| 81 | +We'll review your contribution and get back to you as soon as possible. Thank you for helping improve the Ocre documentation! |
| 82 | +
|
| 83 | +## License |
| 84 | +
|
| 85 | +[Your license information] |
| 86 | +
|
| 87 | +## Contact |
| 88 | +
|
| 89 | +If you have any questions, feel free to [reach out](https://lfedge.slack.com/archives/C07F190CC3X) on Slack or open an issue for discussion. |
0 commit comments