I just got a new website. I’m trying to make a Word document that I have, a one pager, be a webpage that I link to.
What I’ve done: Uploaded the document to my file manager, under the public_html. I have renamed it, and it has a .doc suffix. On my home page source coding, I have <a href =" /<newtitle.doc" and end up getting a window that offers to download the file. I didn’t want to download the file to the site visitor, I wanted to display it as a webpage.
So, where did I miss the boat?
Your problem isn’t with cpanel, it’s that what you’re trying to do just doesn’t work that way. It’s attempting to download it because it’s a file, not a html web page. In order for it to be seen inline in a web browser, it has to be a .html page, not a .doc. And simply changing the extension won’t do it.
I believe most recent versions of Word have a “Save as web page” option. That will give you what you want, with basic formatting intact. Then just upload that new .html file just like you did the original. If you’re on an older version of Word that lacks that feature, you could export it as a Plain Text file, NOT as a Microsoft Word file, and then change the extension to .html. Keep in mind if you go that route, you’ll lose all formatting. It’ll just be a page of raw text, but it’ll display in the browser.
ugh. using Word’s “save as web/html” option is an affront to western civilization.
in fact, I would gladly volunteer my time to convert your Word document to hand-coded html/css just to keep what MS tries to pass off as html off of the internet - see my profile for contact info
Is it that bad? I’ve never used it, so haven’t seen what it puts out. That’s too bad; formatting a simple text document into clean HTML/CSS shouldn’t be that difficult.
I used to convert Word documents to various formats for a living - it was easier to convert to plain text and rebuild html from scratch than to try and clean up the code created by the built-in function. I did a project for a major oil&gas entity last year that involved converting all of their existing html intranet to Word, which was then being converted on the fly by their new intranet platform to html, using the built-in function - I guess it was ok for them, as they were still using Windows 2000 and IE6 on every desktop across the world.