# Steps contributing the documentation

**URL:** <https://forum.liquibase.org/t/steps-contributing-the-documentation/4135>\
**Category:** Liquibase Development\
**Created:** [January 26, 2020, 8:45am UTC](https://forum.liquibase.org/t/steps-contributing-the-documentation/4135 "2020-01-26T08:45:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![un1382561729492r88id](https://avatars.discourse-cdn.com/v4/letter/u/c4cdca/32.png) [@un1382561729492r88id](https://forum.liquibase.org/u/un1382561729492r88id)\
**Post date:** [January 26, 2020, 8:45am UTC](https://forum.liquibase.org/t/steps-contributing-the-documentation/4135/1 "2020-01-26T08:45:00Z")

</div>

Thank you so much for your willingness to contribute! I very much appreciate the effort.

Steps 3-6 are not currently being handled by CI, it is something that we are doing manually on an as-needed basis.&nbsp;

Next steps for you would be to submit the PR to liquibase (against the 3.8.x branch) and mark it as a documentation fix. I will then make sure it gets moved though the system.

When I generate the documentation I will create a PR against the staging branch, where the results can then be previewed (there is a CI solution set up right now that publishes to [http://staging.liquibase.org/)](http://staging.liquibase.org/)) and then I typically merge from staging to master after a day or so, sometimes sooner. There is an automatic process at github to publish any changes pushed to master.&nbsp;

For changes in non-generated documentation, please make a PR that targets the staging branch of the [liquibase.github.com](http://liquibase.github.com) repository. I have been reviewing and approving and merging those as they come in.&nbsp;

Steve Donie  
Principal Software Engineer  
Liquibase Community Engagement  
Datical, Inc. [http://www.datical.com/](http://www.datical.com/)

---

<div class="post-metadata">

**Author:** ![un1382561729492r88id](https://avatars.discourse-cdn.com/v4/letter/u/c4cdca/32.png) [@un1382561729492r88id](https://forum.liquibase.org/u/un1382561729492r88id)\
**Post date:** [January 26, 2020, 8:45am UTC](https://forum.liquibase.org/t/steps-contributing-the-documentation/4135/2 "2020-01-26T08:45:00Z")

</div>

I see that you have submitted PR #964 -&nbsp;[https://github.com/liquibase/liquibase/pull/964/](https://github.com/liquibase/liquibase/pull/964/)

That is a big one, and it appears to alter behavior as well as documentation, so it might take me a while to get it reviewed and merged.&nbsp;

Steve Donie  
Principal Software Engineer  
Liquibase Community Engagement  
Datical, Inc. [http://www.datical.com/](http://www.datical.com/)

---

<div class="post-metadata">

**Author:** ![GyulaBibernth](https://avatars.discourse-cdn.com/v4/letter/g/9f8e36/32.png) [@GyulaBibernth](https://forum.liquibase.org/u/GyulaBibernth)\
**Post date:** [January 26, 2020, 8:45am UTC](https://forum.liquibase.org/t/steps-contributing-the-documentation/4135/3 "2020-01-26T08:45:00Z")

</div>

Hi,

I’m trying to contribute in the documentation also. If I understand correctly to change the documentation of a change like _loadData_ then the steps are:

1. Clone the _liquibase_ repository
2. Change the _description_ value of the repository?
3. Or the _\*.html_s shall be also generated further from the _\*.md_ files some way and committed? 

- Or it is done by some CI step? If not, shall the _bundle_ used for that?

What are the steps for other changes like changing _documentation\changeset.md_?

Thanks,

&nbsp;&nbsp;&nbsp; Gyula Bibernáth