# Taking over existing Sage project (Missing info?)

**URL:** https://discourse.roots.io/t/taking-over-existing-sage-project-missing-info/20292
**Category:** sage
**Tags:** sage8
**Created:** 2021-03-06T13:24:54Z
**Posts:** 3

## Post 1 by @flipnotic — 2021-03-06T13:24:55Z

Hey friends,

I’ve been tasked take over an existing Sage theme to make some customizations, but I may have hit a small wall. The theme appears to be Sage8 since it was built in 2016. Luckily I have the **assets** folder intact, but the root folder has no `composer.json`, `bower.json` or `package.json` file.

When bringing the theme to a development server and running the `composer install` and `yarn` commands, the frontend of the site just returns a white page of death, with no fatal errors (nothing in the logs as well)

Any ideas on how I can get this running? I don’t have access to the previous agency, or GitHub repo

---

## Post 2 by @strarsis — 2021-03-06T13:33:51Z

Is there still a `CHANGELOG.md`?

As a starting point, the Sage releases from 2016:

> **[roots/sage](https://github.com/roots/sage/tags?after=9.0.0-beta.1)**
>
> WordPress starter theme with a modern development workflow - roots/sage

Sage 8.x: [https://github.com/roots/sage/tree/8.5.0](https://github.com/roots/sage/tree/8.5.0)  
Sage 9.x (was still alpha in 2016): [https://github.com/roots/sage/releases/tag/9.0.0-alpha.4](https://github.com/roots/sage/releases/tag/9.0.0-alpha.4)

You can then try to use the `composer.json`; `composer.lock`; `package.json`; `yarn.lock` and other “glue” files (Gulp was used in 8.x; webpack in 9.x) for your own theme.

---

## Post 3 by @flipnotic — 2021-03-06T13:35:22Z

Negative on the `changelog.md` unfortunately.

Those GitHub links look like a great place to start! I’m going to try that in a few minutes and report back

Thanks a ton!

---

## Post 4 by @system — 2021-04-17T13:24:56Z

This topic was automatically closed after 42 days. New replies are no longer allowed.