# Quickest and easiest way to start a Tree

**URL:** <https://gramps.discourse.group/t/quickest-and-easiest-way-to-start-a-tree/7123>\
**Category:** Help\
**Tags:** novice\
**Created:** [February 27, 2025, 8:28pm UTC](https://gramps.discourse.group/t/quickest-and-easiest-way-to-start-a-tree/7123 "2025-02-27T20:28:19Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![bjc49](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/bjc49/32/316_2.png) [@bjc49](https://gramps.discourse.group/u/bjc49)\
**Post date:** [March 1, 2025, 4:53pm UTC](https://gramps.discourse.group/t/quickest-and-easiest-way-to-start-a-tree/7123/15 "2025-03-01T16:53:22Z")

</div>

As I explained in the following post:

> [@Interface graphique (GraphView)](https://gramps.discourse.group/t/interface-graphique-graphview/6977):
>
> Au risque de me répéter Âprès plus de 10 ans d’utilisation du logiciel Gramps avec une courbe d’apprentissage plus ou ardue , il m’arrive de penser aux nouveaux utilisateurs. A mon avis la vue Graphview me semble la plus intuitive : on voit ce que l’on fait. A partir d’elle on peut faire beaucoup de choses a partir de menus contextuels(enrichis par Serge Noiraud notamment, la barre de recherche est performante, les signets permettent de revenir sur l’individu objet d’une recherche,…) et plus …

The most user-friendly approach is to use the **Graphview** + **Combined view** pair  
In particular for its interactivity, we see what we are doing and thus protect ourselves from erroneous entries  
The **Recent Item** plugin is also of immense service for repetitive entry, especially if we want to give the source of all the events entered  
This is my personal practice

---

_[View the full topic](https://gramps.discourse.group/t/quickest-and-easiest-way-to-start-a-tree/7123)._