Pages – What Features are Needed, Wanted or Nice to Have’s?
- This topic has 5 replies, 4 voices, and was last updated 5 months, 1 week ago by .
- January 24, 2020 at 5:10 am #1470TinyBatz
In a previous thread, the devs have agreed that Pages would be a great feature to smooth things over with new users and encourage further adoption and popularity of Publii. So lets get a clear idea of what that looks like. I’m not a web dev or serious coder so I’ll do my best to express what it is I am looking for in a Pages feature in Publii.
- There should be a separate section above Posts, in the same style but it lists all the Pages in the site.
- Pages should consist of a content area, with no title inherently attached to it the way that current Posts have (for example, I should be able to make a Page with no mandatory title viable at the top)
- Pages should not be inherently linked or related to each other the way that Posts are.
- Pages must be able to have embedded html (as current Posts can) so that I can embed an external contact form, etc.
- Pages must have their own unique URL so they can be addressed and linked to from other parts of the site.
It’s possible to get these things now through a series of workarounds and edits (except the “Page to Host your Blog” part) all I am asking for as far as I can tell is that these functions are streamlined for the end user, with a GUI, clickable buttons and clearly marked sections for Pages, not just posts. As far as I can tell (I ight be totally wrong here) but these are all relatively minor changes that shouldn’t affect the underlying deep structure of Publii in a huge, expensive or significant way, but will make a huge difference to usability.
- A Page that can function as a Blog page, so that you can have a website to look at then browse to a single page on that site where you keep your blog, as a single page, not the whole site.
Nice to Have
- Can’t think of anything.
Please keep all replies to this thread about the exact features you want to see in Pages, and not to discussing whether you think they are needed or not.January 24, 2020 at 11:12 am #1480Verhoeckx
I think that you first have to ask the following questions:
- What is a post (what are the attributes of a post) ?
- What is a page (what are the attributes of a page) ?
- What are the differences (which attributes differ)?
- What are the similarities (which attributes do they have in common)?
If you have the answers to those questions, you can start thinking about how to implement the pages. Maybe it’s good to make a domain model first.
ps: I only discovered Publii two week ago and it feels a little bit arrogant of me to say what Publii should do or shouldn’t do. I’m only expressing my thoughts based on my first impression.January 28, 2020 at 6:05 am #1529TinyBatz
I feel like I’ve done a pretty adequate job of explaining what I think on the subject up above. If anyone has anything to add, please comment on the thread and give your thoughts on what you want to see.January 28, 2020 at 6:20 am #1533ajeetJanuary 31, 2020 at 12:49 pm #1593andriezzo
As said before by other users and in other threads, there’s no need to have a “page” content type.
Content types are useful when there’s a different structure (fields) and view.
If you want to have a “page”, just exclude it from homepage and make it hidden. Disable post navigation and related post view. If you want to hide the title you can hide it via custom css or create a custom template for your theme. Maybe I’m wring, but I’ve seen a similar feature in the Meliisa theme available in the marketplace.
Hope it helps,February 1, 2020 at 9:46 am #1603TinyBatz
As also said before by other users – those steps are counterintuitive, difficult to find and utterly at odds with being a total beginner and wanting to build a simple website, not a blog. I’ve stated my ideas above, if anyone has anything useful or new to the conversation, I’d be very open to hearing about it, and hopefully that information can go towards helping to make Publii more total-beginner friendly.
- You must be logged in to reply to this topic.