Project Report: On Personal Resume Website
Project Report: On Personal Resume Website
On
Personal Resume website
Practice School: 2
Submitted in partial fulfilment of the requirements
For the degree of
By:
NAME: Ankit Rao (2013Btechcse005)
Department of . Engineering
Institute of Engineering and Technology (IET)
JK Lakshmipat University Jaipur
May 2017
CERTIFICATE
This is to certify that the Practice School-2 project work entitled Online
Resume Website submitted by Ankit Rao (2103Btechcse005) towards the
partial fulfillment of the requirements for the degree of Bachelor of
Technology in Engineering of JK Lakshmipat University Jaipur is the
record of work carried out by them under my supervision and guidance. In
my opinion, the submitted work has reached a level required for being
accepted for Practice School-2 examination.
--------------------------------------
-------------------------------------------
Dr. Amit Mishra Prof . Sonal Jain
Department of Computer Science Department of Computer Science
Engineering Engineering
Institute of Engineering & Technology Institute of Engineering & Technology
(IET) (IET)
JK Lakshmipat University Jaipur JK Lakshmipat University Jaipur
Date of Submission
Director
Sincerely yours,
Project Title...
Certificate...
Acknowledgment .
Abstract ..
CHAPTER 1
Introduction.
Literature Review
Objectives
CHAPTER 2
Company Profile.
CHAPTER 3
PROJECT DESIGN..
Process Module
Functional Decomposition
Data flow diagram.
USER INTERFACE DESIGN
CAHAPTER 4
Implementation technology
Drupal overview.
The Drupal flow.
General concept......................................................................
CHAPTER 5
Design of website- Personal portfolio
HomeAbout meShop Code.Contact usBlog
CHAPTER 6
Conclusion ..
Future Scope of Drupal
Reference.
Chapter:-1
Introduction
Personal Websites are the best way to let the people know
what you are and what are your achievements in life. Some
choose the funniest quotes for themselves and others show
their personality with full earnestness.
Company Profile
PROJECT DESIGN
PROCESS MODEL
1. Decomposition diagram
A decomposition diagram shows a top-down functional
decomposition of a system and exposes the system's
structure. The objective of the Functional Decomposition
is to break down a system step by step, beginning with
the main function of a system and continuing with the
interim levels down to the level of elementary functions.
The diagram is the starting point for more detailed
process diagrams, such as data flow diagrams (DFD).
Figure 2 shows the Functional Decomposition Diagram
for this project.
Figure 2 Functional Decomposition Diagram
2. Data Flow Diagram (DFD)
Implementation Technologies
1. Drupal Overview
Pick one of the included themes, and just start adding content.
Do you want to have visitors log in? Switch authentication on
or off. Want to switch on some of the included tools? Turn on
forums; enable commenting on node types; turn on the book
module for wiki-like collaboration; create forums and polls; use
taxonomy to give site content structured, hierarchical
categorization or free-form tagging.
General concepts
1 . Node (Content)
A node is the generic term for a piece of content on your web
site. Depending on the type of node, different fields will be
attached, and this is known as a content type. For example, a
basic Page content type has attached fields such as title and
body fields. Other examples of content type are: Book pages
for use in Books, Discussion topics in forums, Blog pages in
blogs, and News articles.
2. Entity types
An entity type is a useful abstraction to group together
fields. Entity types are used to store and display data, which
can be nodes (content), comments, taxonomy terms, user
profiles, or something custom developed.
Content Types are the elements using which the site editors
can input (add) original content on a Drupal site, and are the
building blocks for structured authoring and content. Content
types often work in conjunction with Views, which is one way
you can serve up content to your end users; you can control
the content types that appear and the order in which they
appear.
4. Taxonomy
5. User
6. Module
A module is software (code) that extends Drupal functionality.
Modules fall into one of three categories:
Core modules are those included with the main download
of Drupal. These can be turned on or off without
downloading additional components. Examples include
Blog, Book, Poll, or Taxonomy.
Contributed modules are downloaded from the Modules
download section of drupal.org, and installed within your
Drupal installation. Examples include Panels, Views or
Metatag.
Custom modules are modules you write yourself. This
requires a thorough understanding of Drupal, PHP
programming, and Drupal's API.
8. Menus
You can also create your own custom menus, and display them
by enabling their blocks.
You can also add custom menu items to a menu, from the Add
menu item tab of the Menu administration screen. To create a
menu item, you will need to provide the path to the content.
9. Theme
The Theme layer is separate from the data layer, the
functionality extension layer (module) and Core. Theme
controls the appearance (look and feel) of your site, or how
your site is displayed, including the graphic look, layout,
and colors. A theme consists of one or more PHP template
files that define the HTML output of your site's pages, along
with one or more CSS files that define the layout, fonts,
colors, and other styles.
10. Views
Although not all sites have Views, most sites include the Views
module because of the excellent tools it provides. Views allows
people to choose a list of nodes or other entities and present
them as pages, blocks, RSS feeds, or other formats. The main
use case for views is to create dynamically updating lists of
content (for example, a listing of latest news), based on
properties of that content (in the case of the news listing, that
the content type is News and sorted by publication date).
For more technical users, views can be understood as a user
interface to compose SQL-queries, pulling information
(Content, Users, etc.) from the database and showing it on
screen in the desired format.
a.Fields
Fields, or the individual pieces of data being displayed.
Adding the fields Node: Title, Node: Type, and Node: Post-
date to a node view, for example, includes the title, content
type and creation date in the displayed results
b.Relationships
Relationships, or information about how data elements
relate to one another. If relationship data is available, like
that provided by a CCK nodereference field, items from a
related node may be included in the view
c. Arguments
Arguments, or additional parameters that dynamically refine
the view results, passed as part of the path. Adding an
argument of Node: Type to a node view with a path of
"content", for example, dynamically filters the displayed
items by content type. In this example (shown with Clean
URLs enabled), accessing the view through the path
"http://www.example.com/content/page" displays all posts of
the type "page"
d.Sort criteria
Sort criteria, which determine the order of items displayed
in the view results. Adding the sort criteria Node: Post date
(in descending order) to a node view, for example, sorts the
displayed posts in descending order by creation date
e.Filters
Filters, which limit items displayed in the results. Adding
the filter Node: Published (and setting it equal to
"Published") to a node view, for example, prevents
unpublished items from being displayed.
f. Displays
Displays, which control where the output will be seen. Every
view has a default display, which doesn't actually display the
view anywhere but is used to hold the default settings for
the view. This default display is also used when the view is
called programmatically without specifying another display.
Much more useful to users are the page display, which gives
a view a path and allows it to be the primary content of a
page, or the block display which allows it to appear as
secondary content on other pages.
g.Header
Header, which allow you to add by default one or more text
area above the views output.
h. Footer
Footer, which allow you to add by default one or more text
area beneath the views output.
i. Empty Text
The Empty Text content will be displayed, when you choose
in the Arguments Section "Action to take if argument is not
present" the option "Display empty text"
11. Database
When you visit a URL within your Drupal site, the part of the
URL after your base site address is known as the path.
When you visit a path in your Drupal site, Drupal figures out
what information should be sent to your browser by checking
its list of menu items and routes. Generally, Drupal allows each
module to define paths that the module will be responsible for,
and when you choose to visit a particular path Drupal asks the
module what should be displayed on the page.
13. Bootstrap
The bootstrap is the CPU (central processing unit) of Drupal.
In other interactive software environments this is sometimes
called the event loop. Drupal's core is a bit like that. It sits
around waiting for a path request, and then starts processing
that request.
Home
The user would first see the Home page. It internally
contains links to some particular projects of mine and
also enlightens the area of work and technologies I know
and work with.
Code Snippets
These are exclusively made for arcoders site and will offer custom development
options with easy to understand instructions.
Blog
A blog is a discussion or informational websites published on
the WWW consisting of discrete, often informal diary-style text
entries ("posts").
It will contains posts for users and clients who can see the
timeline of the person , which eventually gives a idea of
activeness of the person.
Contact Us
Conclusion
A personal web page can be used for self promotion for a
person's small business or entrepreneurial venture, to promote
an amateur rock band they play in, to promote community
activities or charitable causes they support, to provide quick
access to information about the user, or just as something
"cool" to do. A personal web page gives the owner generally
more control on presence in search results and how he/she
wishes to be viewed online. It also allows more freedom in
types and quantity of content than a social network profile
offers, and can link various social media profiles with each
other. It can be used to correct the record on something, or
clear up potential confusion between you and someone with
the same name. Early personal web pages were often called
"home pages" and were intended to be set as a default page in
a web browser's preferences, usually by their owner. These
pages would often contain links, to-do lists, and other
information their author found useful. In the days when search
engines were in their infancy, these pages (and the links they
contained) could be an important resource in navigating the
web.[citation needed]
www.drupal-wiki.com