Those Pesky Creepy things called “Bugs”
Last week went a bit slow due to some unavoidable personal reasons, however, I managed to identify some major bugs that had cropped into the Composer Code. Most of these were basically layout related bugs affecting the general layout at varying device widths, however the two most significant bugs that are yet to be resolved via code were concerning the layout of the WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. toolbar and scroll-ability of the Composer page.
It seems that the best solution for the first problem would be to remove the toolbar from above the textarea and replace it with a floating toolbar over the onscreen keyboard. A few simple CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. tricks should be quite able to take care of this problem.
The second problem is a bit tricky though. Ever since I changed the layout of the composer to a single page layout, the scroll-ability of the page seems to have been disabled. This is most likely the result of using overridden fit-able classes, however, I’m yet to investigate further into this problem. I plan to take on this bug sometime later this week and get it done.
Developing the Pages Module
The next thing that I started with this week was implementing the Pages module. After doing a brief comparison between the Pages and Posts module, it was pretty clear that Pages is pretty similar to Posts and requires almost the same code with a bit of reduced functionality. The way I implemented this was by rewriting the same code as the Posts module with a few exceptions in the Composer functionality, mainly the removal of Categories, Tags, Status and Post Format functionalities from it.
Next Steps
The major work that I will be undertaking this week would be fixing the WYSIWYG and scroller bugs after the Pages module is completed. Once this is done, I would start with a few unfinished functions within the Preview module, and move on to a bit of Styling details.