This group's mission is to enable Frontend developers to build, deploy and manage externally facing, static websites using Jamstack architecture in a simple, configurable and scalable way.
Frontend engineers should be able to use GitLab as the primary place to manage Jamstack Frontends.
I am currently working on simplifiying the Pages onboarding experience. To do so, I am integrating the Pipeline Wizard in the Pages UI.
This was a dependency of https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78276, which is next to be merged
In that MR, I made some new changes compared to last week:
public. Ultimately I'd like to remove that behavior, but this is an MVC
If a project has never been set up for pages before, the user is presented with the onboarding wizard (this uses the Pipeline Wizard)
See the "Weekly Update" Epic for a list of all prior updates.
Technology supporting Jamstack is a fast-growing, highly innovating field with many startups competing for market shares.
GitLab's solution is built on GitLab Pages and its solid CI/CD pipelines. This allows any client to grow seamlessly from a simple static site to complex, multi-faceted deployments without having to change the provider at any point. Competing in the Jamstack market potentially allows new Developers to have a shallow entry to GitLab's CI/CD world. That is, if we get the User Experience right.
GitLab is not an infrastructure provider. This is an advantage for established clients that may already pay for their own infrastructure. GitLab can easily support a wide range of infrastructure using CI/CD pipelines, so our goal is to make this as simple as possible. It's important that this scalability is conveyed from the very first onboarding steps to build trust with our users, even if most projects will stay small.
Gitlab’s strength is everything-can-be-configured. Gitlab is the Linux of Deployment platforms: Open-source, adaptable, transportable. So Gitlab should be the go-to platform for Jamstack Apps that not only want the whole project lifecycle in one place, but especially those that have non-default needs like onsite-hosting, support for large, complex sites or the need for fine grained control over the intricacies of the deployment.
Improving the UX/Frontend of Gitlab Pages. The GitLab Pages backend is of very high quality, but the frontend is very basic and does not convey that level of quality and reliability. This is a phase where we catch up on functionality offerings to established alternatives. Although Gitlab’s strengths in the Jamstack space don’t revolve around the single-FE-Developer Persona, we still need to get this experience right to build trust.
Once the catch-up phase has seen some progress, we can demonstrate GitLab's capabilities by publishing Blogposts about:
Sidetrack: Git-as-CMS. Git is actually a great tool for Content Management beyond Code: It has collaboration features, version control, access management, interfaces. Editing source files directly is also a great oportunity to have editors and developers collaborate seamlessly. Still, for a successful experience, there needs to be a UI that's designed for the editor persona and is independent of the Git Platform.
There are already solutions available that do this (i.e. NetlifyCMS, Forestry, Tina), both headless and fullstack, but the options are sparse. The Jamstack SEG should explore whether there is space for an additional framework:
The idea is to provide a FOSS-, developer-friendly full-stack alternative to Wordpress with static builds for high availability and high performance with a modern stack (e.g. Vue/Vite, or Svelte/Astro).
The key focus areas for the Jamstack SEG are:
.gitlab-ci.yamlpowering the solution, it should be straightforward to support a wide range of deployment strategies.
All frameworks have in common that there are three main approaches as to when the rendering happens: