# Fibery for solo projects/features

**URL:** <https://community.fibery.io/t/fibery-for-solo-projects-features/5771>\
**Category:** Get Help\
**Created:** [January 30, 2024, 12:00pm UTC](https://community.fibery.io/t/fibery-for-solo-projects-features/5771 "2024-01-30T12:00:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\
**Post date:** [January 30, 2024, 12:00pm UTC](https://community.fibery.io/t/fibery-for-solo-projects-features/5771/1 "2024-01-30T12:00:46Z")

</div>

Hi all, I’m looking for some feedback/opinions around structuring Fibery for solo projects. For context most of my work is in WordPress (making custom blocks, plugins, themes). I’ll also use Figma for creating mockups related to a dev project.

At the moment I have a few custom blocks that I’m working on. I’ve always tried to treat all work as projects → tasks. But what I find for development projects/tasks is that it feels really difficult to get to a state where you can confidently say something is DONE. It always feels like there are opportunities for improvement, new ideas, or a bug that’s waiting around the corner.

Instead of projects I’ve considered creating a separate database for “Assets”. This is where I would track things I’ve made that have the potential for improvements/ongoing support.

I’m curious how others think about this stuff in a solo context.

---

<div class="post-metadata">

**Author:** ![Karlitooo](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@Karlitooo](https://community.fibery.io/u/Karlitooo)\
**Post date:** [January 31, 2024, 6:09am UTC](https://community.fibery.io/t/fibery-for-solo-projects-features/5771/2 "2024-01-31T06:09:55Z")

</div>

One thing that’s helped a lot to get ideas out of my head and plan them later was building a “story map” view and capturing all my feature ideas into that.

Edit: [Here’s some examples of a story map](https://www.nickyconti.com/blog/a-story-about-story-mapping)

---

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [January 31, 2024, 6:13am UTC](https://community.fibery.io/t/fibery-for-solo-projects-features/5771/3 "2024-01-31T06:13:08Z")

</div>

Hmm, the other way could be to think of Releases for your Assets (or your Projects). That way, you could say a given Release entails the following improvements and then, once those are done, it’s done. 🙂

---

<div class="post-metadata">

**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\
**Post date:** [January 31, 2024, 11:53am UTC](https://community.fibery.io/t/fibery-for-solo-projects-features/5771/4 "2024-01-31T11:53:07Z")

</div>

It looks like I left out a detail at the top. I think I’m leaning in this direction.

Instead of Projects → Tasks, it would be Assets → Projects → Tasks.

Assets are meant to be stay around and not meant to be cleared or marked as done.

Projects/Releases would be the things to indicate that an asset has some work that needs done and will be done.

@Karlitooo I think story mapping will be helpful too.