How to quickly make a website

Favourite cms ( like Joomla and Worpress ) have a vast community where you can find or ask a great deal of information.

Many plug-ins (both free and paid) that allow you to create truly fun sites. Disadvantages: Mostly a similar choice for you is to use a site Builder provided by the host where you buy your shared/sharing. Disadvantages: If you ask for a page, but not a website, you can try Facebook pages.

I use Weebly in my case when I need to quickly build a website. This allows you to Pinterest type contents, provide web addresses, post PDF and PPT files (currently for me), and you always have a good looking easy page with contents to split. It'?s a page, not a website.

Go to Worpress and set up your free online registration and check your domains. It' s like a million different template for Worldpress out there that are completely free. Make a new filename index.html with the content:

Getting any website to respond quickly and simply

Verisign Domain Name Industry Brief for 2013 estimates that 85% of all com and . net Top-level Domain names (TLDs) have websites: that's over 100 million websites[that's .com and .net domain names together over 120 million]. Well, that's a bunch of sites!

So, how exactly are we gonna make them all react? I' m sure if you have an existent website that doesn't respond, you probably thought about how you would make it mobile-friendly. It is really difficult to disagree with the current trends, as today more than 25% of all web travel is generated by mobiles, and revenues from mobiles (phones & tablets) currently exceed those of PCs by more than 6 to 1.

Your website has to be portable, it doesn't matter anymore. Rebuilding a reactive website from the ground up is simpler today than ever before as framework and technology have been enhanced. But with all these unresponsive sites, we need to find ways to quickly and easily upgrade them with fast-response improvements.

I' ll present a step-by-step procedure in this paper to make every website appealing with an appealing web designer frameworks named Restive. JS, and with a very realistic and very beloved website as our example. In order to begin, we need a website that is our experimental rabbit. Thought it would be best to use a website that is quite appealing but does not react native.

Therefore, I chose to use the EnergyBnB website for this tutorial because, believe it or not, it does not respond native (it diverts mobiles to a specific mobiles subdomain). Visiting airbnb.com with a Google Galaxy Nexus, I was diverted to m.airbnb.com where I got a listing of results I wasn't specifically looking for, plus a number of promotional hyperlinks such as "Sign Up", "Sign Up" and a very famous hyperlink to downloading the application for Android (which I already had on my phone).

A few of the interesting things on the initial website like "Neighborhood Guides" as well as the community networking a la Facebook, Twitter, etc. were missing. Nothing against WaterBnB, but I would have liked to have seen a reactive copy of the orginal website and then decided for myself if I wanted to get the application.

So I would have liked it so much that I will make a responsive copy of the AirBnB website. Exclusion of liability: This Tutorial is not supported or approved by AirBnB in any way. It' is intended to provide guidance on how to upgrade your website to make it reactive, and is nothing more than that.

End results are for test use only and should never be used as a replacement for the initial website of Adobe Airborne BnB, which will remain at www.airbnb.com. Not disrespectful of the other webmasters out there - especially Mozilla Firefox - but Google Chrome is fantastic if you're a web designer, especially because it has a built-in mobile emulator that I consider important.

You can also use any web browsers with good development utilities and then test them with your favorite portable simulation tool. We' ll make some changes to HTML and some CSS so that you'll need a text editors, everyone will. It' a jQuery plugin[or framework, if you like] that will help you get a website up and running almost immediately.

Respond with less code and less effort. What JS is about is that it allows you to create all your highly reactive CSS markups online, as opposed to using query forms that split your highly reactive markups into different "markup realms" that you have to administer seperately. In order to get the website of my airline, I just open the web adress in my web navigator and store the whole website.

Then I made a copy of the initial index. html and called it index.orig. html; that's just so we can easily check changes later when we need it. Let's find out if the AirBnB homepage uses jQuery; I suppose it does, but just for the arguement's sake, let's double-check.

and we will be adding the source file and mark-up directly under the jQuery scripts above: Above we' ve set 3 choices in our above File & Mark-up,'Breakpoints','Classes' and'Turbo_Classes' and I will only briefly describe what they do. Holdpoints and class are the most important choices in Restive.js.

They do this by creating defined key point areas and then applying classifications to the specified selected area because the width of the device's Viewer on our Web site corresponds to that area. â??240-cssâ?, â??320-cssâ?], the plug-in would set the key point areas from 0 to 240-pixel and 241 to 320-pixel, and then it would append the 240-css category to the tag (which is our selector) if the device's opinionport width falls between 0 and 240 pixels, and it would append 320-css if the opinionport width falls between 241 and 320 pixels.

That' more or less the way these two choices work together. js, which add to our tags classes[in addtion to the class definitions in the class option] if certain predefined requirements are fulfilled, e.g. if the machine is a portable machine, if the machine is a tray, etc., is a particular Restive thing.

For example, is_landscape=landscape will tell the plug-in to append the classescape to the tags when the unit is in horizontal format, and since Restive. ys is state afflicted, this classes will also be deleted when the unit changes to upright. nb'] to generate a region from 0 to 10,000 pixel that is suitable for all units.

This means that if you have a telephone and are visiting our upgraded Restive website. The JS will ensure that the mobiliyphone portrait category is added to the tags, as the unit is a portable one, it is a telephone, and it is in vertical format. Having set it all up and almost up and running, we've decided to make the fast-reacting improvements we want to make to our website.

It is very important to concentrate clearly in advance on what needs to be changed on the website. I' ve made some comments about the AirBnB website screenshots, which you can view as needed; it contains some strategic hints on how we will make these highly reactive improvements.

