# Modify Gitea or build a new front

**URL:** <https://forum.gitea.com/t/modify-gitea-or-build-a-new-front/1934>\
**Category:** Install/Maintain/Configure\
**Created:** [February 18, 2020, 6:32am UTC](https://forum.gitea.com/t/modify-gitea-or-build-a-new-front/1934 "2020-02-18T06:32:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jiraiya](https://avatars.discourse-cdn.com/v4/letter/j/9fc348/32.png) [@Jiraiya](https://forum.gitea.com/u/Jiraiya)\
**Post date:** [February 18, 2020, 6:32am UTC](https://forum.gitea.com/t/modify-gitea-or-build-a-new-front/1934/1 "2020-02-18T06:32:08Z")

</div>

For my use case I found out that I need to change gitea more than playing with the template. I need to add routing and modify some of the code such as the “createReposotiry” function.

I can achieve the same If I create my own front and use gitea as a backend using the REST API. Part of the cost for doing that will be having to build the GUI for each part, basically recreating the whole interface while implementing my modifications.

I wish to hear your opinion: which of the two you recommend. Using Gitea’s front but changing some of the source code, or building my own front and using Gitea’s API.

---

<div class="post-metadata">

**Author:** ![jolheiser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/jolheiser/32/4807_2.png) [@jolheiser](https://forum.gitea.com/u/jolheiser)\
**Post date:** [February 18, 2020, 2:41pm UTC](https://forum.gitea.com/t/modify-gitea-or-build-a-new-front/1934/2 "2020-02-18T14:41:12Z")

</div>

Doing the latter (different front with same API) would likely be more future-proof, otherwise you’d need to merge upstream into your fork whenever we update.

That being said, what _is_ your use-case? We are always open to issues or PRs if the use-case makes sense for the core code. 🙂