Harvey... You're nervous about NAML... LOL

[mywaytoo]

Harvey... believe me, YOU have nothing to be nervous about... LMAO  

[Harvey]

mywaytoo wrote

Harvey... believe me, YOU have nothing to be nervous about... LMAO

It's true.  I've worked hard to build the forum in 15 months from 0 to 193 members.  Content, CSS, Link building, on-page SEO.  I've worked out deals for "ski-reporters" to get free lift tickets, and other insane things to build our content and community strength.  

 With a ski blog, winter is everything.  We could go to 400 members by mid-winter if all goes well. One thing that is crucial is that  the forum stays reliable and fast. There are ten other forums out there that people can join if my site is down.  I NEED reliability.  I want NAML up now so  we can get the bugs worked out before the snow flies here in the northeastern US.

I think by putting YOU in bold you are indicating that I shouldn't be nervous because I've paid for premium support. But app reliability isn't a premium support thing. Hugo and team Nabble want reliability for all users most of all. They work tirelessly to provide it.  And the respond to calls for help of "forum down" issues as fast for me now as they did when I was in free support.

Premium support is more about Customization.   Every community has different needs. My community just could not grasp the idea that responding to notification emails was the same as posting. A few times embarrassing personal stuff was posted publicly, so I asked Hugo to disable the feature for me.  As much as it KILLED him to reduce features he did it and my life is was easier because of it.

I don't know how much you guys put into your forums and websites, but when you put in the kind of effort I do - PREMIUM support is a no brainer.  I highly recommend it.  It's also fun to see features you've asked for go Nabble wide.

[Peter <Nabble>]

Harvey, I strongly suggest you and all other Nabble users to have test applications where you can test your NAML modifications before they go to your real applications. Not that NAML is hard. It is not. But you don't change HTML without first taking a look if you got what you desire, do you? Do you do it with CSS? I suppose not. So don't do it with NAML. Try it in your test applications and then apply it in your real applications. ;-)

Just don't forget to keep them synchronized. I mean, if you already have changes on your real apps (like when you are a premium user and requested for modifications) don't forget to apply them to your test forums so you know exactly what will happen and how they may interact with each other.

Another hint I can give you is to do one small modification at a time and give it some time between modifications so your users can get used to it and you are sure that no undesirable effect have happened. If you make 3 modifications and notice something wrong, you won't know which one (of the 3) to blame.

If you do it this way it is very unlikely that you will break something.

So, as you see, there is a way to play it safe and it is not hard to follow it.

[Harvey]

I have a test application. It has no modifications.

How would I transfer the all of my current modifications over to it?

Also what I was referring to above was not down time create by modifications, but down time like we had two weekends ago. When NAML is fully running, I'm going to give you the short list of modifications I need (all have already been posted in support -  mostly the title tags stuff) and then I'm not touching a THING until the ski season is over.  I need reliability more than tweeks Nov-May.

[Peter <Nabble>]

You will be able to apply NAML modifications to your other forums once NAML is released.