With this in mind, we decided the CMS guide should be created within the CMS as its own structure. Originally we thought of doing this as hard coded Twig files, however we knew down the line this would cause some problems when we needed to add specific content for the client. The first step was moving the CMS guide into the CMS. One which would display links to the Styleguide and CMS Guide within Craft itself. Our SolutionĪs a team we discussed creating a plugin. This means old versions end up hanging around long past their use-by date. Often clients will print them out, rather than referring to the “live” version. This makes the documents hard for them to find online. It also requires quite a bit of effort to maintain all the guides, through CMS updates and site development.Ĭlients also aren’t always in the Google Docs ecosystem. Generally it involved manually cutting/pasting content to create a new guide. The process of creating the guide was pretty tedious. When their content editors moved on, we often had to resend the guide, which isn’t user friendly or efficient. While this has served us well, there was the issue of the client saving or printing this documentation. This outlines how Craft works, and how each section of the site has been designed so they can easily update their site. ![]() Until now, this has been a branded Google Word Document that we send to the client before launch, to support a full CMS training session. The other client-facing document we created was a CMS Guide. While this isn’t a deal-breaker it also wasn’t the most user friendly way for the client to find it, so we needed to think of something better. However we had no way to get it to the client without sending them a URL. The Styleguide is also great for the client so they can see each component available on the site, and can select the appropriate one based on their content. The styleguide is used to create components and global styles across the site, and help to speed up our build time. A StyleguideĪ few years ago we introduced a Styleguide into each of our website builds. However we needed something bespoke for our build process. Having said that there are some bootstrap classes in use.The Craft Plugin Store is home to hundreds of plugins to help develop a website. ![]() ![]() Second anyone using this tutorial is going to want to style it themselves. The form was built before the page was styled so that we could ensure that all the functionality was working first and then build in the styles. The html in this tutorial includes limited styling for a couple of reasons. How do I enable redactor rich text editor in a front-end form?.How to update Matrix field on frontend for user profile.How to get matrix editor into frontend?.I found the following links to be helpful in building this out and include here as citation. All of the editing/creating was to be done on the front end of the site as head office does not want managers to have access to the Craft Control panel. I built this functionality for another agency where their client requested that managers be able to edit the content of their stores as well as create job postings and edit job postings that were created by head office.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |