I have a multi content page in my WordPress site. such as pics, article, video, infographic, etc.
فاران فارمد
which type of schema should I choose?
I choose article schema but what about those kind of pages that is really an article without video,...
Related
I'm migrating a very large website that is currently on an old version of Plone (approx. 2,000 pages) onto WordPress. I am trying to figure out what makes the most sense in terms of pages / posts/ custom post types.
Originally, I imagined moving content over into different custom post types based on the data type, with main pages being Pages, News being Posts, Knowledgebase content being a CPT called "Articles", etc.
As I'm looking at the Plone site, it seems like things are organized into folders almost like my hard drive, which would actually be much more like the Parent->Child structure of WordPress Pages. So now I'm imagining just moving everything over into a ton of Pages with Parent->Child relationships. But something doesn't feel right about having everything be a Page. At least the News should be Posts... I think.
Any guidance on best practices for this type of migration?
I'm new to Drupal and I'm having to work on a site coded by another developer.
We have found and installed the Metatag module in order to give us access to change metadata on content inside the CMS. This is great for most things, however there are some types of content (not sure the exact Drupal terminology here) such as Testimonials and Case Studies. Each individual testimonial and case study has their own area in the CMS to edit the content, and these each have the Metatag module area to give us control over the metadata.
These types of content also have 'index pages' on the front-end (e.g. website.com/testimonials which lists all testimonials). Does anyone have any ideas as to where I can edit the metadata for these pages?
They're not in the CMS as classic pages and there seems to be nowhere to use the Metatag module to edit the metadata.
Either being able to update the metadata in the CMS or just hard-editing the template files would be an acceptable option.
These index pages can be created with various methods. It’s likely that they are created by the Views module or with the Taxonomy core module.
According to its description, the Metatag module seems to be capable of providing metatags for Views pages:
Customize meta tags for custom pages built using Panels and Views using included submodules.
With the Metatag Views Overview module it’s possible to edit the metatags for Views pages on Metatags’s overview page.
If nothing else works, it seems to be possible to provide metatags based on paths:
Customize meta tags for specific paths (or other conditions) using Context and included Metatag:Context submodule.
I have a fairly large enterprise site and I am needing to create a dynamic HTML site map. Similar to the site map at Apple.
With that in mind, I have created a view that lists all node-based pages (i.e.) those pages created and associated with a content type. The problem is that many of the pages on the site are pages created in Views or in Custom Pages and the url is defined there. These aren't dynamic pages, rather they are pages built to be main pages for different sections.
Example: the site has a team content type. This content holds information about an employe. The page at the node level is site.com/team/john-doe. I've set up a view page with the url site.com/team - This lists the name and a photo of the team member.
This is the case for many sections on the site, since these are important pages I need to somehow create a view that lists these pages so I can then take that view content pane and the node-based content pages and drop that into a custom page to build the HTML site map.
Since these custom pages aren't stored in the db I am not sure how I can get views to extract that data and render it as a list.
Any suggestions?
I think what you are looking to achieve is going to be driven more by menus than by views or nodes, custom or otherwise. The menu system contains references to all paths on the site, whether they were created by nodes, views, taxonomies, custom code, etc.
You might find the Menu Views module useful for this:
http://drupal.org/project/menu_views
For a slightly different approach, I would also suggest looking at the Site Map module:
http://drupal.org/project/site_map
I just first want to say, thanks for taking the time to read this!
I have an e-commerce website running the content management system DotNetNuke, which I believe is built on the asp.net platform in a windows server environment. The specific module that powers my e-commerce store dynamically generates pages for each of the store categories, as a user browses through the products available. As you may be aware, modules such as these must be placed on a specific page, and all the dynamic content generated by the module must reside on that "parent page".
The problem is that while the module does allow me to add HTML text for H1's and H2's on these dynamic pages, it does not support adding page meta tags such as "title" and "description". As a result, all of the dynamic pages generated by the module pull their meta tags from the parent page, making it difficult for Google to understand what I'm trying to show the user. This also causes google to show all these generated pages as having "duplicate title tags" in my analytics.
The temporary fix:
I have removed the title tags from all of these "parent pages", in hopes that google will decide to generate it's snippits from the H1 and H2 tags residing on the dynamic pages. Was this wise?
Now for the question:
Is there any kind of solution available which would allow me to manually assign meta tags to a page I specify in my hosting environment? As I stated earlier, I am able to add body HTML code to pages. Is there any way to force a page title tag from code placed in the body? Is there a better way to do this? You can view my problem in action at www.yandasmusic.com
Thanks for your time and patience!
Alex
The temporary fix: I have removed the title tags from all of these "parent pages", in hopes that google will decide to generate it's snippits from the H1 and H2 tags residing on the dynamic pages. Was this wise?
Blockquote
No, not particularly wise. The page title is important.
The first route you should take is speaking to the module developer. They should know about replacing page meta information on a per-product basis.
You can get (limited) results by varying the page title/description using javascript when the page loads. Just keep the js simple and use the DOM information already on the page (ie, read the product name).
I posted a blog about this recently : http://www.ifinity.com.au/2012/10/04/Changing_a_Page_Title_with_Javascript_to_update_a_Google_SERP_Entry
The javascript fix will probably work if you set it up correct. But you really need to convince the module developer to change the way the module works, as bdukes has posted.
Don't bother with the Meta Tags - none of the search engines really read/use them because they are so easily spoofed. Just concentrate on the title and description of the page.
Ideally, your store module should be setting the page title and other meta information. In DotNetNuke, you can access the Title, MetaDescription, and MetaKeywords of the page by casting Page the DotNetNuke.Framework.CDefault type. If the store module doesn't provide this, you should ask the developer to add the functionality.
Intro
I am in the process of trying to convert my first HTML/CSS design into a theme for Drupal. I have used ModX for quite a few designs and appreciate the ability to create different page templates and custom variables to be assigned to those templates. However I seem to be having some issues making the transition.
The site I am working on theming in Drupal is for a real estate agent. Each page/section will have a different set of content associated with it and will need to display only that content. For example, there will be a page for current listings, each of which will be formatted by a custom content type. However, when I call the content on the home page (or on other pages) I do not want to see this listing data.
Layout
The layout of the site and the regions associated with each page/section is as follows:
Home
Spotlight
Featured 1
Featured 2
About
Spotlight
Bios - Profiles of each agent (each will be a node with name, contact info, pic, etc) listed on the page; multiple nodes listed
Sidebar
Listings
Spotlight
Listings - Profiles of properties (each will be a node with locations, basic info, pic, etc) listed on the page; multiple nodes listed
Sidebar
Services
Spotlight
Content - general paragraph text area
Sidebar
News/Blog
News/Blog Items - List of stories with summaries and links to full article
Sidebar
Each page/section will use the same header and footer.
Issue
I have done some reading on Drupal, custom content types (and CCK), Views, and Pathauto. However I have not been able to get a clear picture of how to put it all together to accomplish what I am attempting. What I really would like to know is which modules to use, how best to use them, which elements I need to use where, and what template files I should be using to theme the elements I need to use. Any help or reference to useful resources would be much appreciated.
This is a rather general question, and your description is a kind of vague on important distinctions like page vs. site section vs. page region. That said, some general advice: start by installing the admin module. Then get all your content generally in the right places with someone else's theme, e.g. Garland, before you start doing any of your own theming. You should be able to get pretty far without touching code. Use CCK to define your content structure. You should already have a type for page and it sounds like you'll want to add a type for feature, bio, listing, and blog post. Depending on the details, you may need to add some additional field modules, e.g. if you have images, you'll probably want the imagefield module.
Once you have the content types defined, configure pathauto, and start adding content.
Once you have some content, you'll want to create some lists of it with views. You may want to start with the simpleviews module, as the views UI can be overwhelming. Save your views as block display, and then use the blocks admin to put the in the right page region, and configure them to show up only on the right pages.
At that point, you'll want to start controlling how the individual items (nodes) look in different contexts. That's when you start theming. For that, I'd install the devel module, look at what other themes do, and call dsm() on any variables you don't understand to see what they look like.
You can generally get quick help with specific questions on the Drupal IRC channels.
The easiest way to do what you want to do may be to put your custom content in blocks and set the access settings for the blocks to be only on certain pages. So, for instance if you have content that you want to appear at /spotlight or /node/22 or such, you would just create a custom block (Site Building -> Blocks) and then in the settings, set the block to only show for that node.