Author: Nicholas

The Introductory site deal is for those who want to build a website that they can update themselves with as much work as can be achieved to implement the site design in a One Week Sprint.  That is Six Days of whatever effort you want to put in to learn how to use your new website and CMS.  Providing you interact with us on Slack this is what we achieve for the average user:

1. complete WordPress installation with 100% support for one week followed by Casual support for the rest of one year.
2. A potentially intense one-week online development interaction to shape your new site exactly how you want to see it.  You can schedule the days but depending upon availability, this may run for 5 contiguous days or, for example, two days, followed by a week’s gap, followed by 3 days in a row.  You may have to book the days you want on a first come-first served basis.
3. After five days of development we spend one day tidying up code, documentating, and sprint planning the next stage of your overall plan.  We then propose the sprint plan as a development project which is already hosted.  If the new Client wants to add more features to their CMS they can,  if they want to integrate a Development Project then Development Hosting is required.  This may involve moving the CMS site to a Cloud host which is a part of the delivery unless a separate Development Hosting is purchased.  The only thing that is “paid up” in a Intro site is the intro site itself which is generally hosted on cloudhosting.co.uk which is the Answerable DNS for all assets including cloud hosted subdomains.
4. We are unlike others: we create a service delivery and ensure that you can use it on whatever hosting you need.  If your service delivery needs more than one host, we simply add the name and sprint plan with you any work to create a new function.  We charge extra for bandwidth when you get very successful, we charge for each domain name, but you only pay for hosting once per annum.  Your overall hosting strategy may mean that basic hosting is no longer suitable for you, but will probably suffice while we configure for your expansion.  Expansions to hosting need not be extravagant but bandwidth costs must always be covered. You may however need both CMS and Cloud hosting accounts to support a Development Project with staging and a CMS which is never staged.
5. as well as subdomains, we can use meaningful domain name suffixes to point at related sites.  Additional domains can be added for the cost of renewing them, we do not charge for the number of domains but it may use up more of the development time you have to make a structure any more complex than it absolutely has to.  It is usually best to have ONE domain name.
6. It is vital to get used to creating content.  Write. Publish.  Revise. Rewrite.  Republish.  Start again.  Be fluid about content.  Link all your posts to social media so people can link to them and publish articles that people will read under menu listed categories that your audience need.  You can make it members only (they have to join/subscribe to see it) or public.
7. The important thing is to write like a river – you are guiding a “user journey” – basically you want them to do one thing – the next thing they need to do – offer too many or a not compelling choice and that is the attention span filter at work.
8. Every page is best done with an image, a story start point (the image) and end point (link to the shop page or a forum, for example).
9. When a new content creator is to be added to the site, they are going to have to create content as Contributors until they get the idea and then Authors until they really get it.
10. Editor status granted to one user at a time.  They take responsibility for all content.
11. A user who wants Admin rights basically takes over the reigns completely and only seeks support from RD.  Out of scope of the Intro package.
12. Intro package could have add-on services like Remote Backup that may be chargeable, as they can be done by the Admin using Export.
13. Supported Admin for small sites can be included, but once we start adding a structure of users, they are not small sites.  So we need a break point of where intro sites have one Editor user needing to be upgraded to CMS sites to establish the Admin Role, perhaps.
14. The Admin sets the roles for all other users.