Jump to content

Nillervision

Privileged
  • Content count

    1,604
  • Joined

  • Last visited

  • Days Won

    2

Nillervision last won the day on April 16

Nillervision had the most liked content!

1 Follower

About Nillervision

  • Rank
    All-rounder
  • Birthday 07/15/1968

Users Experience

  • Experience
    Advanced
  • Area of Expertise
    Web Designer

Contact Methods

  • Website URL
    http://nielsharbo.dk/

Profile Information

  • Gender
    Male
  • Location
    Copenhagen, Denmark
  • Interests
    Web development, design, music

Recent Profile Visitors

13,075 profile views
  1. Cakewalk by BandLab - New Free DAW for Windows

    Thanks for sharing. Ive been a Logic user for over 15 years. But Cakewalk is absolutely a great platform.
  2. Looking for constructive criticism/feedback

    Though these are all valid arguments for using a CMS it is not certain its the best solution for OP. Static HTML/PHP files loads faster than CMS pages because there are no database queries. With a little PHP knowledge you can include a header, menu, footer etc. on a 'static' page as well instead of copy/paste. Wordpress and most other CM systems performs database queries based on parameters in the url. This makes the site much more vonurable to attacks than a static site. The query parameters can also give a beginner problems with duplicate content/multiple urls. The same goes for different post types. All in all a CMS is very powerfull but it takes a lot of experience to set it up the right way. For someone with HTML skills, but no knowledge of backend development, static are often a better solution.
  3. new nominees and winners?

    I think it would be nice to see the competitions again. but I'm not sure that we would get enough contributions. At the moment most active users here are developers with little or no design work to show.
  4. Slide Show?

    You can build it yourself very easily. A slider like that doesnt even require javascript. I've made a tutorial showing how to do it with pure CSS animations: DEMO AND SOURCE DOWNLOAD: http://nielsharbo.dk/?lang=en&page=tutorials&post=css-slider
  5. Too Old?

    Its not to late. I started to develop webpages in the late 30s. When I was 40, I went to uni to take degrees in design and webdevelopment. Now I am almost 50 and employed as a frontend lead developer at an agency. If you have a pasion and interest for the trade, it is never to late to start Keep in mind that it will take a long time to build experience and skills enough to earn a good pay in this business. And you will have to keep educating yourself to stay up to date with the latest tech, development models, design trends etc.
  6. Valuable Feedback

    Hello Neik. Welcome to the forum. If you want to build credibility as a theme developer you should really be working on optimizing your own site, https://developers.google.com/speed/pagespeed/insights/?hl=en&url=https%3A%2F%2Fwww.themevault.net%2F&tab=desktop A PageSpeed Insights score of 30 is really not good enough Suggestions for better UX. Use a honeypot instead of captcha in your contact form Get rid of the slidetoggle on the FAQ page, unless you plan to have longer answers. Why bother the user with having to click to reveal just one or two lines of text The automatic pop up will most likely just annoy users. Nobody will react to it before having a chance to read your offers. And google might punish you for it; https://www.theverge.com/2016/8/23/12610890/google-search-punish-pop-ups-interstitial-ads Most importantly: I think you need to work a lot on your brand and credibility. Let the user know who you are. Your site has zero information about you: no images of you or your team no about-us page no info about your location, your pasion for design or your values, mission, vision etc. no testimonials from happy clients.
  7. Jquery viewport trigger

    This method returns true if the current element is in the viewport jQuery.fn.isInViewport = function() { var elementTop = jQuery(this).offset().top; var elementBottom = elementTop + jQuery(this).outerHeight(); var viewportTop = jQuery(window).scrollTop(); var viewportBottom = viewportTop + jQuery(window).height(); return elementBottom > viewportTop && elementTop < viewportBottom; }; Usage: if (jQuery('.my-element').isInViewport()) { //do something } DEMO: https://jsfiddle.net/Nillervision/fmgjbkps/ Note that this example is not listening for scroll events (which can be heavy for the browser) Instead the function is running on each animation frame: I'm not 100% sure but I think this give you a better performance because each frame is parsed by the browsers js engine anyway, and the interval between the frame "events" is determined by the device itself: var scroll = window.requestAnimationFrame; function loop() { if (jQuery('.my-element').isInViewport()) { //do something } // Recall the loop scroll(loop) } // Call the loop for the first time loop(); To support old browsers you can fallback to vendor prefixes or even a timer var scroll = window.requestAnimationFrame || window.webkitRequestAnimationFrame || window.mozRequestAnimationFrame || window.msRequestAnimationFrame || window.oRequestAnimationFrame || // fallback to timer function(callback) { window.setTimeout(callback, 1000 / 60) };
  8. WooCommerce Size etc. Dropdown option

    This functionality is build into woocommerce it is called variable products. https://docs.woocommerce.com/document/variable-product/
  9. I'm sure this is only an issue because you have some links containing the query string somewhere on your site. Probably because of a quick copy/paste action, check the urls in your menus and inline links in your posts.
  10. What is the correct order of a site design

    Take a look at this test. Test Five: Background Image Where Desktop Image Set with Min-Width https://timkadlec.com/2012/04/media-query-asset-downloading-results/ Edit: I also found this: Source: https://www.mightyminnow.com/2013/11/what-is-mobile-first-css-and-why-does-it-rock/
  11. What is the correct order of a site design

    OK. Let me explain how I've reached this conclusion. Mobil first is a progressive enhancement model (at least from what I read everywhere). That means that our core product is designed to support the devices with the most limited features (in this case screen size/resolution) After we have provided our initial styles we gradually check if the device supports larger resolutions and if so we enhance the initial features (Alows the content to float in to columns etc.) If we were structuring our CSS in a way were the core styles (initial rules) would apply to larger screens and gracefully degrade to smaller screens, we would no longer be designing after a progressive enhancement model.
  12. Could be that the sitemap generator is indexing search results. ?s= is the url key that WP uses for search queries. If you are worried that search engines will make the same "mistake" as the sitemap generator you could take one of these precautions: Note: First of all go through the internal links on your site and make sure you dont have any links with the search query string in it. METHOD 1 In your robots.txt file add this line to prevent indexing of any search queries Disallow: /*?s METHOD 2 In your documents head element (probably located in header.php) you can use a Wordpress function to check if the page is the search result page (which can have endless amounts of URLs) and add a robots meta tag. <?php if ( is_search() ) { echo '<meta name="robots" content="noindex">'; } ?> Or use the Youst settings to do it manually on each page. (you can also manually set a canonical url) https://kb.yoast.com/kb/canonical-urls-in-wordpress-seo/ METHOD 3 Submit a sitemap to Google, Bing and other search engines with only the URLs you want indexed
  13. What is the correct order of a site design

    Not entirely. The mobile first approach also has to do with the structure of your CSS. All your your initial CSS (outside any media queries) would be the only CSS loaded on the smallest screens. Overrides to these initial styles would be placed in min-width media queries and would ONLY be loaded on larger screens which often goes hand in hand with faster connections. When using the desktop first approach the initial CSS rules would be for the largest screens possible. Devices with small screens would have to read all this CSS code only to have it overridden later by styles defined in max-width media queries.
  14. Looking for constructive criticism/feedback

    First of all thanks for making good use of my pure CSS slider @GrahamUK33 If you want I can place a HQ link on the tutorial page so people can see an example on a live production. Back on topic: When in doubt. I think it is always good to give the user a choice. Some users like scrolling, other users might prefer other options. To accommodate for this you could place a bar at the top of the timeline with either inputs for filtering or simple links, like @fisicx suggested. Here's an example fiddle: https://jsfiddle.net/Nillervision/9z3sqm1o/
  15. With "rendering" do you mean the browsers WebGL API? If so remember that everything in your 3D scene has to be compiled to JavaScript and transferred to the client over http and interpreted and rendered in a browser (which BTW was never designed for 3D calculations). With that in mind WebGL is pretty amazing. No matter what software you use to publish your 3D models on the web, you will see performance problems and slow load times if your scenes are to complex. Also, you never know the users specs (graphic card, CPU etc.) so it's really important to optimize your scenes as much as possible. A few tips for optimization: Bake details into a normal map and use the decimate modifier to reduce the polycount afterwards. Limit the number of light sources to a minimum and bake ambient occlusion and shadows into your textures rather than having them calculated in real time. Compress your bitmap textures as much as posible, and try to fit your textures to square images (256x256, 512x512 and 1024x1024 with JPEG compression usually works well) If you have repeating/ similar objects in your scene, use instances (objects with the same mesh and material data) rather than unique copies EDIT: You might also consider at gzip compression. You can either enable that in your servers configuration (.htacces file) or for the individual 3D scene
×