> I do have one question: is it true that a
> non-programmer (some one who is not willing to dig into the lines of codes)
> should not run a website using BoltWire?
I had an entire ensamble of amatuer theatre people use boltwire for
pretty much everything for an entire year. No one complained about
complexity or things being hard to understand / learn.
If you are going to be making unusual things you may encounter a point
when looking at the code would help, but it is probably easier for you
to ask the maillist to improve the documentation of the command/
function in question.
> A week ago I found this software by chance and decided to give it a try. In
> just about 5 minutes I got it up and running, including change of language.
> A big shock! I am sure there are people who can do the job in 5 seconds, but
> for a non-programmer and a beginner to this kind of software that was a
> record high. Before this one I tried the very popular WordPress, Moodle and
> Drupal, none of them gave me such a good experience in setting it up. For
> this all of you developers deserve a BIG APPLAUSE.
Agreed!
> I am not sure how to do so, I am just suggesting what to do in a
> non-programmer's point of view.
Huh. When I began using boltwire the markup was the only thing that
was easy to find in the documentation. The new documentation layout is
much better in almost every way.
isnt the docs.start page a decent hub for that kind of questions?
http://boltwire.com/index.php?p=docs.start
or is that not sufficient?
> The second frustration came from finding inside the box the new pages just
> created. It took me almost half an hour to find them listed in the
> non-system pages.
>I had to spend half an hour blind clicking to find the newly
> created pages.
I've often found it strange that there is a direct link to "plugins"
in the default actions bar, but not site.pages.
I assume this is what you mean, and it would certainly help.
> The next thing is the authorization system.
There are some good points here. Perhaps we should link some
authorisation explainations into the doc.start page? or at least to a
site administrator start page.
> And there is the file naming thing.
I don't agree with this part. I think it is possible that you do not
understand the file naming convention, and what it adds to boltwire. I
also do not understand how one is supposed to have a wiki without
organising the pages into groups, which is what the page-names does.
> Back to the documentation thing. A little suggestion to the use of terms in
> it.I know you are so familiar with the variables since you play with them
> everyday, but useres don't need to know the name of the variables. BOLTadmin
> and admin are simply not the same thing for non-experienced users. When I
> read "login as a BOLTadmin" I really got confused whether to type "admin" or
> "BOLTadmin" to login as an administrator. Of course it took me no time to
> figure out but I imagine there could be quite some people get stuck by such
> things.
These are good points, however, I can not find any page on
Boltwire.com that uses the phrase: "login as a BOLTadmin".
Do you mean the referens to the index.php file?
Could you link to some specific pages that caused this confusion?
Did someone fix this before I had time to read it?
> Again if you think a fool like me should not even bother to run a
> website,
Yeah, no. I strongly doubt that you are a fool, especially regarding
this very helpful email, but even fools should be able to set up a
Boltwire site with ease.
We shall work and make it so.
> B I think there are two main reasons, one of which being that there
> is no such confusion in their documentation. Even though reading your
> documentation was a joy for the fluently written English, terms like that
> alwasy got me stuck. My suggestion on this is to remove all the unnecessary
> BOLT- prefix in the documentation, to keep it easier to beginners.
I agree, although I still cannot find the BOLT-prefixes of which you
speak, except for the index.php file, and perhaps we should write that
to seperate or at least explain the php code better, but you seem to
be talking about more annoying things.
> I said two main reasons above but only mentioned one, what's the other? It
> is that I could change settings mostly with a GUI, no need to edit the
> files.
I mostly agree with you, and the backend could do with some more
visible gui interfaces for authorisations and group membership.
Does Drupal have as simple markup for form (gui) creation within its
pages as boltwire?
> Other minor things below:
>
> - I couldn't find an easy way to assign a member to a group (an action or
> button or something that requires just clicking/typing but no file
> editting).
action.join isnt linked to anywhere. This is a miss.
> - I couldn't logout by just one click.
this is true. we should at least put up a solutions page for it, it's
only a few lines on a code page.
> - Couldn't get to the page
> http://www.boltwire.com/index.php?p=resources.solutions.guito download
> the gui buttons for editor.
>
> Well, I'd better stop here or I won't have time to get my own work done.
> Thank you very much if you have come through all this. I'd like to mention
> again that I am not a programmer and a very beginner to this kind of
> software. Maybe some of my points are just too naive and wortheless, but I
> think that pretty much reflects a beginner's feelings.
I'm sure this will be very useful if we the community get on it. The
boltwire learning curve is pretty steep and easy and so beginer advice
is hard to come by.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