Then, we identify all the general rapid -response improvements [as tasks] needed to make our site ready for use. On one side there is the division of the Layoutzone, on the other side there are the fast reacting improvements for portable units. Any future response enhancement will be done via our RSS system.

Inside the Developer Tools API it is very simple to see all the HTML here, but there is no need to copy and paste all the HTML. Seeing as the mark-up is long, I show sections of markup[or code] as described below: Every mark-up in it that isn't immediately pertinent will be truncated[it's still there, but I just won't show it] and substituted by the HTML annotation with the heading'MARKUP TRUNCATED'[I'll do the same for Javascript with the heading'CODE TRUNCATED'].

I will also specify which layout zone we are looking at by using another HTML annotation in the first line of the section of HTML coding. Thus the fundamental approach is that I describe the objective of the task that is needed to make the intended responsive improvement possible, then comes the HTML mark-up and then the CSS mark-up.

I' ve also written a blogs posting on Testing Responsive websites that might be of use. Exercise 1: First, reset all important fixed-width items so that nothing interferes with the viewing window width of a portable unit. "Job 2: The second job is to hold the headers in place for your portable equipment so that the navigational toolbar always stays in place whether we are scrolling up or down.

"head " "header" "navbar navbar-top" "navbar-inner"... Task 3: Now this job is a blast. We need to activate two different navigation types, one for the initial site and the other for the portable site. You must, however, occupy the same mark-up area. Therefore, we need to insert an HTML mark-up, i.e. div#nav-left and div#nav-right, which contains the navigation system for the phone; this must be concealed on non mobiles.

Similarly, on portable terminals we need to disable the initial website's navigator. Finally, let's build an imagesprite for the icons that are needed for our portable interface. png" "/" "brand airbnb" "nav-right" "nav-new" "nav-new-search" "#" "nav-button-search" "nav-new-button" "nav-new-button" "nav-sprite icon-search" "img/transp" "#" "nav-button-actions" "nav-new-button" "nav-sprite icon-actions" "img/transp" "#" "nav-button-actions" "nav-new-button" "nav-sprite icon-actions" "img/transp" "img/transp" "#" "nav-button-actions" "nav-new-button" "nav-sprite icon-actions" "img/transp" "#" "nav-button-actions" "nav-new-button" "nav-sprite icon-actions" "navg/transp" "img/nav-.

Exercise 4: This exercise is a certain complement to the preceding exercise. Since we will have two different navigationalUIs, and there is not enough room to activate the drop-down menus of the initial site, we need to add another contents area below the top navigational panel; a sub-navigational panel, or the like.

Javascript to activate this function of the subnavigation toolbar follows our Restive. It'?s a JP key. To find the full source for it, view the definitive index. html at the end of this Tutorial. Exercise 5: The fifth exercise concerns the reorientation of the AirBnB logotype.

Located to the south of the head area on the initial website. "The " "navbar-inner"" "container container-full-width page-container" "/" "brand airbnb" ....::::::::: or:::: problem 6: For this problem we will enable some reactive extensions for the area "hero". You can do this quickly, but just to make things easier, let's just jump over that so we don't do this practice anymore.

We will also make some temporary changes to the divs. search area.

Exercise 8: This exercise is primarily devoted to the Neighbourhood Assistance section. Not only do we have to fold the picture tile elegantly, we also have to keep it reactive. But I managed to find some hints on how to make wallpaper sprites react and change the size of a Div while keeping the page ratio; I used this logics to get the desired outcomes.

Exercise 9: This exercise explores the contents just before the footnote, i.e. where we have the headlines "Travel", "Host" and "Trust and Security". It is a fairly simple breakdown surgery where we place the items vertically rather than horizontally. However, it is not a simple breakdown surgery. "2 "2" "content-2" "page-container page-container-fixed" - Exercise 10: This is the last exercise - Pooh!

Again, a straightforward job of compressing the outline. We didn't have to make HTML supplements or upgrades here. I' d recommend you try both first with your web browsers and then with your portable web browsers (via the emulator). Since I have been using the MoE all along on Google Chrome DevTools, it was quite straightforward to see what the upgraded website looks like in a simulation telephone world.

But I have two portable gadgets at hand: an iPod Touch[4th generation] and a Google Galaxy Nexus and have tried it on every gadget, with practically the same results on every gadget. That' s why we used the . mobili custom style sheet only ( although we could be more specialized ).

A little more hassle will allow us to further refine the site to look a little different on tables, as there' a lot more room for working on tables, especially in horizontal format. That' s why we created a perfect website that didn't react native, and we made it appealing in a series of stages that should be standard for most webmasters.

It took the entire lifecycle about 4 to 5 hrs from beginning to end, requiring some harmless HTML mark-up upgrades and a further 70 rows of extra CSS mark-up. JetS: Reactive web redesign workflow is greatly enhanced as all fast-response CSS markups are available in-line and more intuitive, removing the shared awareness challenge of using press releases.

There is no need to test upgraded web sites on different portable computers anymore; once it works on one portable computer, it will work almost on all. The Turbo Classes function allows you to use in-line CSS rules preferences such as .mobi. tablet[for tablets],.mobi.phone.landscape[for telephones in horizontal format], etc. to quickly expand the format factors and orientations.

Keeping your reactive CSS mark-up up and running will be much simpler because it's all in one place. It is not necessary to revise the mark-up in several " mark-up Realms ", since you would probably have to use medium inquiries. Responsible web designing must become a much more effective proces if it is to find the mass acceptance we want from it.

One good way to achieve this is a better and quicker construction process. Native web responsiveness will be a good thing for everyone, especially on the move. Down a website... a few billion more!