# Publish your landing page

### 1. Enable GitHub pages

After pushing your latest changes, go to the project Settings > Pages

<figure><img src="/files/SLPYpPIfKKnfgHhYEK2u" alt=""><figcaption><p>Project settings > pages</p></figcaption></figure>

Once in the page settings, select a branch that will be the source of your page. In our case, we will choose `master`.

Now you can click on "visit site, and you will have your landing page hosted on GitHub servers For Free, Forever. No more paying 14€ to Wix or Squarespace for a simple landing page.

### 2. Add a custom Domain

If you want a professional landing page, We strongly suggest adding a custom domain, it's as easy as adding the custom domain on the GitHub page settings:

<figure><img src="/files/6iI60qKgQxygVtH0II09" alt=""><figcaption><p>Add a custom domain</p></figcaption></figure>

Et Voila, every time you modify your HTML and push to the GitHub repo, your website will get updated. 🤝

### Going Further

If you liked this simple boilerplate, check Lightning Rails, the best Ruby on Rails boilerplate to build SaaS web apps in no time.

{% embed url="<https://lightningrails.com>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lightningrails.com/getting-started/lightning-landing/publish-your-landing-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
