-
Notifications
You must be signed in to change notification settings - Fork 169
Home
Milo is adobe.com's central codebase to power all adobe.com marketing sites.
If you're reading this, you likely want to contribute something. Depending on how familiar you are with Franklin or Milo, you can either start digging in now, or you can start learning about Franklin and what makes Milo special.
If you want to dig in right away, the best place to start is here: https://milo.adobe.com/first. This is a list of all issues we consider to be good first contributions. Be warned: some tickets may not have as much context as you need. Reach out to us in #milo-dev-onboarding in Slack.
Once you pickup a ticket, you can use the README of this project to understand how to start building something in Milo.
Franklin is a CMS built by Adobe. It is written from the ground up to be serverless and allow anyone to bring their own head. For adobe.com, we have chosen Microsoft Word.
Most Franklin sites are built as wholly separate projects. This is where Milo differs. Milo provides a centralized platform that lives on top of Franklin to help anyone build an adobe.com site. This includes analytics, seo, accessibility, authentication, design, and much more right out of the box.
Milo is a runtime dependency. This means that when a feature or fix is merged into main, all "consumers" get it immediately. This can take a bit of getting used to when contributing a feature. Often someone will contribute a feature while not having the full context of the entire Milo ecosystem. What may be good for one use case, may be bad for thousands of others.