Choosing Your Domain Name

Establishing your domain name is the first step in getting started with staking your claim on the web. Your domain name is a unique Web address that can be used to build out your own digital presence. To create your domain, enter your Colgate username (typically first letter of first name, followed by last name).

Signing Up

Review the Guidelines for Use

Before you get started, we recommend that you review the Usage Guidelines for Domains at Colgate.

The Sign-Up Process

Once you’ve reviewed the guidelines, you can proceed to the sign-up page.

  1. Click the “Get Started” Button
  2. You will be redirected to login for verification. You will use your Colgate username and password to log in.

Colgate Login Enter your Username and Password

Create Your Domain

  1. Enter your Colgate username. Click the button labeled Continue.
    Continue button
  2. Review your Domain name and contact information. It should be your first name, last name, and Colgate email. Click Sign Up.
    Sign Up button

After you click Sign Up, you will see a page letting you know that your domain is ready. You will then be redirected to the cPanel where you are on your way to creating your own Colgate Domains space.

Understanding Accounts & Passwords

One aspect of colgate.domains that users may find a bit complicated at first is understanding the different accounts (and associated passwords) that you can manage as part of your participation in the project. This article outlines the types of accounts that you are likely to have, what they are for, and how you go about resetting passwords on each of them.

Your cPanel Account

When you first sign-up for your domain and hosting, a cPanel account will be generated that provides you with access to your slice of the colgate.domains Web server. Your cPanel account is automatically associated with your Colgate username. Therefore, your Colgate user name will grant you access to your cPanel account.

Your Application Administrator Accounts

Every time you install a new application in cPanel, an Administrator Account for that application will be created. You will likely use these accounts very often – every time you need to login to your application to manage the associated Web site, you will use this account.

For example, if you install WordPress to manage your Web site, every time you need to add content to WordPress, change your theme, approve comments, etc. you will use this account to login.

Usually, you will be given the opportunity to choose the username and password for that account. We recommend choosing something that you are likely to remember but that is strong and secure.

Upon installation, you will likely receive an email confirming the user-id/password combination you chose. It will also have information about how to access the login page for that application. You may wish to make sure you don’t delete this message.

Depending on the application you’re working with, managing and resetting the password for this account will vary. If you’ve used Installatron (in cPanel) to install the application, however, you can always review the account credentials:

  • Login to cPanel through https://colgate.domains/dashboard/
  • Click the Installatron icon in the Software/Services section.
  • Find the application you installed under My Applications.
  • Click the Edit button (this looks like a blue wrench).
  • Scroll down to find the Administrator Username and Password.

In addition, most applications should have some kind of password reset link on the login page.

Other Types of Accounts

In addition to the three account types outlined above, there are a few other kinds of accounts you may have as part of colgate.domains:

  • FTP: If you set up FTP on your account, you will need to set up an account.
  • Application User Accounts: In addition to the Administrator Account that you set up when installing an application, most applications will also let you set up user accounts.

Privacy

What you put up in your plymouthcreate.net space rests entirely with you. You can choose not to pick a domain that reveals your name. You can use a pseudonym on your actual site. However, when you sign up through the default process, your name does get published as part of the public record about your domain name. Anyone can find it by looking up details about the ownership of that domain name through a public “Whois” request.

This is NOT an issue if you’re already planning on using your name openly on your site (in your domain name or elsewhere). This option is aimed, specifically, at those who, for whatever reason, feel they want to take every precaution to hide their identity on their site.

What Can You Do with Your Account?

Your ability to do things on Colgate Domains is dictated to a large degree by the limits of your imagination. That said, there are some technical requirements and limitations that you should be aware of and might want to review.

To spark your imagination, here are some ideas that might help you get started:

Install a Web Application in Your Space

Colgate Domains makes it very simple to install certain Web applications in your Web space. Web applications are just special software that run on a Web server. Usually they allow you to build and manage a Web site. The kind of site you can build depends on the type of application you install. Here are some examples of applications that you can easily install within the colgate.domains Web hosting interface:

WordPress LogoWordPress: WordPress is a blogging application. While it allows you to quickly and easily set up a blog, it also comes with a set of features that really make it possible to set up any kind of basic Web site without much difficulty. We have resources available that are focused on installing and using WordPress.

Mediawiki LogoMediawiki: If you’ve ever browsed or edited Wikipedia, you’ve already used Mediawiki. It is the open-source wiki software that runs the online encyclopedia, and you can install it on your Web space. It’s a good choice if you’re interested in publishing documents and then collaborating with others on them. We have instructions for installing Mediawiki.

