1966Mustang
Member
Hello,
I need some advice. I have a large number of static html pages that are CSS and table heavy... I am currently migrating the forum part of the site to 2.1.6p1. I have created a couple of pages in both AMS and Resources and I am generally pleased at first glance with the results, but the process is somewhat tedious and I can envision it being a PITA.
The site with the static content is: https://fordsix.com/ci/Tech.html
Since they are static HTML pages, it makes updating and managing the information difficult (basically never happens), so my plan is to recreate them in either the default XF Resources or AMS system.
My other goals for this content are:
I may make these pages available to members who purchase access or who have attained certain promotions etc.
I would like to keep the number of 3rd party extensions down.
The content should look like the main site. I don't need to recapture the exact look/feel of the existing content (and prefer not to)
Easily editable by staff members / other trusted contributors
The content doesn't need to be available in it's new form all at once for go-live. If it needs to be hand crafted into either AMS/Resources and rolled out as it comes then that is fine.
Thanks for any advice!
I need some advice. I have a large number of static html pages that are CSS and table heavy... I am currently migrating the forum part of the site to 2.1.6p1. I have created a couple of pages in both AMS and Resources and I am generally pleased at first glance with the results, but the process is somewhat tedious and I can envision it being a PITA.
The site with the static content is: https://fordsix.com/ci/Tech.html
Since they are static HTML pages, it makes updating and managing the information difficult (basically never happens), so my plan is to recreate them in either the default XF Resources or AMS system.
My other goals for this content are:
I may make these pages available to members who purchase access or who have attained certain promotions etc.
I would like to keep the number of 3rd party extensions down.
The content should look like the main site. I don't need to recapture the exact look/feel of the existing content (and prefer not to)
Easily editable by staff members / other trusted contributors
The content doesn't need to be available in it's new form all at once for go-live. If it needs to be hand crafted into either AMS/Resources and rolled out as it comes then that is fine.
Thanks for any advice!
