Difference between revisions of "Services"

From Organic Design wiki
m (Intranet & LAN)
m (See also)
 
(25 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Organic Design offers a range of services around setting up wikis for your organisation and helping you use and develop the wiki for document management, collaboration and organisation. This includes the initial set-up of your wiki, administration, development and training as required. Our focus is the adaptation of the software to support additional organisational requirements such as website content management, procedures documentation and record administration. In doing so, we aim to integrate a range of functions into a unified system that can be used to organise projects and businesses in a collaborative way.
+
== Free services we use ==
== Wiki ==
+
*[http://Github.com Github] ''- software repository hosting for open source projects''
We can set up and configure a hosted wiki to your requirements. This will allow you to take advantage of all the features of the software that powers Wikipedia, so you can create an internal or public knowledge base around topics of importance to your organisation.
+
*[https://blogtrottr.com/subscriptions/ Blogtrottr] ''- subscribe to RSS or Atom feeds to have them sent to an email address''
;Further details:
+
*[https://letsencrypt.org/ LetsEncrypt] ''- free SSL certs, see also [[SSL]] which has our configuration details''
*[[Wiki Packages]]
+
*[https://onename.io OneName] ''- decentralised identity using the Namecoin network''
=== Wiki skins for website ===
+
*[https://keybase.io Keybase] ''- decentralised secure identity and encryption/decryption/signing service''
Our wiki skinning service allows you to specify what you want your wiki to look like - you can specify any "normal website" design. Then you can continue to manage your documents using the familiar wiki interface and specify which ones are to be displayed on the public website part. Just like we do on Organic Design.
+
*[[Prezi]] ''- make cool presentations online''
=== Wiki organisation ===
 
We have developed a technology to add a number of functions to MediaWiki, which allow the mass creation and organisation of records. These could be web enquiry forms, contact management, task tracking, invoicing or a range of other records as required by your organisation. All with the ability to track changes, discuss individual pages and mix casual notes with structured data.
 
=== Wiki development ===
 
A lot of organisations need further functions in addition to our standard wiki packages, that's where our experienced developers come in. They can help you determine what is needed and develop custom extensions. Our lead developer is one of the official developers of the MediaWiki software.
 
  
== Support ==
+
== Free online tools we use ==
Getting a wiki set up and hosted is a start, but many organisations require some support with staff training, in establishing best practices to make the most of the wiki or to find out how this technology can support their existing business practices and integrate with existing systems.
+
*[http://validator.w3.org/ W3C Validator]
=== Content Management ===
+
*[https://www.ssllabs.com/ssltest SSL test]
We have consultants familiar with the challenges of keeping large wiki sites organised and well-structured. This includes monitoring the developing content of client wikis and making adjustments and corrections in accord with established wiki best practices (often based on Wikipedia best practices, adjusted to your requirements).
+
*[http://www.loadinfo.net/ Loader Generator]
This can also involve the development of custom training sessions, content templates and navigation structures based on a familiarity with how your organisation uses the wiki.
+
*[http://jsfiddle.net jsFiddle]
=== Training ===
+
*[http://www.redirect-checker.org/ Redirect checker]
We've defined a [[MediaWiki Workshop]]... this is usually done onsite, but has also been used successfully using IRC or Skype.
+
*[http://tools.wikimedia.de/~dapete/ImageMapEdit/ImageMapEdit.html?en ImageMap Editor]
=== Consultancy ===
+
*[http://dnsstuff.com DNS Stuff]
 +
*[http://www.isup.me isup.me]
 +
*[http://www.w3schools.com/browsers/browsers_stats.asp Browser Stats]
 +
*[https://siteexplorer.search.yahoo.com/search?p=http%3A%2F%2Fwww.organicdesign.co.nz&bwm=i&bwmf=s&bwmo=d&fr=yfp-t-501&fr2=seo-rd-se Who links to us?]
 +
*[http://www.colorschemer.com/online.html ColorSchemer]
 +
*[http://www.webpagetest.org/ webpagetest.org]
 +
*[http://samy.pl/evercookie/ EverCookie]
 +
*[http://www.google.com/webmasters/tools/richsnippets RichSnippet Tester]
 +
*[http://repogen.simplylinux.ch/ Ubuntu sources generator]
 +
*[http://vixy.net/ Vixy video converter]
 +
*[http://browsershots.org BrowserShots.org] ''- check what you site looks like in other browsers''
 +
*[http://netrenderer.com/ NetRenderer] ''- alternative to browsershots.org''
 +
*[http://web-sniffer.net/ View HTTP Headers]
  
== Server Installation & Administration ==
+
== Paid services we use ==
Although our primary focus at Organic Design is wiki organisation, we need to have a solid set of procedures and practices in place for setting up and maintaining servers to run the wikis on. Over the years we've developed and refined our server administration to the point where we can quickly and reliably install a complete wiki farm from the ground up based on the Debian Linux operating system. Our server installation procedures allow for rapid deployment of servers which can include the following functionality:
+
*[http://twilio.com Twilio] ''- virtual phone numbers for sending/receiving voice and SMS to and from your server''
*MediaWiki farm
+
*[http://codero.com Codero] ''- our favourite dedicated server provider''
*Other PHP5-based web applications
+
*[http://linode.com Linode] ''- our favourite cloud server provider''
*Email server with IMAP folders, spam filtering and web-mail access
+
*[http://namecheap.com Namecheap] ''- our favourite domain name supplier (they accept [[bitcoin]] too, and their dedicated server prices look good, but haven't tried them out yet)''
*IRC server for hosting your organisations own private and/or public chat channels
+
*[http://www.webdrive.co.nz WebDrive] ''- our domain name host for NZ domains''
*Distributed backup
+
*[http://bitnz.com BitNZ] ''- our favourite NZ bitcoin exchange''
*Robot framework for notification of various events and information over IRC, email and into the wiki's recent changes
+
*[https://www.bitcointoyou.com/ Bitcoin2You] ''- our favourite Brazilian bitcoin exchange''
 +
*[http://paguecombitcoin.com/ PagueComBitcoin] ''- pay Brazilian "Boleto" invoices or topup cell phone with bitcoin''
  
== Intranet & LAN ==
+
== On demand products ==
These days many organisations are using wikis internally on their intranets for internal document management and collaboration on projects and work. The procedures we've established for setting up and maintaining external web-servers form a good basis for intranet servers too, but come with some additional requirements, especially when the organisation has servers both internally and externally.
+
On demand products are becoming very popular nowadays especially due to all the new 3D-printing hardware that's available now.
  
=== Network server ===
+
=== Printing On Demand ===
In addition to the procedure used to install and maintain a normal web-server as described in the previous section, a LAN-based server often requires some of the following additional aspects:
+
*[[W:Espresso Book Machine]] ''- print books on demand - general concept''
*Local email server for internal mail, connecting to external server where necessary
+
*[http://www.lightningsource.com Lightning Source]
*Local IRC server connecting to external IRC server when available
+
**[http://www.lightningsource.com/links.aspx#AuthorServicesLinks List of on-demand printing businesses]
*Network file server
+
*[http://www.ondemandbooks.com/home.htm On Demand Books (ODB)]
 +
*[http://www.lulu.com/ Lulu]
  
=== Workstations ===
+
=== Production On Demand (POD) ===
For organisations that wish to run Linux on their worksations, we have developed a package and procedures similar to those we use to install servers except that our workstations run on Ubuntu Linux instead of Debian Linux. Our workstation package allows us to quickly set up many workstations with a set of applications and configuration we've developed and refined over the years for our own workstations. The installation of workstations can be done either using a standard Ubuntu with an Internet connection, or by booting our LiveCD.
+
*[http://www.zazzle.com Zazzle] ''- on-demand printing of merchandise''
 +
*[http://www.cafepress.com/ CafePress] ''- on-demand printed merchandise and CD/DVD's''
 +
*[http://finerworks.com/pricing.asp finerworks.com] and [http://www.canvasondemand.com/canvas-sizes.asp CanvasOnDemand] ''- printing/framing/mounting photos on canvas''
 +
*[http://www.3dprinterworld.com/article/metal-printing-for-consumer-s1-from-aurora-labs Affordable 3D metal printing available]
  
=== Software migration ===
+
=== On Demand in Software Architecture ===
 +
This concept of production on demand also plays an important role in software architecture and programming environments. Complex applications like office suites and content management systems can have huge arrays of diverse components and modules. Applying the on-demand paradigm in this context simply means to only load those components into memory when their first required.
  
== Why use Organic Design Services? ==
+
This issue is closely related to the programming environment as well, for example the so-called "stateless" paradigm which is the client-server/request-response system used on the web is not a very on-demand environment. This is because every request has to run its own instance of the server application. Although shared-object architectures can help with this, it would be supported from the ground up in a peer-to-peer architecture.
=== Cost effective ===
+
 
We base all our services on free, open source software developed by a worldwide community of experts. This means you only pay for customisation and support of proven and reliable software. We do not charge license fees for software, or ongoing per-user fees for software. Generally there is a setup cost and an hourly rate charged for development and support. That's it!
+
== See also ==
=== Remain independent ===
+
*[[Hosting]]
We will make sure you always have a choice regarding how your organisation uses software to get work done. This means our work complies with standards and we will always make procedures available for you if you wish to administrate the software yourself. Further, our agreements do not include minimum terms or any other kind of lock-in to try and "encourage" our clients to stay. Instead, we focus on delivering quality services and maintaining good communications with our clients.
+
*[[Libre software]]
=== Simplicity and integration ===
+
*[[Open Source#Open Source hardware|Open Source hardware]]
We have years of experience in integrating a range of IT systems using wiki organisation. In doing so, we strive to simplify and cut through the clutter, making the system robust and easy to use. When developing something like a procedure, we aim to make it as complex as necessary, while keeping it as simple as possible. This is in alignment with the "wiki philosophy", which despite a somewhat simple and casual approach has resulted in the creation of one of the most popular, sizeable and relevant websites on the internet - Wikipedia. We embody that philosophy in everything we do.
+
*[http://fiverr.com/ Fiver.com] ''- cheap online services of all kinds''
=== Join the Web 2.0 revolution ===
 
Everyone is talking about the collaborative Internet, "Web 2.0" and many organisations sense great opportunity in creating a collaborative culture. Yet this can remain an elusive and subtle goal to achieve. We have used the Web 2.0 tools to create a collaborative organisation ourselves and can assist organisations in the use of these tools to do the same. This is far more than just getting the tools for collaboration in place, it also includes the supporting processes and organisational culture, things we have been developing for years.
 
[[Category:Organic Design]]
 

Latest revision as of 21:51, 20 November 2019

Free services we use

  • Github - software repository hosting for open source projects
  • Blogtrottr - subscribe to RSS or Atom feeds to have them sent to an email address
  • LetsEncrypt - free SSL certs, see also SSL which has our configuration details
  • OneName - decentralised identity using the Namecoin network
  • Keybase - decentralised secure identity and encryption/decryption/signing service
  • Prezi - make cool presentations online

Free online tools we use

  • Twilio - virtual phone numbers for sending/receiving voice and SMS to and from your server
  • Codero - our favourite dedicated server provider
  • Linode - our favourite cloud server provider
  • Namecheap - our favourite domain name supplier (they accept bitcoin too, and their dedicated server prices look good, but haven't tried them out yet)
  • WebDrive - our domain name host for NZ domains
  • BitNZ - our favourite NZ bitcoin exchange
  • Bitcoin2You - our favourite Brazilian bitcoin exchange
  • PagueComBitcoin - pay Brazilian "Boleto" invoices or topup cell phone with bitcoin

On demand products

On demand products are becoming very popular nowadays especially due to all the new 3D-printing hardware that's available now.

Printing On Demand

Production On Demand (POD)

On Demand in Software Architecture

This concept of production on demand also plays an important role in software architecture and programming environments. Complex applications like office suites and content management systems can have huge arrays of diverse components and modules. Applying the on-demand paradigm in this context simply means to only load those components into memory when their first required.

This issue is closely related to the programming environment as well, for example the so-called "stateless" paradigm which is the client-server/request-response system used on the web is not a very on-demand environment. This is because every request has to run its own instance of the server application. Although shared-object architectures can help with this, it would be supported from the ground up in a peer-to-peer architecture.

See also