-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML5 semantic elements #8
Comments
Personally, I'd applaud this! However, this will break the CSS for existing users. We should therefore include this as an option. We could declare a customizable variable
This will introduce a number of I would like this very much! |
Implemented in #7 |
Hm? Pull request #7 was an attempt at generating validating HTML5, not using semantic tags. It doesn't wrap entries in |
Woops, my bad. |
Introduce new custom option `org-static-blog-use-semantic-html` that default to `nil`. If set to `t` - replace `<div id="preamble" class="status">` with `<header>` - replace `<div id="postamble" class="status">` with `<footer>` - replace `<div id="content">` with `<main>` - replace `<div class="post-date">` with `<time>` Regardless of the value: - wrap each post in `org-static-blog-assemble-multipost-page` in an `<article>` - wrap the title and date of each article in an `<header>` As discussed in bastibe#8
Hi, I was interested in this feature and it seemed within my (limited) elisp abilities. Would you be interested in a pull-request ? |
Absolutely! |
The feature is toggled via `org-static-blog-use-semantic-html`. The output is customizable via `org-static-blog-semantic-html-mapping`. closes bastibe#8
Would you be open to accept a pull request that changes the HTML output to use semantic elements? That is, an index page with elements like:
And perhaps using
<time>
for all dates.This could be done either as a replacement for most of the
<div>
tags or, if that is too controversial, perhaps a multi-stage merge: 1) Adding all the semantic elements without touching div's, 2) Warning all current users about the imminent removal of div's, 3) Remove unnecessary divs's.What do you think?
The text was updated successfully, but these errors were encountered: