WebAIPlanet

Essential list of resources for building your own website

If you choose WordPress or a self-hosted site, you usually need to prepare the program, domain name, hosting, theme, plugins, content material and online optimisation tools first. Newbies can follow a checklist to see what they need to prepare and then follow the route step by step to get started.
fig. beginning / Resources for building websites / Build Your Own Website Resources

snapshot

Self-built websites are for people who want to take control of their website for the long term

Self-built website is not “write your own code from scratch”, but to choose your own programme, domain name, hosting, theme and plug-ins, and be responsible for subsequent updates, backup, security and content maintenance. It is more suitable for projects that want to operate for a long time, do SEO, precipitate content and master the background data.

more suitable

  • Want to run a corporate website, blog or content site on a long-term basis
  • Want to own domain name, hosting, backend and data
  • Willingness to learn basic maintenance in exchange for higher autonomy
  • SEO, multi-language, form or mall functionality may be added at a later date.

Not necessarily suitable

  • Just want to get a simple showcase page online as soon as possible
  • No hosting, updates, backups, or security at all.
  • Requires complex approvals, permissions or business systems
  • No one on the team can maintain content and accounts for long periods of time

Procedure Selection

Choose the programme first, don't compare all the tools at the start

Most self-hosted sites can start with WordPress; Joomla, Drupal, and traditional CMS are better suited for projects with a specific content structure or maintenance experience.

Joomla

Veteran CMS

Full functionality, suitable for sites that have a certain technical base, require column management and strong content organisation.

Suitable for: projects with maintenance experience

Drupal

complex structure

It is more suitable for websites with complex content structure and high permission management requirements, but the threshold for getting started and maintenance is also higher.

Suitable for: medium to large content projects

Traditional CMS

stock scenario

Suitable for some of the traditional information station, column station or have maintenance team projects, new projects are generally not recommended to give priority to.

Suitable for: Traditional content management scenarios

List of resources

You need to prepare these resources to build your own website

The list only addresses “what to prepare” and “when to prepare”. More detailed tutorials, reviews and comparisons are available in the details portal or in the next level of articles.

proceedings
necessarily
Newbie priority WordPress, special structure then consider Joomla / Drupal
Make sure before you buy hosting
domain name
necessarily
Relevant branding, short and memorable, controlled renewal, easy to parse
Before building
Hosting / Server
necessarily
Stability, Speed, Backups, After Sales, Suitability for WordPress
pre-installer
Themes / Templates
suggestion
Page structure, responsiveness, loading speed, subsequent modifiability
After the programme is loaded
plug-in (software component)
on demand
SEO, forms, caching, security, backups, don't load too much at once!
When the base page is complete
Content material
necessarily
Company, Services, Products, Cases, Pictures, Contacts
hyperlinked page
SEO / Statistics
suggestion
Keywords, title description, sitemap, indexing and statistics
Before and after the launch
SSL / Backup / Security
necessarily
HTTPS, background protection, regular backups, updated policies
Pre-launch configuration

Resource details

Look only at the key points for each type of resource and move on to the tutorials in the next step

Here with the card directly show the role of each type of resources, the focus of the choice and the next step in the entrance, do not need to repeatedly expand and collapse. When you really want to operate, then go to the hosting recommendations, WordPress tutorials, SEO lists and other pages to continue to see.

proceedings

Determine what is used in the backend first

Newcomers to business websites, blogs and content sites usually start with WordPress, so don't spend too much time comparing programmes over and over again.

WordPress Priority Don't get hung up on it, CMS.
See WordPress tutorials →

domain name

Pre-branded access address

Domain names should be as relevant as possible to the brand name, company name or core business, with attention to renewals, resolution management and transfers in and out.

short and memorable Renewals can be controlled
Look at the domain suffix selection →

Hosting

Determine the operational stability of the website

Regular business websites and blogs look at web hosting or light cloud servers first, focusing on stability, speed, backups, customer service and WordPress compatibility.

Revenue Core Entry Priority stabilisation
See hosting recommendations

thematic

Decide on page structure and visual basis

The theme is not the more fancy, the better, the official website of the enterprise prioritises to see the effect of mobile, loading speed, whether the module is enough and subsequent updates.

Mobile effect Lightweight and stable
See topic recommendations →

plug-in (software component)

Replenish functions as needed, don't fill them all at once

Plugins mainly address SEO, forms, caching, security, backups, multi-language and mall features. First build the page, and then fill in the plug-ins as required.

SEO form (document) (computing) cache
See the list of plug-ins →

element

Content affects speed to market more than tools

Company profiles, service descriptions, product information, case studies, pictures, contact information and form copy are best prepared in advance.

Company Information Case Photos
Look at the general page of the site locator →

SEO

Prepare the basics before going live SEO

Keywords, column structure, page titles, descriptions, sitemaps and statistical tools are recommended to be configured as soon as possible before and after going live.

Title Description Inclusion statistics
Look at the SEO checklist →

Safety / Performance

Pre-launch processing HTTPS, backups, caching and background protection

SSL, backend accounts, plugin updates, theme updates, regular backups, caching and base protection all fall under the maintenance costs of self-hosted websites.

HTTPS backing up
Look at performance and cache optimisation →

Recommended Routes

Newbies don't study all the resources at the same time and advance in order

The purpose of a resource page is not to let the user see more and more, but to let them know what to do next. Most self-hosted websites can go in this order.

01

redaction process

Default WordPress, compare other CMS for special projects.

02

finalise a domain name

Determine brand name, suffix, resolution and renewal.

03

Mainframe

Prioritise stability, speed, backup and compatibility.

04

Installation procedures and themes

Start by building out the basic page structure.

05

Collation of content

Complementary company, services, cases, pictures and contact portal.

06

On-line inspection

Configure SEO, statistics, SSL, backups and caching.

the next step

After looking at the list of resources, follow these three actions to continue

Don't continue to look for information indefinitely. Determine the route first, then start building, and finally do the on-line check.

initial step

Choosing WordPress Hosting

second step

Follow the tutorial to build a website

third step

Do an on-line check

Other programme resources

Don't want to maintain your own hosting and programming? You can switch routes.

Back to Resources Overview

SaaS Website Building Resources

Platform accounts, packages, templates, domain bindings and content preparation.

AI Website Resources

Branding materials, cue words, first drafts of pages and subsequent optimisation.

Custom Development Resources

Requirements documentation, prototypes, feature lists, interfaces and deployment environments.

Mixed programme resources

Multi-platform portfolio, data synchronisation and phase upgrades.