# galaxy: reame formatting problems

**URL:** <https://forum.ansible.com/t/galaxy-reame-formatting-problems/20515>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [February 10, 2016, 4:00pm UTC](https://forum.ansible.com/t/galaxy-reame-formatting-problems/20515 "2016-02-10T16:00:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nusenu1](https://avatars.discourse-cdn.com/v4/letter/n/db5fbb/32.png) [@Nusenu1](https://forum.ansible.com/u/Nusenu1)\
**Post date:** [February 10, 2016, 4:00pm UTC](https://forum.ansible.com/t/galaxy-reame-formatting-problems/20515/1 "2016-02-10T16:00:36Z")

</div>

Hi,

there seems to be a problem with galaxy displaying READMEs, see:

[https://galaxy.ansible.com/nusenu/relayor/](https://galaxy.ansible.com/nusenu/relayor/)

vs

[https://github.com/nusenu/ansible-relayor](https://github.com/nusenu/ansible-relayor)

especially the sections:  
&nbsp;&nbsp;Requirements  
&nbsp;&nbsp;Available Role Tags

---

<div class="post-metadata">

**Author:** ![Chris\_Houseknecht](https://avatars.discourse-cdn.com/v4/letter/c/c57346/32.png) [@Chris\_Houseknecht](https://forum.ansible.com/u/Chris_Houseknecht)\
**Post date:** [February 10, 2016, 6:05pm UTC](https://forum.ansible.com/t/galaxy-reame-formatting-problems/20515/2 "2016-02-10T18:05:10Z")

</div>

GitHub’s markdown is a little more forgiving than Galaxy. Galaxy stores the raw README and translates to HTML on request. Galaxy also has its own CSS styles, so by definition what you see on Galaxy will be a little different.

We have been doing some work on the Galaxy styling of README files. Those changes will appear in release 2.0.1 scheduled to land on 2/26.

With the above in mind, if you indent sub-lists by 4 spaces, you should get the lists to appear the way you want. GitHub supports 2 spaces, where markdown proper requires 4. In the Requirements section, separate lists from paragraphs with a blank line. And finally, at the bottom of your README there is a numbered list, make sure each bullet has the correct number.

I forked your role, made the above minor changes and imported into our QA environment. You can see it here: [https://galaxy-qa.ansible.com/chouseknecht/relayor/](https://galaxy-qa.ansible.com/chouseknecht/relayor/)

–Chris

---

<div class="post-metadata">

**Author:** ![Nusenu1](https://avatars.discourse-cdn.com/v4/letter/n/db5fbb/32.png) [@Nusenu1](https://forum.ansible.com/u/Nusenu1)\
**Post date:** [February 10, 2016, 6:22pm UTC](https://forum.ansible.com/t/galaxy-reame-formatting-problems/20515/3 "2016-02-10T18:22:43Z")

</div>

Chris Houseknecht:

> GitHub's markdown is a little more forgiving than Galaxy. Galaxy stores the  
> raw README and translates to HTML on request. Galaxy also has its own CSS  
> styles, so by definition what you see on Galaxy will be a little different.
> 
> We have been doing some work on the Galaxy styling of README files. Those  
> changes will appear in release 2.0.1 scheduled to land on 2/26.
> 
> With the above in mind, if you indent sub-lists by 4 spaces, you should get  
> the lists to appear the way you want. GitHub supports 2 spaces, where  
> markdown proper requires 4. In the Requirements section, separate lists  
> from paragraphs with a blank line. And finally, at the bottom of your  
> README there is a numbered list, make sure each bullet has the correct  
> number.
> 
> I forked your role, made the above minor changes and imported into our QA  
> environment. You can see it here:  
> [https://galaxy-qa.ansible.com/chouseknecht/relayor/](https://galaxy-qa.ansible.com/chouseknecht/relayor/)

Great, thanks for fixing my README file!