Skip to content

Instantly share code, notes, and snippets.

View johanoloflindberg's full-sized avatar
💭
Ready to work 😃

WEBBAB johanoloflindberg

💭
Ready to work 😃
View GitHub Profile
@johanoloflindberg
johanoloflindberg / fluidapp_default_prefs.txt
Created November 21, 2016 03:15 — forked from itod/fluidapp_default_prefs.txt
Altering FluidApp default user preferences
This should be possible by cracking open Fluid.app (Fluid itself, not Fluid apps you create, mind you), and editing this config file:
Fluid.app/Contents/Resources/FluidApp.app/Contents/Resources/FluidApp-DefaultValues.plist
All of the default user defaults (aka user preferences) are stored here. Subsequent Fluid Apps created by this Fluid.app instance will have these default preferences.
@johanoloflindberg
johanoloflindberg / feedbin.js
Created November 21, 2016 03:15 — forked from itod/feedbin.js
FeedBin Fluid
window.fluid.dockBadge = '';
setTimeout(updateDockBadge, 1000);
setTimeout(updateDockBadge, 3000);
setInterval(updateDockBadge, 5000);
function updateDockBadge() {
var newBadge = '';
var els = document.querySelectorAll('.feed-link .count');
for (var i = 0; i < els.length; ++i) {
@johanoloflindberg
johanoloflindberg / instapaper_userstyle.css
Created November 21, 2016 03:14 — forked from itod/instapaper_userstyle.css
Kill Fixed Position header in Instapaper
// Starting with: https://www.instapaper.com/read/
#controlbar_container {
position:static !important;
}
@johanoloflindberg
johanoloflindberg / gmail_userscript.js
Created November 21, 2016 03:14 — forked from itod/gmail_userscript.js
Fluid Gmail Userscript
window.fluid.dockBadge = '';
setTimeout(updateDockBadge, 1000);
setTimeout(updateDockBadge, 3000);
setInterval(updateDockBadge, 5000);
function updateDockBadge() {
var newBadge = '';
// loop thru anchor tags
var anchorEls = document.getElementsByTagName('a');

Vi bygger om!

Holding page

HTML5 Markup Template - Basic

A very basic starter template with fundamental HTML5 markup -- only the basics.

Based on HTML5 Bones | http://html5bones.com

@johanoloflindberg
johanoloflindberg / checklist.markdown
Last active September 19, 2015 06:39 — forked from tillsanders/checklist.markdown
You-will-be-in-mortal-danger-if-you-dont-follow-this-checklist-checklist

The You-will-be-in-mortal-danger-if-you-dont-follow-this-checklist-checklist

Common pitfalls

  • Caching and temporary directories accessible (permissions!) by webserver
  • Webfonts available for production domain

Security

  • Are email adresses (a little) protected?
  • Do you need a captcha somewhere?
  • Debug disabled
@johanoloflindberg
johanoloflindberg / Web Projects Checklist
Last active September 19, 2015 06:39
Checklist of things to think about when working on a Web project.
Questions for Client:
List of things that are often overlooked by the client. It can be a big time saver to ask for these elements as soon as you step in a project. You can check them here as you receive them from the client, they are repeated down below for when you will develop the website.
Design:
- Button & Link states (hover, active, visited)
- Transitions and animations
- Fonts
- are the fonts available on a Font Service (Google Font, Typecast)
- if not, is there a Web licence available for that Font ? If yes buy it.
- favicon
- image for facebook sharing
@johanoloflindberg
johanoloflindberg / Launch-website-checklist
Last active September 19, 2015 06:39 — forked from bu-s/Launch-website-checklist
Pre-launch website checklist to be used prior to setting a website live!
EDITORIAL
*************************************************
Spell check
Review for grammar and punctuation
Consistent terminology
Heading levels are appropriate
Style guide compliance
Ensure no test content on the site
SEO VISIBILITY
@johanoloflindberg
johanoloflindberg / HTMLchecklist.md
Last active September 19, 2015 06:39 — forked from billmei/HTMLchecklist.md
Checklist to have a W3C compliant, secure, SEO friendly, mobile-friendly, maximally-compatible HTML site.

Checklist for new websites

Once you're done coding your site, go through this checklist to make sure you have a W3C compliant, valid HTML, secure, maximally-compatible, optimal-performance, responsive and mobile-friendly, SEO-friendly website.

SEO

  • <title> is keyword friendly
  • <meta name="description" content="" />
  • ``