PFT::Tree(3)

💖 PFT::Tree 💖

okay so bestie, welcome to PFT::Tree — the User Contributed Perl Documentation entry that maps out your whole PFT site like a filesystem tree. it's giving directory realness, and honestly? obsessed. 🦋

---

✨ NAME ✨

PFT::Tree — a filesystem tree mapping a PFT site 🌸

---

🎀 SYNOPSIS 🎀

PFT::Tree->new();
PFT::Tree->new($basedir);
PFT::Tree->new($basedir, {create => 1});

that's it, that's the whole vibe. three ways in, pick your fighter 💅

---

🦋 DESCRIPTION 🦋

so the structure is literally this, no cap:

├── build
├── content
│   └── ...
├── inject
├── pft.yaml
└── templates

and here's the tea on what's what:

• content is a directory, and it gets handled with a PFT::Content instance. 👑
• pft.yaml is a configuration file, handled with PFT::Conf. ✨
• the remaining directories? they just get created, periodt. the content is not handled by the PFT::Tree structure. so don't come for them expecting magic 🙈

🌸 Properties 🌸

💜 dir_content

💜 content

returns a PFT::Content object, which is basically the bouncer abstracting all your access to the content directory. 🎀

💜 map

returns a PFT::Map object, abstracting the the content graph. (yes, the double "the" is in the original, we love a typo that ate 💀)

💜 conf

returns a PFT::Conf object, abstracting the configuration file. main character energy fr fr 🔥

---

💀 POD ERRORS 💀

hey! the above document had some coding errors, which are explained below. not me exposing the author like this 😭

Around line 108:

You forgot a '=back' before '=head2'

yeah bestie, =back was right there. it happens to the best of us 🫶

---

so that's the whole page!! this one's from perl v5.42.0, dated 2025-07-25, and honestly it was iconic of you to read all the way down here. slay, drink water, go build your tree 💖✨🌈