Ok, I may resolved this. I asked a similar question earlier about images. I published the contactus.html page, and I am keeping everything in the public HTML folder.
Is that ok? Will that cause any issues later by having it too cluttered?
There is no technical problem with keeping the HTML files and graphical image content in the same directory or folder. As the webmaster or web site designer, you may decide which specific directory or folder to store specific files in. I believe the answer to this depends more on your personal preference for how the site will be designed versus what technical hurdles that may be at play. From my experience, I found it more desirable to have web site files and directories setup in an organized manner whenever possible. For example, it may ease site management by organizing images into a specific images folder, organizing CSS (cascading style sheets) into another folder, and JS (JavaScript) into their own as well; however, both CSS and JavaScript could be included in the same files as the HTML, so it is not required to separate them as either way will still work.
Example directory layout, depending on what type of content is stored:
Code:
~/public_html/
~/public_html/css/
~/public_html/images/
~/public_html/js/
Regarding an earlier question of the source paths or links to use: I recommend that if the page, image, or other content is local to the same web site (e.g., involving the same domain name), then a relative path should be used (i.e., relative to the HTML document or relative to the root of the web site's domain), where as if the page, image, or content is from a remotely-hosted or third-party web site, then typically it is required to use the full, absolute URL. For additional clarification and reference I suggest the following third-party article from the Adobe knowledge-base:
Document-relative, site root-relative and absolute paths
I am not sure they were the same question really. But I can also see being moved the newbie section of the forum.
Is this not a forum that assists with using the cPanel product? If not my appologies, I was under the impression that if I purchase this product, that these forums are in place to help me with this product and making sure I am using it correctly. In other words, I am the host and I am trying to learn.
I do not have the background of most others here, so again, sorry for being a newbie, but there are things that I do not know, and could really use the expertise of the members here.
Thank you
You are welcome to post questions; I believe
Infopro meant well in that it can oftentimes help to group similar discussions into the same thread. Unless it is explicitly stated or noted, it can be difficult to accurately determine whether or not someone handles their own reseller hosting account, full dedicated server, both of which would have access to the Web Host Manager (WHM) area of the control panel, or if someone primarily uses only cPanel, such as an end-user without WHM access. Typically it is the web hosting service provider (or server hosting provider, etc.) that is first in line to answer initial getting-started questions, of which some hosts also offer web site builder features and or templates to help simplify the process of creating a new web site.
In my professional opinion, I would consider using a dedicated software application solely intended for web site design and web site management; I believe this route will help greatly in terms of getting started, advancing quickly and especially to ease the process of managing the web site's complete structure and process of publishing content. However, as with anything new to be tried, there would be a learning curve involved and so I recommend seeking help from someone that can offer local, one-on-one assistance while getting to know how everything works.
If you have any specific questions with regard to how cPanel and WHM works, please do let us know; we are here to help.
P.S., For cPanel/WHM-specific information I recommend reviewing our official documentation at the following web site:
cPanel/WHM Documentation Intro
