Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
fabiovinci authored Apr 10, 2024
1 parent 33ebc4b commit 4843c48
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion how-to-report-new-CF/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ To report a new Country fiche for your Member State, please follow the instructi

* Fork the INSPIRE-in-your-Country repository (For more information, see "[Working with forks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks)").
* In the forked repository, create a new Markdown _.md_ file in the folder related to your country, e.g. _/INSPIRE-in-your-Country/AT/Country\_fiches/_ (For more information, see "[Creating new files](https://docs.github.com/en/repositories/working-with-files/managing-files/creating-new-files)"), with the following characteristics:
* the file name should follow the following naming structure "_<MS-code>-Country\_fiche-<Year>.md_", e.g. _AT-Country\_fiches-2024.md_.
* the file name should follow the following naming structure "_\<MS-code>-Country\_fiche-\<Year>.md_" (e.g. _AT-Country\_fiche-2024.md_).
* the document structure should follow the [country fiche template](https://raw.githubusercontent.com/INSPIRE-MIF/INSPIRE-in-your-Country/main/how-to-report-new-CF/Country_fiche_Template.md) (you can copy/paste the markdown syntax).
* Edit your new country fiche and commit your changes (For more information on the use of the Markdown syntax, see "[Basic writing and formatting syntax](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)"), in particular:
* make sure that links are encoded using the proper syntax, i.e. _\[link text](URL)_, otherwise, they are not converted as hyperlinks by GitHub pages.
Expand Down

0 comments on commit 4843c48

Please sign in to comment.