Loading...
 
Features / Usability

Features / Usability


Re: Re: HomePage configuration

posts: 4656 Japan

>Thank you for responding.

No problem. smile

> >... I would use a "Tiki" file for the homepages, that is, either create a
> wiki page to be your home page ...

>I'm sorry, but I'm having trouble understanding this. I know I can create another page linked from the HomePage, e.g., PublicHomePage, but I'm not sure how to assign that new page to a specific URL that I can then reference as the public site.

In General Preferences (tiki-admin.php?page=general), you can select "Use URI as homepage" and then indicate the address of the file. This will be your site's homepage. Or you can select a Tiki section for the home page. I'm not sure what the default list is that shows up for this item. On my site I see Wiki, Articles and Custom Homepage listed along with a blog and an image gallery. Anyway, you could choose one of these types to be the home page, as well.

>I also understand that from the Admin->Wiki page, I can specify a different name for the HomePage, but I don't see how that solves my problem either.

Right, you need to go up a level, so to speak, to decide even whether or not you want a wiki page as your home page.

>If I create a new file in the tiki directory, I'm not sure what that file should be called, what contents are expected, and how I associate it with the tikiwiki HomePage.

Well, you'd designate it as your home page in Admin General Preferences as I described above. Now, this file could be anything, so the question is what you want to offer to your visitors. What Tiki content features do you want to use?

>None of the standard themes apply, so I will create my own.

I assume you are familiar with the suggested procedure for making a new Tiki theme; i.e., start with an existing theme and modify it. But if it's function that you want to control rather than appearance, I think you should look more at the configuration possibilities for various user groups rather than at themes, which are really more for determining page layout than site functionality.

>I didn't think I could use the same theme for the admin and public pages as there won't be a login option from the public pages.

The log-in box is just a module, and it can be configured so that Anonymous visitors don't see it. (Check the Modules menu item under Admin (Click me!). You could enable the log-in module for your Admin and other member groups but not for public viewers. Of course this could be problematic if you or another "admin" person comes to the site without a cookie set or session active; then you'd be anonymous as well and would see no login box. In this case you'll want to remember this address: tiki-login_scr.php. But is a log-in form on the public index page really objectionable?

> Without a login, you can act on user preferences and display different themes or pages, so I think they have to be distinct.

I'm not sure what you mean here.

>There is also interesting information of the admin pages that I wouldn't want on the public pages

Right, but this is in the realm of permissions, not themes. Have you looked at Tiki's permissions system to see how this works? See "Groups" in the Admin menu. Public visitors don't see Tiki admin pages, by default. And anything you add to the site can be made inaccessible to the public. Again, the permissions system is the key here; are you clear on how to use it?

-- Gary

posts: 4

I’m sorry … I think we’re going in a circle here, so I think it would help if I tell you that I’m creating a web site for a local Habitat for Humanity affiliate. They’re a small, understaffed office and the website will be used to push information out to the world, but not to interact with the world via the website. I think perhaps in time, when they have the resources and the comfort level, they may want to do more with their website, but now is not that time.

So I want a simple non-interactive web site, but it’ll have photo galleries of build sites, calendars for their build events, and a FAQ. There won’t be any distinctions at this time as to the kinds of possible viewers of this website, i.e., no groups should be needed.

>> Well, you'd designate it as your home page in Admin General Preferences as I
>> described above. Now, this file could be anything, so the question is what you
>> want to offer to your visitors. What Tiki content features do you want to use?

Good! … This is what I was initially trying to find out. In my first posting I described my mistaken attempt to use an URL vs. a URI in the Admin General Preferences. Now I know it has to be a URI and I was thinking of making the URI refer to a Wiki page that looked like my originally proposed index.html file. And there would be no login (see below), so I’m looking at different home pages for developers vs. users.

There are no special wiki features referenced in that home page. However, I would have buttons in the top bar that would lead to pages that use features such as a FAQ or photo gallery. The ))HowDidTheyDoIt(( pages show examples of similar menu buttons in the top bar.

Now … Does this mean I need a .php file (e.g. hfh-index.php) that does the tiki-setup and then does the relevant things found in tiki-index.php? If so, would I create a wiki page linked from the standard ))HomePage(( and then refer to that new wiki page in my hfh-index.php file?

And then I’m not sure how to handle the buttons in the top bar. If the buttons go to specific .php files, how can I refer to specific Wiki pages from the .php files? Is there a particular set of files that would show me how this is done?

>> I assume you are familiar with the suggested procedure for making a new Tiki theme;
>> i.e., start with an existing theme and modify it. But if it's function that you want to
>> control rather than

Yes. And it’ll be function and theme. I got a set of zipped theme files from mods.tikiwiki.org by contacting one of the submitters directly and I’ll take a look at that files as an example. BTW: all of the zip files for the themes appear to be corrupted and someone already noted it in a comment for one of the themes; that’s why I had to contact the person directly. I’m not sure just who to notify of the problem since all of them are bad.

I’ve also seen the documentation on themes and the ))HowDidTheyDoIt(( page, so all of that information should help me.

But again, I won’t be distinguishing the types of users; so all users will have the same functionality and will see the same theme.

>> But is a log-in form on the public index page really objectionable?

I think it would be visually distracting. Developers or maintainers would only use a login and they are not the key users of that site, so esthetically it seems wrong to include a login box. The affiliate office might have to deal with questions from people asking how they can obtain logins and that would be distraction for them.

One of the “best Tiki sites??? is a commercial site for a salon and that doesn’t have a login box, so there must be a way to handle this.

> Without a login, you can act on user preferences and display different themes or pages,
> so I think they have to be distinct.
>
>> I'm not sure what you mean here.

My apologies … I wanted to say you *cannot* act on user preferences if there is no way for a user to log in.

I hope this makes it clearer. Thank you for your patience!
Karri


Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting