**OVERALL SCOPE OF PROJECT**.
The overall scope of this project involves customizing Microsoft Word 2007 by creating a new Tab in the Office Ribbon called "Lawfirm" using RibbonXML and Visual Basic.
The custom "Lawfirm" ribbon will dynamically load our lawfirm templates (ex: Letterhead template, Memorandum template) from a "templates" directory, and also contain groupings of default buttons and buttons assigned custom macros, we have already created the visual basic code that dynamically loads templates and have attached it to this project (see below).
The coder will also create a few basic macros such as ("footer" "signature block", etc) that will be assigned to buttons on the "Lawfirm" ribbon tab.
The final code will be easy enough for even non-technical users to deploy in a Word 2007 installation and will not give a macro security warning when the user clicks on Word 2007 or any of the buttons which are assigned to macros. All code will be clean, commented where appropriate, and deployed using "best practices" and be of sufficient production quality to be deployed in a Law Firm setting.
**STEP 1: FORMAT LAW FIRM TEMPLATES AS SPECIFICALLY DIRECTED.**
The first step of the project will require you to adjust the text spacing of a prior template to match our spacing requirements. This should be very easy.
**STEP 2: DYNAMICALLY LOAD LAW FIRM TEMPLATES.**
We have already started on this project and will provide our sample code (and supporting documentation upon request) (*see [url removed, login to view]*) which dynamically loads the formatted template files, however we will require you to modify it and/or clean it up, as we specifically direct in a later communication.
**STEP 3: ARRANGING DEFAULT WORD BUTTONS ON RIBBON IN GROUPINGS AS WE LATER SPECIFICALLY DIRECT**
The project will also require assigning various buttons in different groupings into the custom lawfirm tab, as we will specifically direct in the "informal documentation".
**STEP 4: CREATING SIMPLE WORD MACROS (i.e. "footer")**
Some of the macros that are required are the following (which will also be added as buttons to the "lawfirm" tab:
**1) FOOTER:** a "footer" macro which employs "best practices/production quality" VB programming, by "best practices/production quality" we specifically mean a footer macro that will work in all situations, so for example if the user is in "split screen" mode, the footer macro will still work, as another example, if there is already information in the footer in the document, the new footer macro will replace the old one without any formatting anomalies.
In addition, the footer macro will have a logically grouped way for the user to remove the footer on the first page only, or to remove all footer formatting entirely.
**2) SIGNATURE BLOCK:** several signature macros / which ideally will load dynamically from a "signatures" directory in a format we will later specifically direct
3) BOILERPLATE:** a macro which inserts standard "boilerplate" legal language, and contract signature blocks, which we will specifically provide later, and also a way for us to easily modify the boilerplate, preferably without having to do it in the VB editor.
**4) ENVELOPE:** an "envelope" macro button on the "lawfirm" toolbar
5) A few other macros related to legal formatting, and pleading as we will later specifically direct.
**STEP 5: ARRANGING THE ABOVE MENTIONED CUSTOM WORD MACROS AS BUTTONS ON THE RIBBON IN GROUPINGS AS WE LATER SPEFICIALLY DIRECT**
Simply, arrange all of the above custom macros as buttons on the custom "Lawfirm" tab.
Once again, the project will be easy enough for even non-technical users to deploy in a Word 2007 installation and will not give a macro security warning when the user clicks on Word 2007 or any of the buttons. This may involve creating a custom add-in, however we are not opposed to simply loading a secondary .dotm. All code will be clean, commented where appropriate, and deployed using "best practices" and be of sufficient production quality to be deployed in a Law Firm setting. There will be no bugs. **The visual basic source code, ribbonxml code, and any other code (but not code related to the software tools used to create this project) will be provided as part of the deliverable.
The above requirements are subject to our revisions as specifically directed in the informal communication process on [url removed, login to view]**