CHEWX

Anything to do with the LinkedIn Api requires oAuth. Documentation on the Api isn't great tbh.

I'd wrap the posts and remove the float from the posts and add it to the wrapper. Personally I mark-up like the following. <header> </header> <main> float: left; width: 70%; </main> <aside> float: right; width: 30%; </aside> <footer> </footer>

What does the verify() function do ?

“There's more than one way to skin a cat.” - Honestly. I have just completed a website where the clients wanted to build all the pages that weren't using a CPT. I just built this using ACF flexible content.

Try, if( stristr( $_SERVER['SERVER_NAME'], "http://brkts.tst.8000" ) ) { define('WP_HOME','http://brkts.tst.8000'); define('WP_SITEURL','http://brkts.tst.8000'); } Obviously, change the http://brkts.tst.8000 to whatever.

After reading this from yesterday - it's deemed a good idea - http://moz.com/blog/15-seo-best-practices-for-structuring-urls So I've changed 'admiretheweb.com/the-article-featured' to use 'admiretheweb.com/articles/the-article-featured' from a simple CPT slug rewrite, they are all now in their own CPT and do not conflict with 'inspirations', which they were a category of (Yes, I built the site 4 years ago). In the process of changing 'admiretheweb.com/the-website-featured' to 'admiretheweb.com/inspiration/the-website-featured' which was a case of changing the default post permalink structure. admirethweb.com/%postname%/ to admiretheweb.com/inspiration/%postname%/ however, all my posts will 404 from Google, so need to work out a clever way to 301 re-direct from postname to /inspiration/postname - not worked that one out, it's easy the other way round though :/ Links will stay as they are as they are a new section to the website and have been set-up correctly from the start essentially. I will drop 'category'/'taxonomy' from all slugs as their section slug already say what they are (this is the single page URL's only).

Inspiration, Links and Articles are three different things, they all need a post type, Articles will use standard posts and then the other using post types. That's the easy bit. Although at the moment Inspiration uses standard posts and Articles is just a category of Inspiration (the site was built 4 years ago, I didn't know where I was heading). But I can split this now and make it better for the SERPS or just leave. I just don't want to set-up the URL structure for no gain, I can keep it as it is.

Hi, I am considering re-strucuring my website for web design inspiration. Currently the domains are: admiretheweb.com/the-website-featured admiretheweb.com/the-article-featured admiretheweb.com/links/the-link-featured Would it be better to do: 1) admiretheweb.com/inspiration/the-website-featured or admiretheweb.com/inspiration/category/the-website-featured The inspiration would always be so, so I guess it would be a Custom Post Type. 2) admiretheweb.com/the-article-category/the-article-featured or admiretheweb.com/articles/the-article-category/the-article-featured This essentially will be a Custom Post Type, but it isn't, so maybe the 'articles' part isn't needed. 3) admiretheweb.com/links/the-link-category/the-link-featured Again, a CPT. As the website is WP, it will redirect all old URL's, but is it worth it ?

Personally, I'd use ACF gallery plugin. Loop the images into thumbnails. Then use Magnific light box which will work responsively.

The example looks to be working. Can this be closed.

CSS. Firstly make sure the background images are no larger than 500kb each. Size wise, depending on the image, 1600px should suffice in width. Then: body { background-position: 50% 50%; background-size: cover; } Be aware that background size cover is only supported down to IE9. http://caniuse.com/#search=background-size You can look at other solutions here: http://css-tricks.com/perfect-full-page-background-image/

Best to write your own. I forked one from GitHub and then heavily modified it. I then set it up in bower and then just bower install it when I want to start a new project. https://github.com/CHEWX/motherplate I don't think it'll ever be perfect because new techniques are emerging all the while, so you will need to continue to iterate the boiler-plate.

Without seeing the code, it's kinda impossible to know...

Ask what browser, and then try and replicate in http://www.browserstack.com

I don't think 123-reg understand the problem, you do not need to change your name servers. Unless your domain is registered elsewhere, then you will need to change your name servers to 123-reg, but that is not entirely accurate because you could just point an A Name to your 123 reg hosting. Before that is done, you need to export your database from your MAMP's PHPMYADMIN and then go to your hostings PHPMYADMIN and import the SQL file. You will then need to find and replace the URL's by running the query below. UPDATE wp_options SET option_value = replace(option_value, 'http://www.oldurl', 'http://www.newurl') WHERE option_name = 'home' OR option_name = 'siteurl'; UPDATE wp_posts SET guid = replace(guid, 'http://www.oldurl','http://www.newurl'); UPDATE wp_posts SET post_content = replace(post_content, 'http://www.oldurl', 'http://www.newurl'); UPDATE wp_postmeta SET meta_value = replace(meta_value,'http://www.oldurl','http://www.newurl'); Then you need to use FTP or GIT to transfer your files from local to your hosting environment. All should be complete. FYI, developing with Wordpress can get tiresome with a live website. I would advise getting Migrate DB PRO to keep your local database up to track your live database. You cannot use 1 database unless you point your local files to your live db, which is not advisable.