Yes 100%. I actually built and maintain a GitLab pages website and CLI tool that are both wrappers around the GitLab api to parameterize and trigger pipelines on behalf of my teammates. In order to do this on the GitLab pages side, we need a few things: Create a GitLab application in Preferences -> Applications, and configure it to allow OAUTH and whichever permissions you need for yourself/teammates. Set the website up to login with OAUTH to get an access token for the user that logged in Using that access token, you can now access the GitLab API and can use it to call the GitLab triggers api endpoint. Given you mention Hugo, you'll need to write your own JavaScript modules to handle the API calls and letting the user know about success/failure statuses. One simple way is to have your inputs all within a ``, and then intercept the submit call, make the API call to trigger your GitLab pipeline, and then open the running pipeline page in a new tab (part of the Trigger pipeline response). Another Consideration: - Since GitLab pages can be protected behind private organizations (i.e. GitLab will protect your site from anyone who doesn't have access to your GitLab account), you can skip the OAUTH part and create an AccessToken that you deploy with the site. The access token can be used to call the GitLab API directly without having people login. This solution assumes some familiarity with JavaScript, web technologies, and authenticated web apps/apis. Let me know if you need help with any of these!

Check the response for the X-Total-Pages header. As long as page is smaller than total pages, you have to call the api again and increment the page variable. https://docs.gitlab.com/ee/api/rest/index.html#pagination-link-header