Since Fedora supports secondary arches. It would be nice to have a some notes about it.
Would it be possible to write a some notes?

I will contact our secondary arches team.

We need to provide a docker content for developer so that they can play with docker on Fedora.

• How to install it
• how to create a docker file
• how to create a image
  .....

I think that there should be a section about Sphinx as the most commonly used documentation generator for Python.

In a case that someone is already working on this, please let me know. Otherwise I will start to work on this.

There is a nice how-to setup for Drupal, that I've just fixed to be working on Fedora 23:
https://fedoraproject.org/wiki/How_to_install_Drupal

I'm thinking now how to connect that wiki page with the developer portal, if that is something we want to do at all. What I was thinking about was to create a new category on developer portal, under: Technology called "Applications". That would be place to include short how-tos for things like wordpress, drupal, joomla, etc. After that the wiki page above would be removed and only a link to developer portal would be used.

What do you think? Or is it totally out of scope of developer portal?

I think personaly, that if user creates a daemon, service etc. then it will need a some information about systemd and how to start it.

I think that we should cover it by some short information with references to this page.
https://wiki.freedesktop.org/www/Software/systemd/

I don't know where it belongs to. "start" or "tech"?

Some headlines are camel-cased, some not. We should use just one style.

e.g. My Headline About Something
vs My headline about something

I prefer the latter.

Fedora is a good and popular development platform for Gtk+ and Qt development. Writing GUI applications in these toolkits involve knowledge of tools, languages, and guidelines.

I suggest adding a Desktop section with articles such "Writing a Hello World application in gjs" (gjs is gnome javascript, the language we focus on for newcomers). I am willing to contribute with this introductory article for Gtk + gjs.

We include a list of Ask.Fedora links to relevant labels where it make sense. Perhaps with an Ask.Fedora logo on the site.

It would be nice to have possibility to show images in the content. It doesn't make much sense for programming languages and CLI stuff, but in some cases it might be fine:

1. Showing image with end result as a motivation (I am working on Sphinx tutorial, and I think screenshot of some documentation would be nice)
2. Showing some GUI/Web tool (From current content it can be DevAssistant and Copr)
3. ...

As discussed at Fedora E&S meeting on July 16, this would be aimed at helping to guide developers packaging different kinds of applications to appropriate packaging tools (Nulecule, xdg-app-, software collections)

As we talked on Environment & Stacks WG meeting

http://meetbot.fedoraproject.org/fedora-meeting-2/2015-07-30/env-and-stacks.2015-07-30-12.00.html/

There should probably be some "rules" enforced during content addition.

1. Every section should have editor - i.e. subject matter expert has to review all content changes for the given section
2. Before starting work on a specific topic, issue has to be created and draft should be linked from this issue so that editors and others can review and comment the draft early
3. Every content change needs to be proposed as a Pull Request and needs to get LGTM from two editors (if the PR submitter is also an editor, only one LGTM from another editor is ok to merge)

I guess, at least in the beginning, it will be hard to get editors for all the content, but it should definitely be one of the goals.

Fedora 23 Feature set should be a part of content.

Later on Features since F22 should be created too.

I couldn't find a link from the Portal back to this repo. Perhaps there could be an "About" page or similar that describes how to report problems and contribute fixes?

The new RPM Packaging guide is great, but in many cases folks can generate a decent starting SPEC file from upstream metadata, rather than having to start from scratch. Two tools I'm aware on that front:

• Python: pyp2rpm (by Slavek Kabrda & Robert Kuska)
• Perl: cpanspec

I assume similar tools exist for at least some other language ecosystems, I'm just not aware of them personally.

In terms of structuring this, the layout that makes sense to me would be to have:

1. An RPM Packaging section in the relevant language page that describes how to use the SPEC file generator, and then links to the main RPM Packaging guide
2. A summary section in the main RPM Packaging guide that lists the languages with SPEC file generators and links to the appropriate section on the language page

If that layout seems reasonable, I'd be happy to put together a PR using Python and pyp2rpm as the initial example.

Content should point out to devassistant.org

Guides such as https://fedoraproject.org/wiki/How_to_debug_Virtualization_problems can be very helpful in debugging libvirt and should be linked from vagrant content.

We need to provide a vagrant content for developer so that they can play with vagrant on Fedora.

To be shown in menu and in the header as well.

https://raw.githubusercontent.com/developer-portal/mockups/master/Mockups/details-page_1.0.png

I would sort it alphabetically.