Hi, currently, I’m developing my first project with kirby. Because of my visual impairment, a sighted person has to get access to the project in order to help me with designing. That’s why I don’t develop locally, but on a live-server instead. Now, how can I make the project invisible from within the panel? Base of my page is the zero-one-theme. When I access mydomain.de the page is visible. But of course I would like to have it invisible, until it is ready, and only accessible from within the panel. When I change the status to unlisted, the page is still visible with the browser. What do I have to do to make it a draft?
Thanks and best.
Michael
I think a better solution here would be to use this plugin during develoment GitHub - AndreKelling/kirby-force-login: Force Login on Kirby CMS
It’s meant for use on staging sites, personally i use a subdomain like dev.yourdoman.com and block it from being indexed by search engines, but you could use that plugin on a live site.
What this plugin does is force any user who hits any page on the site to actually login before they are they are able to view any page on the website. Aslong as they have a panel account set up with Kirby they can login and then they will be able to view the site.
When you are done done developing, just disable / unistall the plugin, then eveyone will be able to see the site. This avoids juggling around with page statuses etc to hide things.
Using draft status for developent can be problamatic depending on what you have going on in the template. For example if you were building a a little side menu using $page→siblings() to display pages within the same section - if that page is a draft, siblings() will return the siblings of the page in the draft folder, rather then the siblings of the content folder that page would be in if it was published. I hope that makes sense.
On a side note, as a visually impaired person, how do you find working with Kirby? Im sure the Kirby team would love to hear any feed back you have that could improve the system in anyway in terms of accessability.
A method usually used for such cases is HTTP basic authentication: https://www.howtogeek.com/devops/how-to-setup-basic-http-authentication-on-apache/
Since you usually don’t have root access on shared hosting, you can create the password file locally and copy to the server. Then make the change in .htaccess.
Sites behind http basic auth are not indexed.
Thank you both of you for your suggestions. I think, I will create a subdomain and turn on debug-mode. But will definitely also have a look at the plugin. I would like to give feedback on Kirbys accessibility and suggest possible improvements. But for now, it’s to early, because I’m at the beginning of my development.