Content for Fedora Developer Portal
Project Page | First Milestone | How To Contribute
How To Create a Content
- Read our contribution guide about writing a content
- Learn about markdown syntax
- Create new or modify existing files with content
How To Test Your Changes
You can easily review the markdown formatting directly on Github but if you want to see how your changes look in context of the whole website, you might want to take a look at the Website repository and run a local instance of the portal.
Structure
The website would consist of several sections. Each section would contain a set of pages. Each content file must start with initial section in YAML syntax describing the title and where the file belongs.
An Example for DevAssistant
Every file except the main page would start with:
---
title: Some Title # This title is shown in menus
page: devassistant # This is an ID of your content (select value from the list below)
order: 1 # Optional - order in menu
---
The main page would contain:
---
title: DevAssistant # This title is shown in menus
page: devassistant # This is an ID of your content (select value from the list below)
section: tools # This page would be linked from the main menu in a group called tools (select value from the list below)
description: Lorem ipsum... # a short description to be shown in the section menu
---
Section and Page Names
First level is a section id. Second level is a page id.
Start
- start-sw
- web-app
- cli-app
- gui-app
- mobile-app
- start-hw
- raspberry-pi
- arduino
- embeded-devices
- start-tips
- collaborate
- documentation
Tools
- tools
- devassistant
- docker
- vagrant
Technology
- tech-languages
- python
- ruby
- php
- perl
- go
- c
- nodejs
- java
- tech-database
- postgre
- mariadb
- sqlite
Deployment
- deployment
- copr
- scl
- nulecule
- xdgapp
- rolekit
- openshift
- fedoranext
- fedoranext