ZenPhoto iconZenPhoto: This application is a good choice if you’re looking for a way to share images in your Web space. It’s also a quick install through Installatron in cPanel onto your Plymouth Create Web space.

 

These are just a FEW of the open-source applications that are available to you in your Colgate Domains Web space.  We encourage you to read more about what Web applications are and which ones are available to you through this project.

Organize Your Site with Folders

Through this project, you’ve received a domain name that you can actually subdivide and organize anyway you like. One easy way to organize your domain is to create subfolders for your site (which can also have their own applications installed in them). Here’s an example of how you might organize your site (using the subdomain vs. the subfolder approach)

Subdomain Approach Subfolder Approach
yourdomain.com (“root”) Install WordPress as your “main site” yourdomain.com (“root”)
course1.yourdomain.com Install a second WordPress instance for a course you’re taking yourdomain.com/course1
photos.yourdomain.com Install ZenPhoto for a public photo gallery of your photos yourdomain.com/photos
docs.yourdomain.com Install MediaWiki for a club you belong to that wants to collaboratively edit its bylaws yourdomain.com/docs
files.yourdomain.com Install OwnCloud so you can access your files on your laptop and at work yourdomain.com/files

This is just an EXAMPLE of a way to organize your site and then use different sections to do different things. There is no one solution to this challenge, and what you do should be driven by what makes sense to you. To start, you may just want to install one thing at the “root” of your domain, and then let the rest evolve as you get to know more about what’s possible.

Map Your Domain (or a Subdomain)

If you already have a digital presence that you’d like to pull into your Colgate Domains space, domain mapping is an option you may wish to explore. This allows you to assign your domain (or a subdomain) to another service. Some services that work with domain mapping are:

When you map a domain, users who visit your URL will automatically see your space on one of these services. It’s a great way to incorporate your activity elsewhere into your domain, and it might be a good first-step if you’ve already established a presence somewhere else and just want to point your new domain to that space.

What Exactly is a Web Application?

In the most general terms, a Web application is a piece of software that runs on a Web server. A Web server is a just a specialized computer designed to host Web pages.

Most Web applications are comprised of two components: files and a database. When you install a Web application, you will need to make sure all of the files are copied over into the appropriate location AND that a database (and database user) has been set up to connect to those files. Often, you will have to do some configuration to make sure the application knows how to access the database.

The system we use for Colgate Domains uses a special script installer called Installatron (in cPanel) that allows you to automatically install dozens of open source applications. When you use Installatron, you don’t need to worry about moving files, creating databases, or doing the initial configuration. It’s all taken care of for you. You can find out more about Installatron here.

In order to run on the Colgate Domains server, Web applications must be able to run on a LAMP server, which is the particular kind of Web server that we use. Occasionally, a Web application may require additional components or modules that need to be installed on the server.

Static and Dynamic Websites

Static Websites

In the early days of the Web, almost all Web sites were what is known as 'static sites.' Content (text, images, video, audio, etc), was placed or embedded in a file in which HTML tags were used to format it. If you looked at the actual contents of the file, you might see something like this:

example of static HTML code

The content and the tags lived side-by-side. To edit the page, you’d open up the file (on your own computer) in a program capable of editing HTML files and make changes to either the content or the presentation. Every page had to be edited individually, even if the edits you were making were for common elements that appeared on many pages (like menu bars).

From a technical perspective, accessing a static Web site is fairly straightforward. When your computer is connected to the Internet, you can use a Web browser to access files on a Web server (as long as you know the address). The Web server delivers the contents of those files to your browser, and your browser displays them.

Dynamic Websites

Over time, as the Web became more sophisticated, new systems emerged for creating and managing Web sites. These moved beyond the model of having content and HTML tags live in a simple HTML page which your browser accessed and displayed. Instead, these systems were Web applications – software that literally runs on the Web server and makes it possible to manage a Web site, often with very sophisticated features. One feature of these applications is that they separate content and presentation by storing most content (your text, images, etc) and data about the site (the title, options, etc). in a database.

On the Web server, the Web application installs files that are written in some kind of programming language. The server reads this code and obeys any requests in it to access data in the database (which lives on a separate server) and displays it according to the instructions in the code.

example of dynamic HTML code

