You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upstream project distinguishes between a "post" a "page" and a... "neither-post-nor-page", let's call it "infrastructure" (home, posts, tags).
As far as I can tell, the only current difference between the three kinds of pages should be the CSS class of the title / description <div>: post-heading for posts, page-heading for pages, site-heading for infrastructure. However, the conceptual distinction is more important than just the CSS class, because the StartBootstrap team may decide to, say, use different masthead colors for posts and pages, and we wouldn't be able to implement that if we can't tell what a "page" is.
#23 adds an IsArchive setting which is similar in purpose (a "neither-post-nor-archive" is a "page") but an IsPage setting would probably make more sense, as it maps easily to the concept of "page" in Jekyll, Wordpress, and probably others.
Add a pages folder under input with an about.md file (that will be overridden by users) to demonstrate the feature. (EDIT: no sense in forcing a page to exist on user sites; a decently-written section in README will do)
Add PageSources and IsPage settings in settings.yml:
Styling for the page-heading class is already implemented and imported, we just never got to see it so far.
Make all other necessary changes wherever IsArchive was used to tell apart pages from infrastructure.
Incompatibilities
An existing blog's "About" page will not see any changes, unless the author adds IsPage: true to front matter.
If an author wants to keep existing pages in input they have to exclude the pages folder from processing; it shouldn't be hard AFAIK, but I'd advise moving pages under pages and using redirects instead.
@daveaglick any thoughts? Should I add this to #23 instead of the IsArchive mess (admittedly of my creation)?
Background and motivation
The upstream project distinguishes between a "post" a "page" and a... "neither-post-nor-page", let's call it "infrastructure" (home, posts, tags).
As far as I can tell, the only current difference between the three kinds of pages should be the CSS class of the title / description
<div>:post-headingfor posts,page-headingfor pages,site-headingfor infrastructure. However, the conceptual distinction is more important than just the CSS class, because the StartBootstrap team may decide to, say, use different masthead colors for posts and pages, and we wouldn't be able to implement that if we can't tell what a "page" is.#23 adds an
IsArchivesetting which is similar in purpose (a "neither-post-nor-archive" is a "page") but anIsPagesetting would probably make more sense, as it maps easily to the concept of "page" in Jekyll, Wordpress, and probably others.Implementation
IsArchivesetting (I could do this directly in Update dependencies, refactor styles and scripts, add some goodies #23 before it gets merged).Add a(EDIT: no sense in forcing a page to exist on user sites; a decently-written section in README will do)pagesfolder underinputwith anabout.mdfile (that will be overridden by users) to demonstrate the feature.PageSourcesandIsPagesettings insettings.yml:_header.cshtmlfrom this:to this:
Styling for the
page-headingclass is already implemented and imported, we just never got to see it so far.IsArchivewas used to tell apart pages from infrastructure.Incompatibilities
An existing blog's "About" page will not see any changes, unless the author adds
IsPage: trueto front matter.If an author wants to keep existing pages in
inputthey have to exclude thepagesfolder from processing; it shouldn't be hard AFAIK, but I'd advise moving pages underpagesand using redirects instead.@daveaglick any thoughts? Should I add this to #23 instead of the
IsArchivemess (admittedly of my creation)?