Creating a totally custom design for your publication

Ghost comes with a beautiful default theme called Casper, which is designed to be a clean, readable publication layout and can be easily adapted for most purposes. However, Ghost can also be completely themed to suit your needs. Rather than just giving you a few basic settings which act as a poor proxy for code, we just let you write code.

There are a huge range of both free and premium pre-built themes which you can get from the Ghost Theme Marketplace, or you can simply create your own from scratch.

Anyone can write a completely custom Ghost theme, with just some solid knowledge of HTML and CSS

Ghost themes are written with a templating language called handlebars, which has a bunch of dynamic helpers to insert your data into template files. Like {{author.name}}, for example, outputs the name of the current author.

The best way to learn how to write your own Ghost theme is to have a look at the source code for Casper, which is heavily commented and should give you a sense of how everything fits together.

• default.hbs is the main template file, all contexts will load inside this file unless specifically told to use a different template.
• post.hbs is the file used in the context of viewing a post.
• index.hbs is the file used in the context of viewing the home page.
• and so on

We've got full and extensive theme documentation which outlines every template file, context and helper that you can use.

If you want to chat with other people making Ghost themes to get any advice or help, there's also a themes section on our public Ghost forum.

Ghost has a single, powerful organisational taxonomy, called tags.

It doesn't matter whether you want to call them categories, tags, boxes, or anything else. You can think of Ghost tags a lot like Gmail labels. By tagging posts with one or more keyword, you can organise articles into buckets of related content.

Basic tagging

When you write a post, you can assign tags to help differentiate between categories of content. For example, you might tag some posts with News and other posts with Cycling, which would create two distinct categories of content listed on /tag/news/ and /tag/cycling/, respectively.

If you tag a post with both News and Cycling - then it appears in both sections.

Tag archives are like dedicated home-pages for each category of content that you have. They have their own pages, their own RSS feeds, and can support their own cover images and meta data.

The primary tag

Inside the Ghost editor, you can drag and drop tags into a specific order. The first tag in the list is always given the most importance, and some themes will only display the primary tag (the first tag in the list) by default. So you can add the most important tag which you want to show up in your theme, but also add a bunch of related tags which are less important.

News, Cycling, Bart Stevens, Extreme Sports

In this example, News is the primary tag which will be displayed by the theme, but the post will also still receive all the other tags, and show up in their respective archives.

Private tags

Sometimes you may want to assign a post a specific tag, but you don't necessarily want that tag appearing in the theme or creating an archive page. In Ghost, hashtags are private and can be used for special styling.

For example, if you sometimes publish posts with video content - you might want your theme to adapt and get rid of the sidebar for these posts, to give more space for an embedded video to fill the screen. In this case, you could use private tags to tell your theme what to do.

News, Cycling, #video

Here, the theme would assign the post publicly displayed tags of News, and Cycling - but it would also keep a private record of the post being tagged with #video.

In your theme, you could then look for private tags conditionally and give them special formatting:

{{#post}}
    {{#has tag="#video"}}
        ...markup for a nice big video post layout...
    {{else}}
        ...regular markup for a post...
    {{/has}}
{{/post}}

You can find documentation for theme development techniques like this and many more over on Ghost's extensive theme documentation.

site: Get results from certain sites or domains.

- olympics site:nbc.com
- olympics site:.gov
- admissions site:www.lse.ac.uk  ->  admissions information from London School of Economics’ site
- peace site:gov -> pages about peace within the .gov domain. 
windows security –site:microsoft.com -> information on Windows security from all sites except microsoft.com

** You can specify a domain with or without a period, e.g., either as .gov or gov.

related: Find sites that are similar to a web address you already know.

- related:time.com

OR - Find pages that might use one of several words.

- marathon OR race

info: Get information about a web address, including the cached version of the page, similar pages, and pages that link to the site.

- info:google.com
- info:gothotel.com -> information about the national hotel directory GotHotel.com home page.

cache: see what a page looks like the last time Google visited the site.

- cache:washington.edu
- cache:www.eff.org -> will show Google’s cached version of the Electronic Frontier Foundation home page.

define: shows definitions from pages on the web for the term that follows. This advanced search operator is useful for finding definitions of words, phrases, and acronyms. For example,

- define: blog -> will show definitions for “Blog” (weB LOG).

filetype: restrict the results to pages whose names end in suffix.

- web page evaluation checklist filetype:pdf -> will return Adobe Acrobat pdf files that match the terms "web", "page", "evaluation" and "checklist" 

** You can restrict the results to pages whose names end with pdf and doc by using the OR operator, e.g. [  email security filetype:pdf OR filetype:doc ].

link: pages that point to that URL.

- link:www.googleguide.com -> pages that point to Google Guide’s home page
- link:www.google.com -site:google.com  -> links to the Google home page not on Google’s own site.
- link:www.www.ownersdirect.co.uk -site:ownersdirect.co.uk -> links to the UK Owners Direct home page not on its own site.

basic search operators +, –, OR, and " ".

inanchor: restrict the results to pages containing the query terms you specify in the anchor text or links to the page.

- restaurants inanchor:gourmet -> will return pages in which the anchor text on links to the pages contain the word “gourmet” and the page contains the word “restaurants.”

** allinanchor:** restricts results to pages containing all query terms you specify in the anchor text on links to the page.

- allinanchor:best museums sydney -> will return only pages in which the anchor text on links to the pages contain the words “best,” “museums,” and “sydney”

intext: restricts results to documents containing term in the text.

- Hamish Reid intext:pandemonia -> will return documents that mention the word “pandemonia” in the text, and mention the names “Hamish” and “Reid” anywhere in the document (text or not).

** Putting intext: in front of every word in your query is equivalent to putting allintext: at the front of your query, e.g., *intext:handsome intext:poets* is the same as *allintext: handsome poets*

intitle: restricts results to documents containing term in the title.

- flu shot intitle:help -> will return documents that mention the word “help” in their titles, and mention the words “flu” and “shot” anywhere in the document (title or not).  

** Putting intitle: in front of every word in your query is equivalent to putting allintitle: at the front of your query, e.g., *intitle:google intitle:search* is the same as *allintitle: google search*

inurl: restrict the results to documents containing that word in the URL.

- inurl:print site:www.googleguide.com -> searches for pages on Google Guide in which the URL contains the word “print.” It finds pdf files that are in the directory or folder named “print” on the Google Guide website. 
- inurl:healthy eating -> will return documents that mention the words “healthy” in their URL, and mention the word “eating” anywhere in the document.

** Putting inurl: in front of every word in your query is equivalent to putting allinurl: at the front of your query, e.g., *inurl:healthy inurl:eating* is the same as *allinurl: healthy eating*
In URLs, words are often run together. They need not be run together when you’re using inurl:

Symbols:

-
When you use a dash before a word or site, it excludes sites with that info from your results. This is useful for words with multiple meanings, like Jaguar the car brand and jaguar the animal.
jaguar speed -car
pandas -site:wikipedia.org

“
When you put a word or phrase in quotes, the results will only include pages with the same words in the same order as the ones inside the quotes. Only use this if you're looking for an exact word or phrase, otherwise you'll exclude many helpful results by mistake.
“imagine all the people”

*
Add an asterisk as a placeholder for any unknown or wildcard terms.
”a * saved is a * earned”

..
Separate numbers by two periods without spaces to see results that contain numbers in a range.
hard drive $50..$75

References:

• Search operators - Search Help
• Google Search Operators - Google Guide

This post was originally written in november 2016 and recovered from my old blog

This is my final year at university as Software Engineer Student and we need to complete at least 120 hours working in a company as a part of one of the 'subjects'.

The process starts with a list of offering companies and every student enrolled in the course choose several options in order of preference. Then the course staff start to sort by average grade mainly the students. The output of this process is a list of students who should contact the respective companies to start the process.

Well, so my first company choice was CSC, a very large company located in Avilés (also Barcelona, Madrid, etc). I contacted the human resources person who was responsible of the agreement with my university and sent her the english version of my resumé. After a couple of weeks I received a call asking me to go to their offices in Avilés next day. I accepted to be there at mid-morning to realize the internship interview.

The interview

I arrived at their offices a little bit early because I try to follow the rule '5 Minutes early is on time; on time is late; late is unacceptable.' I had to sign a sort of contract to enter the building and keep in view the visitor's accreditation that I was given.

After a few minutes two men, one from Spain and one foreigner, came and introduce themselves. They were part of the IT systems department of the company. All of us went to a meeting room where they started asking me some questions about my CV (they'd printed it and underline the parts they were more interested in). When we finished talking two of the DevOps engineers of the company and one of the development department entered the room and introduced themselves. They asked me kind of the same things that the other team and some questions about their respective job tasks, like if I was familiar with some of the concepts. We also talked about some of the technologies the company use in daily task and a little about how things work there. I explained them why I think university is a little obsolete and the disconnection that exists between the institution and the real-world companies. We also talked about some of my hobbies, what project I was working on for my final course between others.

I wouldn't like to finish without adding I felt really comfortable talking with all of these people, specially because they were actual workers of the company and I had the opportunity to ask them some technical questions related to the task I would be doing. In fact it was more like a relaxed conversation between engineers who like working on what they do. All of this process was realized in Spanish and English to test my conversational skills . I didn't wanted to fool anybody about my english level and I liked the idea to talk a little in the Shakespeare's language even though I'm not the best english speaker xD

UPDATE: Today I received a call from CSC's human resources department telling me I was one of the selected candidates. Hooray!