Is there a place where people can find "Users Manuals" for some of the core stuff in Pl5? Like shortcodes and how to use and setup some of the Extensions?
The Signup Extension is driving me nuts - can't see where to actually add it to a page, widget, section after installing/activating. Have run into this frustration with other things.
Searched and found this on Github: https://github.com/pagelines/Docs
These Docs Are No Longer Updated
These docs were originally created for DMS 1. We are now at DMS 2 and these docs are no longer active. To get the most up-to-date documentation, please click the links below.
When are the docs pages going to refilled?
..and will the content they have replaced be made available somewhere else?
A bit too far into a DMS2 project to drop it for Platform 5, but it certainly gives the impression it will be a lot more of a peppy, positive experience, so I'll shoot for that as the second rollout of the site, but until then- the inbuilt links to content (Docs, sections, answers..) in DMS 2 are either 404 or empty. Perhaps a revision that redirects those pages to the old content so it's available where it's needed and not on the current site / product offering where it would could cause confusion and such.
I will say, I got into Pagelines because my interpretation of it was that it combines the easy (better) parts of NationBuilder, Webly, et al- and allows one to still have ultimate control, where with the aforementioned platforms, you are basically .. SOL.
-BUT- it took a while for exactly what was going on, what all the pieces were, and what exactly the product really was, to click with me.
I might add that, it was looking at the Platform 5 preview that it all started to make sense. Because Platform 5 is not a huge clusterfudge of a pile of stuff that is all essentially the same thing.
I wanted a theme, (WHP), then I saw the options, "oh, well if I get this, then I have 'more'" as the lineup gave me the impression that I can get "the theme" -or- I can get the theme and the framework, along with the PSDs and similarly related assets.
Platform 5 doesn't do any of that at all, but rather say "Here I am, this is going to be great!, Let's go!"
As you're aware, I am in the process of writing the documentation for the Platform plugin as well as creating introduction videos for all sections.
Although this is a rough draft of the video, it should give you some idea as to what to expect from them. Please check it out on the link below, please do not share the video, as it is a draft and contains some mistakes.
Another idea for the section docs after they're finished was to add the following:
A reference to the shortcode that generates the section, so you can quickly see the shortcode that generates that section. Like so:
[pl_section section="boxes" id="Unique ID"] Another idea was to include some of the sections classes, as a reference:
.pl-sn-boxes .box-title .boxes-pad .boxes-media .boxes-icon Let me know what you think of these ideas and the video please.
the logo sizing option is
not expalined not logical
Currently, the main heading for an element is automatically wrapped with a <h1> tag.
That's okay if the content its wrapping around is, in fact, meant to be the main heading for the page.
But I suspect there may be people who will already have a heading on the page wrapped with <h1> tags, so that's going to create a bit of a semantic issue (theoretically, from what I understand about HTML5 spec, it is possible to have more than one <h1> tag on a page, but you really need to know what you're doing).
So I think that designers should have the option to select that tag for each text part that makes up an element.
Additionally, if the main heading of an element is being used as the <h1> heading for a page, if designers are able to select the tag, then it should automatically wrap the <h1> tag with <header> tags (and maybe even the appropriate classes - e.g., entry-heading, entry-title).
When you look at the other text parts that make up an element, you see that the subheading is automatically wrapped in a <h3> tag.
If the main heading tag is a <h1> tag (as it is at present) then, logically/semantically, the subheading should be wrapped in <h2> tags or <p> tags (perhaps it could be set conditionally - depending on designer selection of main heading).
Further, the subheading <h3> tag actually wraps around <p> tags that contain the subheading content.
That makes no sense whatsoever.
Finally when you specify a tag in the paragraph textbox of an element, it doesn't actually that tag as HTML. Instead, it adds a class - using the specified tag (e.g., class="h2") to a span.
That also does not make sense.