I understand using microdata to highlight a thing, person, movie etc.
I think you should also highlight key pages, such as the 'About' page and 'Contact' page.
I've heard you should markup navigation areas too. I suppose this is a good idea as it can tell Google the areas which aren't important.
How would I do this? Is it just a case of wrapping a div around each nav bar etc?
Is it important? Does anybody else use it?
As navigation items are links, one way is to use itemprop "url" (dependant on the itemscope). For creativework you may also use "isBasedOnUrl."
You may also try nesting.
Related
I want to use the News system extension from Georg Ringer like this:
Multiple News Details & Lists All on one page
the Detail view on top of the "cards" of the List view should show the Detail of the item clicked on
The behavior seems like to allow multiple list but only 1 detail view
Detail View of "Services"
List View of "Services"
------ other stuff
Detail View of "Projects"
List View of "Projects"
------ other stuff
Detail View of "Sectors"
List View of "Sectors"
Has anyone experience with this?
I would change the list view to handle the first news entry with much more information. In Fluid you have access to all needed fields for displaying it like in detail view.
Then, you only need three list views on the page with your special template. No need for a detail view.
In general it's possible what you desire but you've to adjust the detail-view in the plugins statically to a special detail or you always will only be able to display one detail at a moment, no matter which category because news is like probably all TYPO3-extensions not programmed with the ability to transfer parameters for several plugins on a page at once.
Many years ago when extensions still have been programmed fundamentally different I had some similar desires related to other extensions and programmed something which transferred the parameters always related to each plugin on a page, so it was possible to regulate several plugins of the same type on a page separated. Today it will be harder probably to implement something like that.
What you can do is to look in the manual about the AJAX-posibilities of news. There might be still an option to fetch the detail for each of the categories separated, perhaps even on page-load already, but it will be a nifty setup which takes probably some time.
I'm building an app with Phonegap/Cordova and Web standards, such as HTML and CSS. However, somewhere on the part of creating this, my skills aren't sufficient.
Ok, let's get this straight: I'm trying to create a navigation bar at the top of the screen. Very basic, even without buttons, just plain text with links.
Check-out this screenshot. As you might see or not.. The middle one isn't exactly placed in the middle. I've tried with div styles, span classes and tables seem the best option.. Yet still insufficient.
What's the best option to create such header?
p.s. No, of course there won't be a border in the table :D - Just for viewing. ^^
I did an example of something like this for a talk... here's a basic version with just a header and some scrollable content: http://jsbin.com/UWeQeli/1/edit
Hope it helps.
Can any one explain what is the specific usage of UIPagecontrol in iPhone please.
I am using it for pagination in scroll view. Is there any other specific purpose for it???
Reading documentation for UIPageControl help you to understand uses of pagination.
Pagination, which automatically separates the content in your form into smaller groups of rendered content. When you use pagination, these groups of content are automatically formatted to fit the target device. The form also renders user interface (UI) elements that you can use to browse to other pages.
Here is the more simple explanation
http://www.smashingmagazine.com/2007/11/16/pagination-gallery-examples-and-good-practices/
You can know how many pages are there and also tapping on it ll navigate to next page.
I wonder which will be the best route for build edit forms on the iPhone, using a TableView or using a scrollview.
I need:
Support up to 15 fields (similar to contact app)
The same behavior of safari forms, where is possible go back/forward among fields, and the form center the selected field and stay there when the user end the editing
Simple layout (one field after other)
I'm looking for the most-user friendly experience. Which route has been proved to be the better?
Exist good examples of great edit forms on iPhone apps?
I would vote for a tableview organized by sections. If nothing else, it is a more common layout and most users will be familiar with it.
In either case, you will have to handle the transition from field to field with custom code.
From a design and usability perspective is it best that an edit page mimics the layout of the view page?
Our view page is very dense. The data is tightly packed together, but when editing there are going to be extra controls next to each entry field. If we leave the layout the same it will be overly crowded. Will this cause problems with usability if the fields are rearranged?
It definitely impairs usability. Two hazards of re-arranging fields are:
Confusing users about which field they are editing
Making it difficult for users to find the field they want to edit.
These problems are exacerbated on high-density pages.
There are some times when this is ok. The best example I can think of is where the editor and viewer are different users. Another (more ambiguous) case is a situation where the edit screen needs to be highly optimized for fast throughput.
If possible, you might consider splitting the screen up, or making collapsable regions to give the user (and the screen) a little room to breathe.
In general you want to keep the edit page as simillar as possible to the view page. In general. There are cases where this just doesn't make sense especially if you have to input a lot of extra data that is not shown in the view, which it sounds like is your case.
What I would try and do is make sure you continue to group and order the fields in the same manner as if you were viewing so while they might be in slightly different places at least they would be logically grouped the same.
It depends upon your workflow.
If the user has to go back and forth between edit and view, it will be very confusing to the person, as fields may jump around, they might lose which field they are on, etc.
If your view page is very dense, you might try breaking it up into sections, each with its own edit function. You could have it shoot to its own edit page or be all 'web 2.0' and throw up a lightbox with the section edit form over the view page.
The more that things are similar, typically, the easier it is for a user to use. I don't know what your particular layout looks like but from a general point of view, a crowded view is often hard to look at and cluttering it up with additional controls would make it worse.
As much as I'm not a spreadsheet guy, editing in Excel or similar products is easy because it doesn't clog up the view with lots of controls. The edit panel is the view panel. For my own products, when things are consistent, the users are generally less confused.
I have had a similar problem. What I did was have a View page that lets you see everything, but you need to drill into individual edit pages for logical sections. Within the logical sections the fields are always in the same order (and with the same labels) as on the view page. It's things like this which make your application just feel a bit nicer.
Don't throw everything onto a massive edit page just because they all relate to the same thing in your database model. Break them out into sets that make sense each with 3-7 fields on them.
If they really need to edit everything (like when creating a new thing) then I would go for a wizard approach which steps through through, presents a view-only summary and then lets them save.