Calendar grid and date proofing
VectorPaint calendar proof: a Monday-first November 2026 grid needs a sixth row for the 30th
Practice a seven-column, six-row layout for a fixed month, checking weekdays, dates and blank cells separately before exporting an original static calendar.
On this page
Design an original static calendar for November 2026 in seven columns from Monday through Sunday. The month starts on a Sunday and ends on a Monday, so a complete grid needs six rows: only the 1st falls in the first row and only the 30th in the last. Check dates first, then arrange lines and text in VectorPaint. The drawing does not update automatically and is not a calendar event or reminder.
Fix the month and week-start rule
Record year 2026, month 11, Monday as the first column and 30 days in the month. Do not mix in a Sunday-first convention used elsewhere: it changes positions and cannot reuse this grid unchanged. On an approximately 1800 × 1500 landscape canvas reserve room at top for month title, weekday headings and the grid below, with space beside it for proofing notes. Group grid, dates, weekdays, title and guides separately and save an editable original.
Draw seven columns and six rows
Below the title create seven equal-width columns and six date rows. Draw shared edges once so overlapping strokes do not make individual vertical lines heavier. Use visible guides and manual shapes or alignment/distribution controls actually offered by the installed version; do not assume an automatic calendar component. Six rows give 42 date cells: 30 numbers and 12 blanks. The weekday heading is not one of those cells. Inspect boundaries and spacing first. If the last row clips at the frame, enlarge the content area or adjust spacing rather than deleting the row containing the 30th.
Label weekday columns left to right
Label the columns Monday, Tuesday, Wednesday, Thursday, Friday, Saturday and Sunday, aligned above their respective centers. Weekend colors may vary slightly but words must remain sufficient to distinguish the columns; do not rely only on color. Check every heading, especially that Monday and Sunday are not swapped. When changing language, adjust word widths without silently changing the first-day rule. If headings collide when reduced, adjust type size or column width first.
Fill six date rows and retain blanks
Leave Monday through Saturday blank in row one and put 1 under Sunday. The next four rows contain 2–8, 9–15, 16–22 and 23–29. Put 30 under Monday in the last row and leave Tuesday through Sunday blank. The two dots below mark blanks only in the checking table; they need not appear in the finished artwork. Dates may omit leading zeros, while the table uses two digits for column alignment. Fill rows first, then inspect columns rather than copying the prior month's layout by eye.
Mo Tu We Th Fr Sa Su
.. .. .. .. .. .. 01
02 03 04 05 06 07 08
09 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 .. .. .. .. .. ..
Check counts, weekdays and boundaries
Count 1 through 30 once each. The Sunday column must contain 1, 8, 15, 22 and 29; Monday contains 2, 9, 16, 23 and 30. Six leading blanks and six trailing blanks give 12, and 30 + 12 = 42. There is no 31st; do not automatically fill blanks with adjacent months. Verify externally with an existing Gregorian-calendar tool. Python's standard calendar can set Monday as the first day, but the numbers still require manual layout and checking in VectorPaint.
In a proof copy highlight all Sundays, then only the last row, ensuring both the 1st and 30th survive. Put proof marks on a separate layer and hide them afterward instead of erasing dates. If an entire column shifts, first check the Monday-first rule and headings, then move dates to the correct grid rather than dragging numbers randomly until spacing looks even.
Arrange title, dates and room for notes
Use a clear type hierarchy for month title, weekday headings and dates. If leaving room for handwriting, place each date near a cell corner; a reading poster may use larger dates, but no numeral should cross into its neighbor. Use a small consistent palette and check text against a light background. Do not label dates as statutory holidays, anniversaries or private plans without separately verified data; this proof communicates dates and weekdays only.
For proofing, temporarily number the first-row blank cells lightly and count them separately from the final-row blanks. These marks belong on a checking layer hidden before output. If notes obscure a date, shorten them or enlarge the cells rather than moving the date to another weekday. Keep the version from before checking so layout changes remain distinguishable from changes to date data.
Check both languages and small outputs
For an English copy use Mon through Sun, retaining Monday first and the same six rows. Titles may occupy different widths, but shorter words must not shift date columns. Reduce both versions to the intended size and confirm Monday and Sunday remain distinct and 1 and 30 remain in their corners; screenshot scale is not actual print size. If lines crowd, lighten stroke or increase spacing before deleting the sixth row. Keep a monochrome proof readable without color.
Save, export and inspect
Keep editable dates, grid and language copies. Hide temporary proof marks and export SVG, PDF or PNG through an actually available control, then open it elsewhere. Check title, 42 cells, sequence and crop. PNG is raster; SVG or PDF containing bitmaps is not automatically all vector. Reopen the source and move one grid line to inspect grouping. Mark unperformed export, reopening or device tests pending. A different month needs a new first-weekday and day-count check; this static proof is not a perpetual calendar.
Related guides and sources
Align and distribute three buttons; Checklist rows and writing space.
Method reference: Python standard-library calendar documents first weekdays and month grids. The November 2026 table was checked as Gregorian with Monday first; layout is original and does not depend on the app calculating dates.
Checked 20 November 2026: Apple's public lookup lists VectorPaint 1.0.8, requiring iOS / iPadOS 17.0 or later. The official store describes shapes, text and SVG editing. No completed physical-device test is claimed.