Wondering if people could chime in on what their general workflow is moving from a front-end dev mode to pagelime. Do you just build out your front-end as normal and then just add a bunch of cms-editable classes and IDs onto everything after the fact? I'm finding that I need to add a lot of unnecessary IDs just to have things editable and am unsure how it makes most sense to name the IDs so I don't get confused and think there is a style associated with the ID... how do people deal with this? Just invent some simple ID code simply for pagelime purposes like #a1, #a2, #a3? or keep it more meaningful even though in some cases the ID may not connect to any styles? How are you managing your images and documents? are you just creating 'theme' images and uploading those separately and then using pagelime to integrate the body content images and pdfs and stuff? also, is there a way to have pagelime not mess up your code formatting output? guess i'm having like OCD about pagelime workflow or something could use some advice.
General Workflow
(4 posts) (3 voices)-
The ID doesn't have to be connected to a style at all. It's just a way for Pagelime to identify an area as unique, in case you move it around on the page, etc. We also use it to power our API, and for the iPhone app.
Posted 1 year ago #
Reply
You must log in to post.
