From: Andriy Berestovskyy <berestovskyy@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] SSI or similar
Date: Mon, 14 Dec 2015 22:51:28 +0100 [thread overview]
Message-ID: <19813ADC-6039-4C13-9FE9-42F8D9D08C9A@gmail.com> (raw)
In-Reply-To: <42661128.1kKa8q4RBg@xps13>
> On 14 Dec 2015, at 21:53, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> Thanks for the suggestion.
> The current flat HTML files can be tested locally with just a browser.
> How a change would be tested with SSI?
At the moment all the links inside the HTML files are not relative (i.e. start with a slash), so browser as is does not render the pages correctly anyway.
Having SSI enabled we could separate the content from the rest of the page, say:
/dev.html: // the whole page to test with an HTTP server
includes inc/header.html
includes inc/menu.html
includes content/dev.html // flat HTML file to test with just a browser
includes inc/footer.html
So the „content" directory could be used to store flat HTML files, but without any headers/menus/footers.
Alternatively, we could build (i.e. concatenate) HTML pages using a makefile or a script. So we could have a structure as above without any code duplication. Then we could build the pages with headers and menus to test them locally or to upload to a web-server.
Andriy
next prev parent reply other threads:[~2015-12-14 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 20:38 Andriy Berestovskyy
2015-12-14 20:53 ` Thomas Monjalon
2015-12-14 21:51 ` Andriy Berestovskyy [this message]
2015-12-15 5:43 ` Thomas Monjalon
2015-12-15 22:12 ` Andriy Berestovskyy
2016-01-27 14:01 ` Thomas Monjalon
2016-01-27 20:50 ` Andriy Berestovskyy
2016-01-28 7:50 ` Thomas Monjalon
2016-01-28 9:48 ` Andriy Berestovskyy
2016-01-28 11:00 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19813ADC-6039-4C13-9FE9-42F8D9D08C9A@gmail.com \
--to=berestovskyy@gmail.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).