Home Visit Form Template: Fill & Download for Free

There a couple of design examples that have always inspired me in my work as a freelance designer.Printing AdvertisingThe Print Ad titled “Welcome Home” was done by an Irish advertising agency for Guinness in Ireland. If you look closely, you’ll notice a beer.It is cool,isn’t it?2. Web DesignWhen I seek for inspiration to design a minimalist, yet a very creative website, I always visit Ucraft’s website. They have more than 50 stunning templates for those who want to build a website without coding. But as for me, I mostly use them to get new ideas. Check out this one from one of their templates:

I think to answer this question we should start with the abstraction that we often refer to as a design pattern, and in this particular case the design pattern “MVC”. This stands for Model, View, and Controller, and in many contexts the front-end is the “View” (what the user sees), the back-end is the “Controller” (what does the work), and the database or other permanent data store is the “Model” (what stores the information for later). I like to build middle-out meaning that I first consider what my application needs to DO (like, log in users, or update account information, or run queries, etc.), and then build out the business logic that it will use to accomplish this. In doing this, it helps me define what I need to store (the model), and how the front-end will interact with the back-end. Now, going into great detail on how the front-end and back-end are integrated.The View takes many forms, but at its heart, on the web, it is HTML, JavaScript, and CSS. A given view (like your homepage, or accounts page), or a partial view (perhaps your header, or footer) may be integrated to your framework (as with ERB templates in Ruby on Rails, or Django templates in Django), or it may be entirely separate (and potentially written with a front-end JavaScript framework, like Angular, or Backbone, or Ember).This means that in the former example, where a view is integrated with the framework, as a request is made to the back-end (I’ll come back to this later), what is returned is HTML that has been pre-rendered by the back-end engine, that may or may not use values from the controller, and can even do logic using the templating language (like ERB templating for Ruby on Rails or Django templating in Django, as above). In the latter example, everything is HTML, CSS, and JavaScript (potentially with a JavaScript framework), and this changes the way that the back-end returns data to the front-end.Now, for the important part: how does the front-end really communicate with the back-end? The front-end always makes a call, meaning a GET or a POST request generally. A call can be made actively, by a user clicking on a link, in response to some event (in JavaScript), or passively (on a timer, also in JavaScript).A GET request is one that has all of the values that it will pass to the back-end in the URL itself (like mywebsite.com/someservice?somekey=somevalue&anotherkey=anothervalue). In this example, when the call is made it makes a get request to the “someservice” endpoint of your back-end and has passed the parameters “somekey” and “anotherkey” with values “somevalue” and “anothervalue”.A POST request is one that has all of the values it will pass to the back-end encoded in the request body. In this case you would invoke mywebsite.com/someservice, but the values would encoded in the request body itself. This happens whenever you fill out a form, in which case the request body is multi-part form-encoded content. This too can be done actively (e.g., a user submits a form), passively (e.g., the form is submitted in response to all fields being filled out), or on a timer (e.g., the front-end checks the back-end for some value in the form and validates it using the back-end every 5 seconds).And this is the meat of the answer: a call is made from the front-end to the back-end through either a user interaction with the page, listening to an event in JavaScript, or using JavaScript as a timed event. In all three cases we have a choice: will the request by synchronous, or asynchronous? Synchronous typically means that the user makes a request and waits for the response. Asynchronous typically means that the request is made in the background, and the page (or elements of the page) are updated when the response from the request is received. Asynchronous requests are all done through XML HTTP Requests (XHR), which you can do using plain JavaScript or any JavaScript framework (even jQuery makes this very easy).The next big question is, how does the back-end, once it receives a call from the front-end, know what to do with this information? What happens is this: a back-end receives a call from the front-end (as above, we’ll use the GET request as the example), and it takes apart the request, classifying the following:It’s a GET requestThe domain is mywebsite.comThe port is 80, for http, or 443, for https (by default)The endpoint is “someservice”It then takes that information to route the request appropriately, passing the request body as well. What do I mean by route? Let’s assume the back-end is set up in a typical way, with a web server (like Apache or NginX), and an application server (like Passenger or uWSGI, which would mount and provide the gateway to a Ruby on Rails or Django application respectively). The web server takes this information and, assuming it knows the host and the port, and the resource is allowed, will pass on the information to the application through the gateway.When the application receives the call it too needs to route the request appropriately, which is where “routes.rb” and “http://urls.py” come into place (for Ruby on Rails and Django respectively). These files say: if a request matches a given pattern (endpoint, request method, and potentially arguments, typically), then the router should route the request to a given controller and action (often a method within a given controller).When the controller receives the request, finally, it comes complete with the request body, so all of your passed keys and values are present. The controller action (your method in your controller) then does the “business logic,” potentially communicating with a database (to store or read information), or doing some calculation, etc. What’s important about the different ways of making a request (synchronously or asynchronously) is in two parts:What does the back-end return? XML, JSON, or HTML typically, and a single method may return any one of the three depending on how the request was made. This is what “responds_to” does in Ruby on Rails, when dealing with an asynchronous request. Render, and redirect, are the statements we use in Ruby on Rails when we wish to render a view or redirect to another action. This is also something we’ve typically decided through architecture, in deciding whether or not our front-end is integrated as a template in our back-end, or not. When a front-end is integrated as a template, we may be returning a view (rendering a view), in which case we pass on values to that view, the back-end engine renders it all as HTML, and it is then returned to the consumer. When we’re receiving an asynchronous request, our controller must return XML, or JSON, or HTML, depending on how the front-end will receive and interpret the results. A good example of this would be in making any long-running request (like a large database query): the consumer doesn’t want to wait to get a request, it’s likely that their browser would time out before the response is returned. As a result, the request would be made asynchronously, and either the user could remain on the page and wait for an update, in which the back-end returns a block of HTML, or a JSON object representing the query results, or a timer could be set up on the front-end to listen for such an event, probing the back-end periodically.This brings us to the second part for making a request: what does the front-end do with the returned data? When making a synchronous request, it renders that data (necessarily), meaning it shows a whole page typically, like when you log into a service and are “forwarded” to your account page. When making an asynchronous request, the front-end has to decide what to do with the results. It may take those results and render them to the page in a particular spot (like the query results above); it can do anything as a result of or using the response from the back-end.Let’s add in a quick example, step-by-step, for the scenario where user visits your homepage:The user types in your website to their browser URL bar and hits enter, making a GET request to mywebsite.comThe back-end receives this request, and knowing the domain, port, method, and endpoint (“/”), it passes it to the applicationThe application receives this request, and knowing the endpoint and method, it passes it to the correct controller action (we’ll say Application controller and home method)The application controller home method simply renders the HTML associated to the home page as a view, passing back to the consumer rendered HTMLThe browser interprets the HTML, and the user sees the homepageLet’s do a second scenario, one where we make a query using a form and then the results of that query should be rendered to a text box on the page some time later:The user enters information into a form related to their query (maybe date ranges, or IDs, etc.), and hits the “submit” buttonJavaScript (that you’ve written) captures the event (prevents the default from occurring), wraps up the request parameters, and makes a POST request asynchronously to your endpoint (we’ll say mywebsite.com/query)The back-end receives the request, and knowing the domain, port, method, and endpoint (“/query”), it passes it to the applicationThe application receives this request, and knowing the endpoint and method, it passes it to the correct controller action (we’ll say Application controller and query method)The application controller query method needs to do some business logic to start the query and provides a query ID, which it then returns to the front-end as JSON (e.g., {‘query_id’: 1234})The front-end receives this response through the asynchronous listener you wrote, and sets up a timer to listen for query completionThe front-end uses JavaScript (that you’ve written) to make a POST request to the back-end every 5 seconds, (we’ll say, mywebsite.com/queryresults), passing the “query_id” we received in the previous step as the request bodyOnce again, the back-end routes the request appropriately, this time to a controller action that asks if the query is done yet (I won’t go into detail on the how of this today)If the query is done, the back-end returns the results as JSON, e.g., {'query_complete': true, ‘query_results’: ‘somequeryresults’, 'success': true, 'msg': ''}If the query is not done, the back-end returns the same structured JSON but with different values (note that you don’t need to maintain the structure, but again I won’t go into the why of this now), e.g. {'query_complete': false, ‘query_results’: ‘’, 'success': false, 'msg': ''}It could also return an error message using the structure above, where query_complete is true, but success if false, and a message accompanies it in the msg parameter.Once again, the front-end must decide what to do with the results:It does nothing with the results if the query isn’t done yetIt renders the results in the appropriate place if the query is completed successfullyIt tells the user there’s an error when the query has failed, for whatever reasonHope this helps!

