Make a wish

do you mean a content management system for writing blog entries, uploading images, and creating pages? we currently do not have an "all in one" script for that, but you can use dannys Sitemanager to create php pages, or use the Simple Uploads Companion together with one of the add-ons depending on your content type (images, designs, downloads).

aw, thank you! we're actually constantly adding more. is there anything specific you're missing at the moment? <3

hey! is your calendar in a folder? ☺️ if your advent calendar script is in a folder and your header/footer files are somewhere else, you have to adjust the path in your config. I hope it's okay if I write a mini tutorial here directly, because normally (when not in a folder), the script just picks the files automatically.

the reason why it doesn't work for you is probably because the server starts looking from the directory of the current file.

so, for example, if your script is in a folder like event/adventcalendar.php, the server expects the header file in the event folder. you need to tell the server how to move to the correct location. this is kinda a general rule for most php scripts actually, just a tip for the future! ☺️

example 1: header and footer files are outside of the script folder, "one folder back":
📁 home
  ├─ 📄 header.php
  ├─ 📄 footer.php
  └─ 📁 event
          └─ 📄 adventcalendar.php

__DIR__ . '/../header.php'

the .. means 'go up one folder' in the server directory hierarchy.

example 2: header and footer files are two folders back:

📁 home
  ├─ 📄 header.php
  ├─ 📄 footer.php
  └─ 📁 event
          └─ 📁 advent
                  └─ 📄 adventcalendar.php

then you need to go up two folders:

__DIR__ . '/../../header.php'

each ../ steps up one directory.

also, when your header and footer files (and your css) are outside of the script folder, image paths in your css usually need to start with / so the server loads them from the root and not from inside the script folder. for example:
background-image: url('/images/snow.png');

also just a small tip: it's usually easier not to put php scripts deep inside nested folders, because paths can start acting unpredictable really fast.

but the solution above should fix your issues! I hope this helps! feel free to contact me if you need help. ✨

hi matt! you can actually turn any design into a wordpress starterkit if you want to, by using our split tool! ☺️ if you prefer an official blank theme instead, there's one called 'underscores', and it creates a blank theme with all the required core files: underscores.me

a more recent starter theme by automattic is 'blockbase', which supports the latest block-based features in wordpress. personally, i am not a big fan of those. i still prefer the old-school approach like underscores.

maybe i will make my own templates in the future, but i don't personally work with wordpress anymore (and neither does danny). wordpress has shifted heavily toward block-based editing and gutenberg, which i am just not really into. 🥲