Moving lektor-website into this repository

The Lektor website currently lives in its own repository. I’d like to streamline the commit process by moving it into this repository as a folder (website/). I think this has been discussed in other issues but I can’t seem to find any mention of it.

Why I think this is better:

• PRs can fix both documentation and code in one go which means documentation will always be in sync with the code
• Dogfooding Lektor master and ensure that Lektor master can build a decently sized site

What I propose:

• Export the lektor-website commit history verbatim into website/ (technically not verbatim since commit hashes will be rewritten, but close enough)
• Remove assets/static/ and let CI build it instead. We may want to prune this before importing to avoid growing the Lektor repository size
• Migrate to GitHub actions from Travis and auto-deploy
• Move issues from lektor-website to lektor
• Remove/archive lektor-website

[runfalk]

If we’re discussing hosting doesn’t it make the most sense to just use the GitHub provided one? You can have custom domain names for it.

[starworldx]

I agree with @runfalk , AWS is a rock solid option for web hosting but it would be nice to know if the Lektor site sees enough traffic and has long load times to justify expanding Lektor project infrastructure vs simplicity of GitHub pages. As an example, if most of our website visitors are repeat visitors coming back for documentation, we don’t risk of losing them as users if the site takes an extra second to load. Github pages still would likely be faster than what it is now.