In addition to Balaji Viswanathan (பாலாஜி விஸ்வநாதன்)'s amazingly profound answer, I would like to insert my own take.Why are the gods worshipped? Why do people go to Temples? Why should you care about philosophical fiction?Hinduism enjoys a long history. Hinduism shaped India's culture and India's changing culture for years shaped Hinduism. The belief system works on the basis that there are no specified value rigid set of rules at any point of time. A sea of ideas, practices and gods (Avatars) are created spontaneously as the patina of time takes it's course. There is an artistic freedom for poets, writers and sculptors to give form to gods in ways they like. For example, a sculptor could take an existing avatar of god and shape it to the way he likes. He can modify the image of a God, say, Ganesha from a template produced by his ancestors. Hinduism is polytheistic religion and the most remarkable thing is that each avatar of a single god is expressed in several forms, names and stories. Artists take a template and express the avatar which represents various natural phenomena and moral ideals in various ways they like. Often with artistic subtleties in a statue or through literatures filled with moral values.The most amazing thing about Hinduism which most people take it for granted is how the rituals are practiced for over centuries in a seemingly same fashion. Sure, the scripture, the Slokas, the deity being praised varies across the country and communities, but the template is the same.The template's goal is to make people who visit temple to offer prayers to be in the moment. Make them aware and conscious. How? By awakening all the senses of a human being.Sound - Hindu temples are known for Bhajans and music. Percussion instruments and wind instruments are employed generously to make a person listening to fly high in the skies. The sounds are designed to heighten your hearing sense. Women devotees provide the songs, it's soul with their sweet honey dripping vocals.Smell - This is a no brainer. Hindu temples are filled with aromas. Even people performing Poojas at home light incense sticks (agharbattis) to provide a sweet aroma that fills the room. It's enchanting. The smell is soothing. It heightens your sense of smell and it's pleasurable. Many Indian incenses have a unique scent that is not found in any other part of the globe.Visuals - Hinduism is known for beautiful patterns and colors. Hindu temples are filled with beautiful sculptures and art works in every nook and corner you can see. Every inch is filled with a statue or an art work. Patterns that are visually attractive. It takes your eyes on a beautiful trippy ride.Touch - After Dharshan, people try to touch fire, a natural element using their closed hands from a safe distance and take in another natural element, water or tender coconut water mixed with Tulsi, a herb. Then they apply paste made of ash on their heads that represents earth and death, another powder that is either made from turmeric or saffron and another paste made from sandal wood tree.Taste: Every Hindu temple provide "Prasad". Food items are offered for free. People consider them to be holy and eat them with diligence.Mind: Hindus consider mind to be a sense organ. After prayer, people meditate or sit in some place in the temple together with their family to calm their mind. This is a common practice.When people leave the Temple, they have a sense of satisfaction and purpose in their life. They are unconsciously fed with a sense of hope to walk safely through the maze of human life by the guidance of virtue.This is the observable reality. It's wonderful to see how a cultural practice is carried out through centuries. Hinduism's philosophy is deep. It's literature works are excellent. There is a place for artistic freedom. And morals are intact. That's how I see Hinduism.And I think most of the people in Indian countrysides would express the same. It's so fascinating. It's amazing to witness and experience an entire diverse culture which includes great literary works, various art forms that grew just because of an intuitive understanding and experiential wisdom. It's just another side of the coin. There is no place for logic and reasoning. Only beautiful experiences.