Documentation and maintenance of layout. What is more convenient?

D

DenisZ2012-10-26 23:50:52

css

DenisZ, 2012-10-26 23:50:52

Sooner or later in any development team comes the understanding that something needs to be improved. This happened to us too :)
Description of the problem : there is a certain number of technologists working with the frontend on a long-term project. The number of technologists is increasing and there is a problem of communication. One of the challenges is documenting the html and css for better navigation and reusability.
It is not yet possible to use the bam toolkit and the assembly for a number of reasons) But the css and html description style is close to oocss, so we need a mechanism for documenting blocks with the possibility of a text description, placing a preview of the block and all the code that relates to it. Project code(s) at bitbucket.org. Tried his wiki - did not take root.

Essence of the question: what do you use?

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

E

egorinsk, 2012-10-27
@egorinsk

Make an HTML page/site in a local area with code snippets (for example: buttons and forms) and let everyone copy-paste it from there.
Well, or a more correct way is to make macros in a template engine for all occasions, if your template engine supports it.

D

DenisZ, 2012-10-27
@DenisZ

Well, since they put a minus, they would have commented already. Is the question stupid? Set incorrectly? Not enough data?

D

DenisZ, 2012-10-28
@DenisZ

Well, if you have some absolutely identical block that is found on several different pages (like the block of the last posts on Habré), I would take it out into a separate template and include it. I don’t know if the technology you use allows this, if not, then this is very bad, you will have to continue to suffer copy-paste with all the consequences.

Also, I would advise you to organize the templates systematically, by folders and files. so that it was not necessary to “look for them through the pages”, but it was immediately clear where this or that code is located.

With this, yes, it's clear. This is taken out in a separate template, connected where necessary and of course the code does not stretch or copy-paste. The question is in the stage before integration.
You need to think about a table with two columns. I just thought there was something more "industrial".