# EPF Dev Update #6

**tl;dr:**

- Posted an [issue on the Trin repo](https://github.com/ethereum/trin/issues/855) to discuss the structure of the documentation.
- Picked a new project and started working on it.

## Structuring the docs

Two weeks ago, I published [my design for Ethereum node documentation](https://hackmd.io/@danielrachi/r1OL_QFhh). I mentioned in my [Update #5](https://hackmd.io/@danielrachi/HJ_O59ZTn) that I wasn't sure about what to do with it. I decided to start small and just create an [issue on the Trin repo](https://github.com/ethereum/trin/issues/855).

This is something that interests me, but not as much as my project. So for now, I'll just leave the issue there without doing more about it.

## First steps on my new project

When it was decided that I should change my project, Piper suggested that I should look into how we can serve beacon API data from the Portal Network. This would allow node operators to only have to run a Portal Node and a Consensus Layer Client.

I really liked the idea, so I started working on my new proposal right away.

I decided to take a slightly different approach to writing my proposal this time: I'll write a series of articles that I will later compile into my project proposal.

So far, I've written:

- [**Serving Engine API Data from the Portal Network: Evaluation**](https://hackmd.io/@danielrachi/BkgGB9Qa2). This will serve as the _motivation_ section of the proposal.
- [**Serving Engine API Data from the Portal Network: Initial Ideas**](https://hackmd.io/@danielrachi/B1Bd4jF6n). This will serve as the _specification_ section of the proposal.

One of the things I asked Piper during the AMA really helped me evaluate my motivation for the project. I want to leave it here for future reference: