###Front End Frameworks
Bad analogy would be imagine some provides the frame of a house and you finish it off by adding the interior/exterior walls, roof etc.
###Front End Frameworks
Bad analogy would be imagine some provides the frame of a house and you finish it off by adding the interior/exterior walls, roof etc.
RSS (is this still a viable option?)
Yes.
You would have to learn some php scripting. What you are wanting is the ability to add items to an RSS feed. Let's say you create an RSS feed and put it in the web_root as feed.php. Both pages pull the RSS feed and display it. How you pull it is up to you. There's javascript/jquery for this available on the web. Figure this approach will be best since it doesn't require converting pages to php (or changing server configuration to parse html as php, which is an option).
Here's a javascript class for reading RSS feeds. This should be part one, grab an existing feed and use a test page to display the feed. It's important to understand how to limit the # of items shown.
From this reddit post :
http://www.reddit.com/r/forhire/comments/2zam6d/meta_hiringpotential_whats_involved_with_a/
This is tagged as [Meta] as I'm not hiring just yet, but I'm looking into my options and may be hiring in the near future.
You can check http://www.php-login.net/ it has several levels of a login script available. For best practices, check the security guide.
https://www.owasp.org/index.php/Main_Page
Specific security guide for PHP : https://www.owasp.org/index.php/PHP_Security_Cheat_Sheet
And another security guide : http://phpsec.org/projects/guide/
For general best practices for PHP, PHP The Right Way . https://leanpub.com/phptherightway/
MDN : https://developer.mozilla.org/en-US/docs/Web/HTML/Element
MDN CSS : https://developer.mozilla.org/en-US/docs/Web/CSS/Reference
caniuse : http://caniuse.com/
codrops css : http://tympanus.net/codrops/css_reference/
overapi javascript reference : http://overapi.com/javascript/
Let's see :
Search form is the focus of the page. It's too complex and lacks clear instructions. The top row should be discarded or minimized to the #1 search query type to reduce confusion.
would have replaced the above section with instructions or a lead to get people to search. 'Pick Your Destination' or something similar
Would work to center the form and move the delta small advert to the left, making the form center of attention.
overall for a travel based site, it's pretty plain looking. But isn't about design I would gather.
<div class="container"> | |
<div class="col-md-6"> | |
<div class="panel panel-default" id="one"> | |
<div class="panel-heading">Title | |
<button type="button" id="add" class="pull-right hide">+</button> | |
</div> | |
<div class="panel-body">Content here..</div> | |
</div> | |
</div> | |
<div class="panel_row col-md-6"> |
It's the same concept as style guides but with CMS theme development you have the luxury of building and reusing a predefined content package so it can be visually inspected. It's just a method I've used for situations where the content is an unknown.
I think we're probably in agreement there's a base line of design/style/code that should be provided for default HTML elements. If it's something a text editor can insert into a document, there should be some level of styling provided. Just because the client says they won't need unordered lists, we don't believe them because it is such a common thing it would be silly to skip.
Now specific UI elements is where we listen to the client or the requirements. Like the elements presented on this page :
http://rizzo.lonelyplanet.com/styleguide/ui-components/cards