Essentially, the data for the site (living in a series of tables in a database on the database server) is entirely separate from the actual presentation of the site (living in the code of the programmed files on the Web server). Special software on both the Web server and the Database server enable the two to speak to each other and work together.

One of the benefits of using a Web application is that you usually don’t need to touch (or even look at!) the code in order to make changes to your content. In addition, editing the site usually involves accessing some kind of control panel through your Web browser and filling out a form, instead of having to download and access files in software on your own computer.

Dynamic vs Static Content

Sometimes when we talk about the difference between dynamic and static content we get bogged down in the idea of whether or not the content is “fresh” (dynamic, regularly updated) or “old” (static, never updated). How frequently you update your content has nothing to do with what kind of system you are using to manage your site. You can manage a static Web site (as described above) and update the content every day. You can also have a dynamic Web site (running something like WordPress) and never change the content after you create it.

Generally speaking, it IS easier to regularly update content on a dynamic Web site because the Web application just makes it easier. Sometimes, even when you just want a very basic page or placeholder, it’s easier to install a Web application (and only put up a single page) then to manually create an HTML page and upload it.

A Side Note about Separating Content from Presentation: Style Sheets

Another aspect of separating content from presentation involves the use of 'Cascading Style Sheets' (CSS). These are special files that live on your Web server and are linked to your Web pages. They contain information (written in a special markup language) about how to make elements on your site look. They allow you, for example, to define in a single location what all Level 1 Headings look like on your site. They are an important aspect of understanding how to separate content from presentation, but they’re not really an aspect of the difference between static and dynamic sites. Both static and dynamic sites can use style sheets.

LAMP Environments

When you sign up for colgate.domains, you get space on a Web host that is associated with the project. There are a few things you need to know about the Web host that will make it easier to understand what you can do with your new space.

The Web Server

The Web server is the main computer that is associated with the colgate.domains hosting account. It is literally a computer – a computer that has special software on it that allows it to be accessible via the Web. The files that run your applications, images or video you upload, or any other files you upload into your Web space are stored on this server.

(For comparison’s sake, your desktop or laptop computer, by default, doesn’t allow this; I can’t access files on your computer through a Web browser by default. You CAN actually install Web server software on your own computer, essentially making your files accessible over the Web.)

In order to run, a Web server has an operating system installed and some kind of Web server software. The colgate.domains server runs the 'LINUX' operating system and an 'APACHE' Web server.

The Database Server

In addition to the Web server, there is also an associated database server. This is another computer, but it is configured with software that allows it to host databases. It is also connected to your Web server so that your applications (hosted on the Web server) can retrieve data (from databases hosted on the database server).

Databases come in LOTS of varieties. The kind of database you can use for a Web application depends on the kind of software that’s installed on the database server. The colgate.domains server can run 'MYSQL' databases.

The Programming Language

When you install open-source software on your Web account, it’s going to be written in some programming language. Your Web server has software installed on it that allows it to understand different languages. If you install software that’s written in a language that your Web server doesn’t read, it won’t work.

The colgate.domains server has software installed on it that allows it to understand 'PHP''PERL', and 'PYTHON'.

Add it Together: LAMP

If you take a look at all the descriptions above, you can determine that we are running what is known as a LAMP server for colgate.domains:

  • Linux (operating system)
  • Apache (Web server)
  • MySQL (database server)
  • PHP/PERL/PYTHON (programming language)

Applications that are written for LAMP environments will, presumably, run on the server. HOWEVER, some applications do require additional extensions or libraries that aren’t included, by default, in a LAMP environment. The applications you can install via Installatron (in cPanel) should work just fine.

What makes LAMP environments special is that all of the component parts are open-source. Linux, Apache, MySQL, PHP, PERL, and PYTHON are all open-source programs or systems. Anyone can download them (for free) and install them. Anyone can also modify them and redistribute them. As a result, there are lots of online resources for using these systems that have been built by their communities of users. But, also as a result, since you’re not paying for these systems, you can’t just call up a company and ask them to fix a problem.

What are the technical requirements and limitations of Colgate Domains?

Colgate Domains uses a Web server known as a LAMP server. “LAMP” is an acronym for the technology stack that is installed on the server:

  • Linux: This is the open-source operating system that is used on the server.
  • Apache: This is the Web server software that the server uses.
  • MySQL: This is the database software that the server uses.
  • Php/Perl/Python: These are the three programming languages that the server can interpret.

Generally, if you are using applications available to install by default through the colgate.domains, you shouldn’t need to worry about these technical details. All of the software that is available for installation (in cPanel) meets the technical requirements.

