search

rockstor / rockstor-website

Main rockstor.com webpage. As a community endeavour we welcome contributions / corrections. Be sure to add your name to the AUTHORS file when submitting changes.
Other
2 stars 3 forks source link

Rename "Commercial Support" to "Paid Support" #80 #93

Closed phillxnet closed 6 months ago

phillxnet commented 6 months ago

Simplify/update wording regarding our planned relaunch of the 'Incident-based Support subscription'. Present as a "Support included" variant of our existing 'Stable Updates subscription' membership tier.

Incidental changes:

Fixes #80

phillxnet commented 6 months ago

Notes on proposed relaunch cost revision

The more current thoughts on this from me are that we incorporate a Stable Updates subscription within any support tier that we offer. This way we avoid the complexities, on our and other's sides, of having to subscribe to both a stable Updates subscription and an incident based support tier. Ergo we have say a €240 / year single instance support tier that includes a Stable Update subscription.

€24 - Stable Updates subscription membership €240 - Same as €24 option but with single instance support included.

So the equivalent of a €216 premium for single incident paid support. In the context that we are a non-business non-profit and small !!

This way Appman would treats each near identically. We may need an additional flag (order.field) to indicate if an incident has been used, and we show this element within Appman's Web-UI only if this is a support tier variant. Upon yearly renewal (New Transaction updating existing order) we ensure this order.field is re-set to what-ever number of support incidents the specific tier level represents.

Pricing is based on BareOS https://www.bareos.com/ from around 7 month ago.

https://www.bareos.com/pricing/

From the details we have: https://www.bareos.com/Bareos_Pricelist.pdf They also have a subscription as requirement - but we bundle this for the above reasons re Appman integration and user/back-end simplicity.

So our current equivalent of 48 hours response would be their €2600/10 = €260/incident Or their €1080/3 = €360/incident (but note this has no service level guarantee !!) So for business clients our €240 with best effort at 48 hour response, we should be within current context: reasonable. And this would be the recommended/suggested option for small-to-medium businesses. Expiration after 1 year if unused (within reason).

phillxnet commented 6 months ago

Caveat re Draft

When testing this PR, the intended page/menu changes look to be as intended. But we appear now to have a broken downloads page! I.e. no entries for each of the Downloads available - only the headers are now listed !!

~~@FroggyFlox or @Hooverdan96 any ideas on this. I've made no changes in related areas from what I can tell !! I'll update here if I track this one down.~~

Quick update - this no listed downloads (only OS headers) issue looks to be in current master also, so this may be down to a Hugo update/version issue or the like as our production website was build from master when last published.

[EDIT] see spin-off issue: "Hugo v0.123.0 breaks downloads page" #94

Building using last know working Hugo version of 0.122.0 and we again have a populated download page.

phillxnet commented 6 months ago

Moved status to 'ready for review' as our back-end has now received a work-around re our upstream Hugo update sensitivity detailed in the last comment.

Hooverdan96 commented 6 months ago

Two small comments on the page text ...

phillxnet commented 6 months ago

@Hooverdan96 Thanks for the suggestions. I'll take another pass and see what it looks like then.

phillxnet commented 6 months ago

I've done another pass and incorporated @Hooverdan96 suggestion, it does mean we now have a couple of rouge hard-coded email links (markdown), but it works from the user perspective and I've added an comment to note these in config.toml where all other emails references come from. That boostrap table addition is a tricky one via the shortcode.

I've also done some more simplification/reduction word-wise which I think helps.

If there are no more suggestions I'll merge and publish this on the 17th.

phillxnet commented 6 months ago

PR product PRODUCTION published