Jump to content

BrowserBugs

Privileged
  • Content count

    2,129
  • Joined

  • Last visited

About BrowserBugs

  • Rank
    Unhinged

Users Experience

  • Experience
    Intermediate
  • Area of Expertise
    I'm Learning

Profile Information

  • Gender
    Male
  • Location
    Surrey, UK

Recent Profile Visitors

17,141 profile views
  1. If someone already has a website then they have hosting. You 'could' build the new site in their space so long as you're careful not to overwrite the live site, but it's risky for sure. I'd suggest getting some cheap space of your own to develop the new site in. If you setup the hosting under their domain you could either use a sub domain based on their domain as an alias, build the site and then migrate it to their live server once ready. Option 2 without a sub domain would be the same but instead of using a sub domain you could use your hosts file to view the new site in your browser when the rest of the world would get their current live site, this is safer as there is no chance of a duplicate site (e.g. both sub and main urls are being indexed). Either way you cut it you will need development space or be extremely careful in their live hosting. As many point out there's some dirt cheap hosting out there ideal for developing multi-sites, e.g. TSO has host 3 sites for £4.58 per month, just cancel the hosting when you're done.
  2. Front end before or after backend?

    Back end first if complex. Generally the nips and tucks behind the scenes will dictate the UI requirments, at the end of the day it needs to function first and look pretty / ux later.
  3. Not a wordpress site

    Most security flaws will be with regards to variables your page accepts. Security attempts are made by trying to manipulate the variables, either via the url parameters or posted form fields with something else. I'm 99% sure PHP only listens to the variables given however this is where validation, sanitation and checks are vital. It's also down to selecting the right choice for each variable with php, $_GET (Requests data from a specified resource), $_POST (Submits data to be processed to a specified resource) or $_REQUEST (Could be $_GET, $_POST or $_COOKIE data - more open to manipulation) are the three options. An example of $_REQUEST is both /yourpage.php?name=Jim and a form input <input type="text" value="Jim" name="name"> posted would work, but if you were expecting a form input call it by name using $_POST. With a contact form the process should be $_POST['name'], then validate the content, in the case of a name you could validated to exclude anything not used for someones name like @, ?, etc. Final step is sanitise, so if storing it escape the string and use prepared statements. With the validation step you can get really creative, the idea being regular people inputting regular stuff sail through and anyone trying to manipulate your php gets caught in the validation steps.
  4. The end of the 'listicle'?

    I think i'm "10 best" blind these days, like google ads when they first started appearing people looked, now it's just white noise
  5. What is your preferred way of building Websites?

    The one thing I have learned is to try and gauge client commitment from as early as possible in the planning stage. Often they will want 'gallery', 'blog' or 'showcase' sections yet once complete and the site is live they either lose interest or are too busy to keep it up-to-date ... and if not kept up to date these sections serve as a thorn in their side rather than the goal of "feature rich quality content". It's better to hire a writer to create some timeless copy and run a static site. How I tend to develop sites for my clients is to assume everything is static e.g. nice content about their service etc. Then for things like price from, testimonials, opening hours, adding a showcase and other things like that would be controlled from a simple CMS, essentially form to database which i scratch write (or use pre written modules of my own) depending on requirements. With this approach rather than letting them have WYSIWYG gives you as the designer more control over the overall look, you can add validations before publishing e.g. everything must have a title and description etc, all this combined helps keep the quality of the site high. Here's an example, one of my clients is a tuning company with a showcase controlled by simple forms to database. When they input the starting power and torque then their tuned power and torque we now use the data to form charts. It's this sort of thing I love to build in, their showcases are feature rich and generate leads of people wanting similar, all from a minimal CMS.
  6. They have their uses, their benefits although marginal offer visitors an index to the site and search engines a clearer picture to the structure of your site, coupled with breadcrumbs it makes the search engines job easier to apply site wide and section scope terms, the parent and sibling structure they tend to like. HTML site maps have no negative effects if made correctly, so a safe bet to include one. Instead of a site map I tend to treat them as the index of a book. In the instance of xml sitemaps these once connected with Google search console are integral to understanding what's you've requested to be indexed vs Googles actual index count. I've seen many a web master assume it's just to 'make google index these pages' rather than to spot possible problems, grave mistake, if Google has 3412 indexed pages and your xml map says there should be 256 then alarm bells should be ringing.
  7. Hi, I'm not 100% sure what pages should be in your site map, what are 'all' your pages? I did notice some strange navigational links that go nowhere. Take for example the top navigation; Flights, Hotels, Packages and Cars. None of them link anywhere, clicking them does nothing. Also on the https://www.faremakers.com/SiteMap page, again we've Flights, Hotels, Umrah Packages, Holiday Packages and Cars linking to nowhere. Cheers,
  8. What are the ideal breakpoints and font size?

    Nail on the head. I like to think in terms of available space based on screen size and not it's a 'mobile' or 'tablet' device; 1024px is simply 1024px, nothing to do with what the screen is attached to or which way round it is. When I first started with responsive design I had so many orientation rules; now I have next to none.
  9. What have you been up to?

    Well slowly, I'm all good working with them as css backgrounds, having some issues with IE and using them as an image, oddly as a background image they work fine :s
  10. What have you been up to?

    Welcome back! I've been messing with SVG thanks to you
  11. New site! Let us know what you think.

    One thought; I just spotted we have a 'E-Commerce' section; would that not be better under server side or CMS? Either they will want to connect their CMS to a payment provider or they'll want to implement a payment api server side for processing .... just a thought.
  12. What are the ideal breakpoints and font size?

    "Google is rolling out a new mobile-first index. This means Google will create and rank its search listings based on the mobile version of content, even for listings that are shown to desktop users." - 9 Nov 2016 Source. A well designed responsive site will tick both the desktop and mobile crawler index. I think many mistakenly take 'Mobile First' as a rule, make a mobile site and then just scale it up for a desktop. The problem with this approach is often the desktop version has super large fonts to compensate, or has lots of dead space, or ends up with a hidden navigation which although works well on a phone is not the best user experience for a desktop. The industry used to have the reversal issue, people trying to shoe horn in a desktop site on a phone. There's a balance to be found for each individual site for desktop, tablet and phone. Just my 2 pence worth
  13. What are the ideal breakpoints and font size?

    yes, that would be fine. I would suggest though choosing a measure and sticking to it for fonts, makes life easier in the long run. If you use that link I sent you select your base font size and it shows scaling up and down values.
  14. What are the ideal breakpoints and font size?

    The sticking point is the initial 16px font size; 16px = 1.000em = 100.0% = 12pt; so why not just say font-size:100% or font-size:1em at the start? See http://pxtoem.com/. The reason is ...
  15. What are the ideal breakpoints and font size?

    Both the font size and break points can be used to make a site responsive. Here's a really simple fiddle, https://jsfiddle.net/xjknap8L/, as a demo I decided to use 516px as the point I think the col div gets too small for the content, just a random number to show it's not a 'set' point in terms of device or orientation.
×