CVS edit link for moufmouf

The idea of the Static HTML Viewer module, is to bind a static HTML web site directly into Drupal.

This is not about importing a static HTML website into Drupal (this is already well documented). Instead, we are directly binding a website into Drupal.

This is very useful if you want to expose a set of HTML pages into your website without having to create a node for each page.

For instance, if you are a developer and generate documentation for your code (using Doxygen in PHP or Javadoc in Java), you will end up with a lot of HTML pages. You might want to expose those pages inside your Drupal website, in order to benefit from all the benefits of a Drupal install (themes, etc...) This module will help you do this: the content of every HTML page is copied in the content of the theme.

Until the project is approved, I am hosting the project on the page below:

http://www.thecodingmachine.com/static-html-viewer-drupal-module-bind-st...

You can download the module there.

CommentFileSizeAuthor
#1 static_html_viewer.zip10.28 KBmoufmouf

Comments

moufmouf’s picture

moufmouf commented
StatusFileSize
new static_html_viewer.zip10.28 KB
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed (maintainer needs more info) » Needs work
Issue tags: +Module review

Hello, and thank you for applying for a CVS account.

As per requirements, the motivation should include a comparison with the existing solutions.

moufmouf’s picture

moufmouf commented
Status: Needs work » Needs review

Hi Kiamlaluno,

Here is what could be added to the motivation to compare to existing modules:

The closest module to "Static HTML Viewer" is the Import HTML module.
While the Import HTML module creates a new Drupal node for each HTML page it imports, the "Static HTML Viewer" does not create any nodes. Instead, it loads HTML pages directly from the disk and embeds them in the Drupal theme.
This means that the Import HTML module is best used for one time imports, while the "Static HTML Viewer" is best suited for HTML static sites that changes often.

For instance, the "Static HTML Viewer" is great if you are a developer and are working with continuous integration systems that generate an HTML documentation for your project.

If you have a static HTML web site that needs importing, but are also looking to transform your website into nodes, you would rather want to use the Import HTML or one of the modules in this great comparison of import modules.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Thank you for your reply.

moufmouf’s picture

moufmouf commented
Title: moufmouf [moufmouf] » Static HTML Viewer module
Component: Miscellaneous » miscellaneous

Just changing the issue title.

Anyone for a review please? I know everybody must be quite busy :)

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Static HTML Viewer module » [moufmouf] moufmouf
Component: miscellaneous » new project application
zzolo’s picture

zzolo commented
Status: Needs review » Postponed

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

  • The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
  • Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Postponed » Closed (won't fix)

As per previous comment, I am setting this issue as Won't fix.
Since new users can now create full projects, applications have a different purpose and they are handled on a different issue queue. See Apply for permission to opt into security advisory coverage for more information.