If you’re interested in finding/installing another application (that isn’t available through our automatic installer tool), then you’ll have to be sure that the server can support it. To start with, you’ll want to be sure that the Web application can run on a LAMP server. Check the technical requirements for the application to determine this. You’ll also need to do some research about whether there are any additional services or modules required on the server. Some software may require components that aren’t included in the default installation of the LAMP stack. In that case, contact us with details about what you need, and we’ll see what we can do.

Social Media

As you begin to build out your digital presence you’ll probably start to think about social media in some form. In fact it’s likely that you already have at least one, if not more, social media accounts (Facebook being the most popular to date). Everyone uses social media in different ways, and although it’s often interesting to see people break the boundaries of the “social norms” of a specific online community, this article will focus more on the accepted use cases for specific social networks and how they can help you build your digital presence. This is by no means a comprehensive “How To” of Twitter or Facebook, but a good starting guide to think about where you best fit in to these online communities.

Facebook

The majority of folks that will read this likely have a Facebook account. With over 1 billion active users it’s by far one of the more popular social networks. Many treat Facebook as a semi-personal space, one reserved for family and friends to share photos and highlights of what’s happening in their lives. Facebook also supports “Groups” for sharing amongst a smaller set of individuals regularly, and “Pages” which are less personal and more public-facing profiles meant for organizations and businesses. There are plenty of applications that make it easy to publish a link to the work you do on your blog and your participation in other networks back into your Facebook profile. In genera, it’s a good practice and can often lead to interesting conversations with different groups of folks. This practice of publishing elsewhere and then feeding into Facebook is desired over the alternative, using Facebook for all content and then pushing it out to other communities. The main reason for this is that privacy concerns over how different people can view content on Facebook have changed often enough to leave users concerned. There’s also never any certainty of sustainability with any of these social networks (remember MySpace or Friendster?) no matter how popular, so publishing in your own space and then pushing out to others makes a lot of sense. The key takeaway is that Facebook is a great personal network and can also be the starting point for some of these larger professional discussions should you decide to use it that way.

Twitter

While no longer the new kid on the block, Twitter has only relatively recently started to gain momentum. It doesn’t have nearly the same user base as Facebook (though there are about 500 million accounts to date) and the way people use it is very different. Twitter has focused on the short status message from the start, before Facebook even integrated the idea into their platform. Users are limited to 140 characters. It’s a conversational platform for interacting with people. It’s used heavily at conferences and many choose this as a social network for really networking with peers and others in their community as well as people they might not ever meet in real life. You can follow as many people as you want and it’s a great way of having a stream of information about “what’s happening” with people and groups you’re interested in. One powerful development of Twitter is that celebrities have begun to embrace it as a way to speak directly to their fans without having the message interpreted through other media and journalism with a slant. The ability to search various topics or hashtags (keywords) and see a running stream of what people are saying about that topic is also a very powerful way of gauging reaction to ideas and events. It’s a great idea to experiment with a Twitter account by signing up, adding a profile picture and information about yourself, following a group of people, and interacting with it daily. While the gratification may not be immediate, it’s one of those social networks where the more you put into it the more you will get out of it.

LinkedIn

LinkedIn is the professional resumé of social networks. It mixes the ability to keep an updated resume of where you work and what your accomplishments are with a social aspect of having people recommend you and comment on your work. Most users find LinkedIn helpful not as a day-to-day network they use, but rather when they’re searching for a new job and want to find people they know that might have connections. The old saying “It’s who you know” when finding a job or making a connection is particularly relevant here where those connections can be exposed to you (You know this person who works for the company of one of Bill Gate’s sons, and the VP went to high school with you).

Summary

As mentioned in the opening paragraph, talking about social media is an ever-changing and moving target and this article can never be truly comprehensive. The goal of Colgate Domains is to have you thinking more critically about where you put your content, not that you don’t participate in these networks which still have a lot of value, but rather that you own the work you create. Facebook, Twitter, LinkedIn, and others all have different audiences and the more places you push your content to, the more opportunities for discussion and feedback you’ll receive. The ability to network with an increased amount of people that isn’t reliant on face-to-face meetings is a powerful change in how we interact on the web and the value of it. As you begin to explore social media the best recommendation would be to choose a space you want to explore and really dive in. Follow as many people as possible, talk to them, respond to their work, and you’re more likely to get responses in return that start to build that sense of community for you.